Summary:
| Excerpt |
|---|
Planned Topics:
|
Recordings from the call:
- Full Meeting: 20220614 ACA-Pug Community Meeting Call Recording.mp4
- Extracted segments:
- Relevant Chat Bits:
...
- Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
- Wade Barnes(Neoteric Technologies Inc.) <wade@neoterictech.ca>
- Bruno Hivert(https://idlab.org) <bruno.hivert@idlab.org>
- Colton Wolkins(Indicio) <colton@indicio.tech>
Announcements
Deployments and Work Updates
- BC Gov Team
- Aries Cloud Agent Python
- Aries Shared Components – indy-vdr, indy-shared-rs and aries-askar
- Aries-VCR/OrgBook BC Deployment
- Issuer Kit - VCs for OIDC Issuer Service
- Aries Agent Test Harness work - Results page: https://aries-interop.info
- Aries Mobile Test Harness
- BC Wallet – based on Aries Framework JavaScript and Aries Bifold
- Aries Endorser Service
- Traction
Agenda
- An update from Hakan Yildiz and his team from the discussion on 2022-04-19 about adding DIDComm V2 to ACA-Py.
- Getting to release 0.7.4 – what is needed after RC2
- Dealing with duplicate Admin API calls – e.g. Issue 1798 - store credential; Issue 1782; even issue 1730 - problem report for a non-protocol
- How aggressively should we address these issues?
- One pass through the protocols, states and endpoints?
- As they come up?
- From discussion:
- Where possible, report back to the Controller that their call was unexpected – by the response to the request where possible, perhaps via the follow up event.
- Separate out where the action breaks the protocol (interaction with other Agent) and where it impacts only the operation if this agent (e.g. the store credential example – doesn't impact the execution of the protocol).
- Definitely prevent problem reports being sent out BEFORE the protocol exists (the issue 1730 - problem report for a non-protocol example).
- For now, handle as they occur and learn from those implementations.
- Look for the patterns and see if there is something that can be done at the framework level. What do other frameworks do?
- How aggressively should we address these issues?
Next Meeting
- An update from Hakan Yildiz and his team from the discussion on 2022-04-19 about adding DIDComm V2 to ACA-Py
Future Topics
Action items
...