...
- Record the meeting
- Absa wallet: how AFJ reduced thousands lines of code, by Jakub Koci
- Moving to OWF - proposal
Meeting Notes
- Moving to OWF - meeting notes from this week's Aries WG
- https://github.com/hyperledger/aries-framework-javascript/discussions/1586
- Org migrations should be done with a transfer of the repo
- maintains links & commit history
- Move is far better than a fork.
- Should discuss which components would be moved simultaneously
- Probably at least Bifold and Askar
- What to do with the RFCs?
- Interoperability: are .Net and Go implementations still interoperable with the latest RFCs and interop suite?
- .Net already moved to OWF
- OWF policy: maintainers are in charge of the repositories and decisions (same as in Hyperledger)
- AJF would probably be the most mature wallet framework, so OWF would have an incentive to promote and market it
Recording / Slides
Future topics
Future Topics:
- 0.5.0 release
- Separating the storage layer
- Storing messages? All state should be derived from message exchange
- User chooses whether to store the messages, but user needs to provide the current state of the protocol
- Goal from Timo: More control over the database entities, how state is persisted.
- Built in storage useful in a lot of cases as well
- Discuss next time: current storage model
- Splitting DIDComm in packages like:
- @afj/didcomm-base
- @afj/didcomm-credentials
- @afj/didcomm-proofs
- @afj/didcomm-mediation
- Storing messages? All state should be derived from message exchange
- DIDComm v2
- Discover Features V2 over DIDComm V2: https://github.com/hyperledger/aries-framework-javascript/pull/1576
- Basic Messages V2: https://github.com/hyperledger/aries-framework-javascript/pull/1546
- Credentials protocols V3: https://github.com/hyperledger/aries-framework-javascript/pull/1560
- Missing:
- DID Rotation
- Mediation / Pickup
Meeting Notes
- Moving to OWF - meeting notes from this week's Aries WG
- https://github.com/hyperledger/aries-framework-javascript/discussions/1586
- Org migrations should be done with a transfer of the repo
- maintains links & commit history
- Move is far better than a fork.
- Should discuss which components would be moved simultaneously
- Probably at least Bifold and Askar
- What to do with the RFCs?
- Interoperability: are .Net and Go implementations still interoperable with the latest RFCs and interop suite?
- .Net already moved to OWF
- OWF policy: maintainers are in charge of the repositories and decisions (same as in Hyperledger)
- AJF would probably be the most mature wallet framework, so OWF would have an incentive to promote and market it
Recording / Slides
Future topics
...
- It would be good to discuss OCA implementation in AFJ and in Aries Bifold and where should be a boundary between the two in this feature.
- Extracting parts of AFJ into generic libraries
- Cheqd integration (Daev Mithran )
- AFJ Interop tests not running
...