Meeting recording


video1616040318.mp4

Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.


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.

Attendees

Resources

Status updates

Agenda

  • Record the meeting
  • OWF

    • OWF is interested in 'wallet engine components' so viewing AFJ as a wallet engine will be a good frame.

    • we'll talk about common components before, so askar will be explained already. probably an architecture diagram?

    • the 'features' list will be similar to the other projects, but noting things like Bluetooth and OpenID4vc progress will be interesting.

    • OpenWallet Foundation presentation from Aries community - February 20th 8PM CET
    • Topics / Ideas
      • Future plans regarding OpenID (e.g. verification side)
      • Multi-credential format support
      • Non-Indy specific / Ledger Agnostic (core + specific components)
      • Multi-platform (Node.JS / React Native)
  • Shared Components React Native / Bifold integration
    • Remove support for Indy SDK?
      • Need migration script from Indy SDK to Aries Askar
      • Need clear communication, no versioning for Bifold at the moment
      • Need good documentation on how to migrate
      • Keep it simple, just do it
      • Keeping separate branches is complex, the faster we get it done the better
      • Create a tag for the commit that includes the migration
      • I'd surface the issue and allow anybody in the community to raise their voice if they want to keep IndySDK. (We'll ask the community in the Bifold Discord)
    • Lowest Android  version?
    • Migration Script support version?
      • Prompt the user to open the wallet and upgrade
      • Complexity: have to upgrade from any version to any version
      • Optional module
      • The app vendor can decide how long to keep the migration script in. People can update the migration script as long as there's a need for it.
      • As per iOS — “Use the BackgroundTasks framework to keep your app content up to date and run tasks requiring minutes to complete while your app is in the background. Longer tasks can optionally require a powered device and network connectivity.”
      • https://developer.apple.com/documentation/backgroundtasks
  • Module bundles
  • AFJ as a mediator. Thoughts and conversation on High Availability (HA) support. Anyone who runs a mediator in prod will probably want HA (3 pods, 3 servers, etc) (Jason Leach / Timo Glastra)
  • Open Issues / Pull Requests

Meeting Notes

  • ...

Future topics

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.