Summary
| Excerpt |
|---|
Expected topics:
|
Timezone: US afternoon and Asia morning
...
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.
...
- Documentation improvements: Michael B and Stephen C
- Need to review and prune out-of-date documentation (Alice / Faber treatment of pairwise DIDs is a key pain point)
- Michael is working on Indy Agent walkthrough using C#
- SDK 2.0 architecture / Indy-Aries split (Sergey)
- GitLab migration (Mike and Steve G)
- Demo in the Identity Implementers call?
- Issues with Jenkins machines because Rust builds run out of memory—workaround increased build time but is a temporary solution
- Advanced Schemas and W3C creds (Ken)
- Can successfully write and retrieve the Context object from the node code. Will track through all layers up to Aries.
- https://github.com/ken-ebert/indy-node/commits/master
- Once unit tests work, will commit back either to Master or in a Branch.
- 5 additional objects need to be added.
- Can successfully write and retrieve the Context object from the node code. Will track through all layers up to Aries.
- Warnings from rust cargo clippy (Mike)
- IS-1270 through IS-1274
- New design for revocation / Anoncreds 2.0 (Mike)
- Would be useful to have a comparison in performance between Anoncreds 1.0 and Anoncreds 2.0
- First draft is latex document in Ursa repo. Will be published as PDF and HTML.
- Need a plan for changes to Indy Node
- HIPE for overall changes, then a design PR for the changes specific to the different repos.
https://github.com/hyperledger/indy-node/tree/master/design
- HIPE for overall changes, then a design PR for the changes specific to the different repos.
Other Business
- Ursa and AMCL
- New pack / unpack requires disclosure of recipient
- Cannot hide the receiver of the message like we could with msg_pack
- Allows having multiple recipients of the same message
- Should list the drawback in the Aries-RFC? Is there an alternative way that preserves the capability to selectively disclose the recipient?
- Ursa and AMCL
- Accepting HIPE PR #138, Issue #144
- Close PR https://github.com/hyperledger/indy-sdk/pull/1048 as something that will be replaced by the advanced schema work?
...