2019-11-12 Framework Go Weekly Planning
Summary:
Planned topics
Work updates (5 mins)
Grooming (20 mins)
Design discussion (20 mins)
Open Discussion (10 mins)
Date
Nov 12, 2019 (7:30AM Los Angeles, 10:30AM Toronto/New York, 3:30PM London, 17:30H 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
@Андрій Солук (Euristiq) <andrii.soluk@euristiq.com>
@Firas Qutishat (SecureKey) <firas.qutishat@securekey.com>
@Rolson Quadras (SecureKey) <rolson.quadras@securekey.com>
Welcome / Introductions
Announcements
None
Release status
None
Work updates (from the previous week)
0.1.0 documentation #739 - @Firas Qutishat
Refactor DidResolver.Read() should return a did.Doc #118 - @Firas Qutishat
Refactor use did resolver to get the peer did doc #703 #645 - @Firas Qutishat
DIDExchange - State Name update for Action Events Github #690 - @Rolson Quadras
RestAPI - Accept Invitation API Implementation Github #692 - @Rolson Quadras
Fix for query connection not returning transient data - Github #722 - @Rolson Quadras
DID exchange client refactoring #727 @Андрій Солук
Fixed data race in introduce protocol @Андрій Солук
Introduce protocol client implementation #657 @Андрій Солук
Added dependency interface to Client #724 (on review) @Андрій Солук
Custom mock was replaced with gomock (introduce protocol) (on review) @Андрій Солук
Refactor state tests #707 @Talwinder Kaur
Create a connection between request and invitation, Sign the Exchange response with Invitation RecipientKey #issue-676, #issue728 @Talwinder Kaur
Add support for public dids in did-exchange protocol #561 (@Sandra Vrtikapa)
Documentation, examples for didexchange client(@Sandra Vrtikapa)
Verifiable Credential follow-up issues #514, #712 (@Dmitriy Kinoshenko)
JWT from Verifiable Credential with ES256K (secp256k1) signature #381 - in progress (@Dmitriy Kinoshenko)
Support environment variables in addition to command line arguments (#473) - Complete (@derektrider)
Grooming stories for issue-credential/ making technical flow diagram - In progress (@derektrider)
0.1.0 documentation - Running aries-agentd/CLI and webhooks - In progress (@derektrider)
Minor fixes, linters and restructuring in bddtests & aries-agentd go module #738, #584, #713, #686, #648 (@Sudesh Shetty )
Get all connections #429 (@Sudesh Shetty )
Refactor Keys structure in KMS #596 - in progress should finish soon (@Baha A Shaaban )
Grooming updates (from the previous week)
Upcoming work
Consolidate creator, storage and resolver DID under VDRI #777 - @Firas Qutishat
Define clear relationship between framework and context #212 - @Firas Qutishat
Continue working on design for issue-credential implementation. Need to figure out the format for request-credential (@derektrider)
externalAddr scheme can be set by user #747 (@derektrider)
DidExchange -Errors #112 (@Talwinder Kaur)
Implicit Invitation #718 (@Sandra Vrtikapa
Implement service behavior according to Client dependency (introduce protocol) @Андрій Солук
event tech debts @Rolson Quadras
JWT from Verifiable Credential with ES256K (secp256k1) signature #381 (@Dmitriy Kinoshenko)
Refactoring creation of serialized JWT from Verifiable Credential #339 (@Dmitriy Kinoshenko)
Design discussion
Showed first draft of issue-credential technical flow. More work to be done (@derektrider)
DIDExchange Request Msg - Empty label
Milestone progress
TBD
Other business
TBD
Future topics
TBD