Summary:
Topics:
- PRs, Issues
- Status: OWF Submission
- Handling PyPi (`aries_cloudagent`) and GHCR artifacts during the transition
- AATH ACA-Py Backchannel into ACA-Py?
- did:tdw Resolver
- Progress on other initiatives
Zoom Link: https://zoom.us/j/91279968714?pwd=Yk9GVVNLOFE1cklkSk51UEZQTklOQT09
Call Time: 9:00 Pacific / 18:00 Central Europe
Recordings From the Call:
|
LF Decentralized Trust is committed to creating a safe and welcoming community for all. For more information please visit the LFDT Code of Conduct. |
|---|
Welcome, Introductions and Announcements
- Heads Up: New Zoom links for this meeting and ACA-Pug when we move to OWF
Attendees
- Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Announcements
- ACA-Py documentation: https://aca-py.org
- Plugins: https://plugins.aca-py.org
- did:tdw DIF Working Group Meeting this Thursday, Sept. 26 at 9:00 Pacific / 18:00 Central Europe, Agenda/Zoom info is: https://hackmd.io/k4cIK9vQSlaeg2pdHE51IQ
Agenda
- New maintainers – Thiago and Mourits - #3239
- Dealing with artifacts and naming:
- Any flashes of inspiration on the name?
- What do we rename "aries_cloudagent" to? "acapy_cloudagent"? Leave it the same?
- Can we keep publishing to PyPi "aries_cloudagent" after we make such a change?
- Assuming we can get permissions, can we keep publishing to GHCR – e.g.ghcr.io/hyperledger/aries-cloudagent-python:py3.12-1.0.0
- Should we keep a fork of ACA-Py at it's current
https://github.com/hyperledger/aries-cloudagent-pythonlocation with an updated README so we can keep the GHCR?
- Should we keep a fork of ACA-Py at it's current
- Documentation – what file should we create? Just put it at the top of the README in screaming letters?
- Document that details the change – published on https://aca-py.org
- Discord
- Aries Mailing List
- Any concerns about the plugins?
- Any other concrete things we can do?
- Timing:
- Should we update the documents across the board first or move the repo first?
- PRs and Issues – #3184 (connection protocol – and next version number and how to document?), #3246 (multikey management), #3243 (in-memory wallet),
- Any thoughts on #3240 – extending the
--seedto include what DID method to use with the seed? - Progress on other initiatives:
- OpenID4VCs plugin - Indicio team focus
- Other?
- Open Discussion
- Urgent request to complete did:indy support (e.g., JSON-LD VCs based on did:indy DIDs) – triggering learnings about DID handling. Daniel Bluhm to assemble those learnings and share as work proceeds.