Meeting recording
...
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy . If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
...
- Aries Bifold (Aries Bifold User Group Meetings)
- Short meeting to catch up on open PRs
- Restructuring of repo to monorepo/workspaces has been merged
- PR open for shared components (draft)
- Short meeting to catch up on open PRs
- Aries Call 2023-02-08 Aries Working Group Call
- presentation on OCA bundles by Stephen Curran
- Presentation from Thomas on Nessus CLI with W3C VC exchange, DIDComm v2, DIDComm v1
- Releases
- AFJ 0.4.0-alpha releases (74)
- DIDComm v2
- Aries Interop Profile 3.0 continues to be discussed https://hackmd.io/_Kkl9ClTRBu8W4UmZVGdUQ
- Shared Components
- Indy VDR 0.1.0-dev.12
- React Native & Node.JS
- No support for older Android versions yet
- Aries Askar 0.2.8-dev.6
- React Native & Node.JS
- https://github.com/hyperledger/aries-framework-javascript/pull/1211
- ACA-Pug Call talking about Askar profiles: 2023-01-24 Aries Cloud Agent - Python Users Group Community Meeting
- AnonCreds 0.1.0-dev.11
- Node.JS
- React Native
- Berend made a demo: https://www.loom.com/share/8497e12cb1c64383aa01768ac2551078
- Indy VDR 0.1.0-dev.12
- Open Source Summit in Vancouver
Agenda
- Record the meeting
- Open PRs and issues for 0.4.0 release
- JSON-LD enabled by default?
- BBS package public
- Continue the conversation about “prioritisation for 0.5.0”
- DIDComm v2
- now that indy-sdk is gone, other libraries have DIDComm v2 support, main objective of AIP 3
- Askar as backend for DIDComm v2? SICPA has implemented using didcomm v2 wasm library
- support both libraries
- Need to work on a new wallet api
- focused on indy-sdk
- still uses parameters for indy-sdk
- way we are creating / opening the wallet is inherited from indy-sdk
- Improving interfaces for message repository
- fully support pickup v2 and v3 protocols
- be a mediator without in memory message repository
- Refactor basic message / trust ping to align with new way of doing things (support multiple versions of the protocol)
- End user wallet perspective
- key rotation
- changing mediator
- initialization, efficient way to check if the wallet key is valid
- DIDComm v2
...