Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Summary:

Planned:

  • Planning future meetings
  • Language wrappers: SDKs and Frameworks
  • Misalignment between RFC 94 and ACA-Py
  • Aries KMS design

Note: This call is Recorded. Recordings posted at the bottom of the page.

Date

(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

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                                                                                                                                                            

  • Name (Employer) <email>

Welcome / Introductions

Announcements

Related Calls

  • Previous Aries Working Group calls
  • Identity Implementors Working Group call
    • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

RFC Progress

  • Rich Schema RFC headed to an APPROVED status, Troy had some comments on how the Link Secrets tie to W3C spec.
  • Proposal to renumber RFC 0289
  • Progress on JWE envelopes (RFC 334).
  • Draft RFC on HTTP over DIDComm.

Other Business

  • Scheduling future meetings
    • January 1: Cancelled
    • January 15: Need to select a topic
  • Aries language wrappers
    • Connect-a-thon proposal: let's only build Frameworks instead of SDKs—let's be opinionated!  Simplify the experience of a new developer.
      • Merge the SDK and the Framework repositories so developers don't have to choose between them.
        • aries-sdk-go should merge into aries-framework-go
        • aries-sdk-javascript should move into aries-framework-javascript
        • other SDKs renamed as Frameworks?
      • Can have a separate SDK artifact in the Framework repository, if desired.
    • When can we deprecate the Indy SDK wrappers?
      • Overlap in development between Indy and Aries. New developers should start in Aries.
      • Hard to maintain CI / CD and do bug fixes for environments and wrappers we don't use.
      • IS-1423 for DotNet, because the Aries Framework is mature.
      • IS-1424 for Java, JavaScript, Android, iOS
      • Challenges with Python
  • Misalignment between RFC 0094 and ACA-Py
  • Aries KMS design
    • Define approved algorithms
    • Define plugin interface
    • 3rd party libraries we could leverage:
      • Google Tink as an encryption library

Future Topics

Action items

  •  

Call Recording

  File Modified




  • No labels