2023-10-31 Aries Cloud Agent - Python Users Group Community Meeting
- Stephen Curran
- Warren Gallagher
- Kimmo Hovi
Owned by Stephen Curran
Summary:
Topics:
- 0.11.0-rc0/rc1 releases
- Moving from CredX to AnonCreds-RS
- PRs and Issues - status update
- Open Discussion
Zoom Link: https://zoom.us/j/98856745538?pwd=VkJROWRxeW43d3hOdnJLemwrS0JKUT09
Call Time: 8:00 Pacific / 17:00 Central Europe
Recordings From the Call:
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
Welcome, Introductions and Announcements
- BC Gov Code With Us – AnonCreds in W3C Format – Application Period open until October 20, 2023.
- Hyperledger Member Summit October 23 in San Francisco and December 4 in Tokyo
Attendees
- Stephen Curran (BC Gov/Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
- Warren Gallagher (AffinitiQuest) <warren@affinitiquest.io>
- Emiliano Suñé (BC Gov/Quartech) <emiliano.sune@quartech.com>
- Daniel Bluhm (Indicio PBC) <daniel@indicio.tech>
- Sean Bohan_personal (Hyperledger Foundation) <sbohan@linuxfoundation.org>
- Kimmo Hovi (FindyNet) <ext.kimmo.hovi@findy.fi>
- Alexandra Walker (Indicio PBC) <alex.walker@indicio.tech>
Announcements
- ACA-Py documentation: https://aca-py.org
Agenda
- Release 0.11.0-rc0 and 0.11.0-rc1 released
- Publish failed on 0.11.0-rc0 because of the handling of sd-jwt library
- Publish failed on 0.11.0-rc0 because of the handling of sd-jwt library
- Next releases – per this plan (Issue #2569):
- 0.11.0 final with additional, labelled 0.11.0 PRs planned added in. Any others wanted?
- Additional 0.11.x patch releases as needed – not from main.
- Same approach as we used for the 0.10.x releases.
- Main branch work to get the AnonCreds-RS branch added in, based on this approach (Issue #2567), working as quickly through the process as possible.
- Other PRs Ready for Review and Issues to Discuss
- Update on Please Ack:
- Implementation comes down to a clarification needed and to be discussed at tomorrow's Aries Working Group call:
- Does a ~please_ack for OUTCOME on an incoming message apply to the processing of that message only, or to the overall protocol? The RFC is not clear on that.
- It appears a bit easier to determine what it would mean and how to apply it if applied to the protocol, not so much if applied to the message.
- Implementation comes down to a clarification needed and to be discussed at tomorrow's Aries Working Group call:
- Open Discussion
Upcoming Meeting Topics:
- Discussion Topics:
- Update on ACA-Py Container Scanning
- Multi-architecture containers
- Issue with BBS+ package – doesn't support ARM containers – need an update to their CI
- Solution: A third container published that includes BBS+ package, but is single architecture
- Others are Askar
- The DSR team has started looking into supporting the "please-ack" protocol. A draft PoA will likely be ready for review on the next call,