Versions Compared

Old Version 2

changes.mady.by.user Richard Esplin

Saved on

compared with

New Version Current

changes.mady.by.user Richard Esplin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt

Planned:

  • Planning future meetingsAries KMS design
  • Language wrappers: SDKs and Frameworks
  • Resolving different interpretations of Aries RFC 0094.

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

...

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                                                                                                                                                            

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.

...

RFC Progress

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
    • ACA-Py pull request: https://github.com/hyperledger/aries-cloudagent-python/pull/240
    • Evernym products and Pico implemented one way, ACA-Py and DotNetFramework implemented the other. Resolution will be a breaking change.
    • A breaking change will be needed in the near future to implement Tobias' proposed changes to the envelope format.

Future Topics

  • Next call
  • Other:
    Next call
    • Aries KMS design
      • Define approved algorithms
      • Define plugin interface
      • 3rd party libraries we could leverage:
        • Google Tink as an encryption library

Future Topics

...