Versions Compared

Key

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

Summary:

Planned topics

...

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

...

  • Troy Roda (SecureKey) <troy.ronda@securekey.com>
  • Baha (SecureKey)
  • Bob (SecureKey)
  • Aleks (SecureKey)
  • Filip (SecureKey)
  • Firas (SecureKey)
  • Talwinder (SecureKey)
  • Sandra (SecureKey)
  • Sudesh (SecureKey)
  • Rolson (SecureKey)
  • George (SecureKey)
  • Arjan 

Welcome / Introductions

Announcements

  • None

Release

...

  • None

...

status and milestone progress

  • 0.1.0: Trending towards 1-2 weeks behind.

Work updates (from the previous week)

  • State handlers completed (Talwinder)
  • Selection criteria RFC (in progress) (George)
    • Feedback provided regarding incorporation of missing use case
  • Ability to inject custom configuration into default providers completed (Firas)
  • Allow injectable Wallet completed (Firas)
  • Inbound Transport Initiation in framework.New() complete (Rolson)
  • JWE Authcrypt Decryption - Completed except for switching OID to SKP recipient header and interop with PHP encryption (Baha)
  • Controller API for share invitation workflow (completed), (Sudesh)

Grooming oversight

  • Add support for Ed25519VerificationKey2018 #96 (Filip / Baha)
    • Epics needs breakdown into tasks.
  • Note: next week will need a bit more time on grooming before the weekly meeting.

Design discussion

...

Other business

  • TBD

Other Business

  • TBD

Future Topics

  • TBD

Future topics

  • Indy DID resolution and payloads (beside the W3C standard versions that we are implementing as our first priority).
  • High-level eventing/messaging proposal 
    • Golang API (channel based) (Rolson)
    • REST API (webhook based) (Rolson / Sudesh?)

Action items

  •  TBD