Versions Compared

Old Version 19

changes.mady.by.user Camilo Parra

Saved on

compared with

New Version 20

changes.mady.by.user Paul Knowles

Saved on

Key

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

Summary:

Excerpt

Planned:

...

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.

...

  • Ursa - Progress on packages and Plenum work.
  • Semantics - Pilots underway - The agenda, video, notes, etc. from yesterday's HL Indy Semantics WG call: 
  • DID UX Call - Slack/Mailing list - details in the shared document as well minutes and additional information, currently bootstrapping discussion about UX for defined personas
  • Indy Contributors - Richard Esplin (Mon) - Discussed future of Indy Ledger (View Change, Aardvark BFT, bug fixes, future of Plenum)
  • Identity WG / Identity WG Implementer calls (Wed / Thurs)

...

  • Aries Protocol Test Suite
    • Works, and ready for test contributions
  • Aries Core Libraries (agent storage, ledger interface, comms)
    • Moving Indy Wallet crate into aries-ams aries-kms (name changed on repo... MIGRATION is being planned and not approved)
      • SQLite as the default wallet.
      • aries-ams-sqlite is archived
    • Need to migrate Postgres wallet plugin from Indy to aries-ams-postgres
    • Future:
      • Verifiable Data Registry Interface library
      • Static Peer DIDs in aries-vdri as the default implementation
      • aries-vdri-peer is archived
  • Aries-CloudAgent-Python (bc.gov) - Release 0.3.5 Coming Soon - mainly cache handling updates.
    • Continuing to learn about performance/storage impacts of using Aries protocols and non-secrets (metadata) interface.
    • Lessons learned:
      • Database calls are fast, but there are a lot of calls being made - take great care in using tags (credentials and protocol state)
      • Protocol state is large - leave it to controller to decide what to keep
      • Really hard to understand inside the KMS - what's happening and getting metrics out.
      • Caching is hard (smile) - self-inflicted wound
      • Current issue - not understanding all the calls to "SELECT item" from secrets storage.
  • Aries-Framework-Go (Troy)
    • Weekly planning notes (2019-10-29)
    • Closing the 0.1.0 milestone this week.
      • Framework structure.
      • Draft DID Exchange Protocol (including Go and REST "controller" APIs).
      • HTTP Binding for DID resolver along with first phase of peer DID support.
      • Envelope pack/unpack (including support for draft JWE envelopes).
    • Shifting focus to the 0.1.1 milestone.
      • Introduce and issue credential protocols (and finalize DID Exchange).
      • WebSocket transports.
      • Refactor pluggable interface categories (kms, crypto, ...).
      • Stretch goals (in planning page).
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav) Transaction Authors/Endorser support for Indy.
  • Aries-SDK-Python - PR from JeromeK - weigh-in from those interested in Python wrapper would be appreciated.
  • Aries-SDK-Java - Usually Wed Evenings
    • Javier => asking help to move forward. Any agenda on what is being developed on other SDKs?
  • Aries-SDK-JavaScript - Contributors are now meeting on every Fridays - 
  • Indy
  • Ursa

...