Summary
Expected topics
- Updates: PostgreSQL wallet storage, Maintainership requirements, incomplete request format refactor, Indy / Aries split
- Ursa and AMCL: Discussed in the Ursa call (August 21), but no decision yet.
- Handling pull requests.
Timezone: US afternoon and APAC morning
We intend to record this call.
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
- Name (organization) <email>
Announcements
- Community project: Aries RFCs - process to move HIPES; RFCs that have been moved concepts / features / pull requests.
- Aries Workshop/Connectathon December 3-5 in Provo, Utah (details to follow)
- Internet Identity Workshop
- Hyperledger Maintainers Summit: Minneapolis October 8-10
- Bootcamp Russia: Event Location
Summary of Prior Call
Release Status
- Indy Node
- August: 1.9.2
- Bug fix release
- Important bug fix for ledger corruption INDY-2211
- Recovery complicated by https://sovrin.atlassian.net/browse/SN-7
- September: 1.10.0
- PBFT view change
- Indy Node and Indy Plenum support for Ubuntu 18.04
- August: 1.9.2
- Indy SDK
- August: 1.11.1
- Finish Authors vs Endorsers
- Finish proof of possession of payment address
- Platform Updates: Ubuntu 18.04
- September: 1.12.0
- Fully qualified DIDs
- Dependent on DIDDoc support? (Daniel's document and David Huseby's work)
- Platform Updates: MacOS, CentOS
- Fully qualified DIDs
- Future
- GitLab migration alongside Jenkins (Foundation)?
- Aries / Indy split
- Anoncreds 2.0 (Sovrin Foundation, BC.gov?)
- August: 1.11.1
- Ursa
- Working on release of 0.2.0 (September / October)
- ZKP / ZKLang improvements
- Debian packages
- Refactor internal plumbing for anoncreds 2.0, shouldn't impact external interfaces
- Refactor multi-signature BLS in addition to aggregated signature
- Working on release of 0.2.0 (September / October)
- Aries
- Lots of progress on language libraries, frameworks, and agents.
- Indy Catalyst
- Production deployment testing: volume loads.
- Won't go live in production at BC.gov until October.
- Not yet migrated to Hyperledger. Needs more documentation.
Work Updates
- 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#
- Finishing work on ReadTheDocs (2 more weeks?)
- Cloud Compass is building the Linux Foundation EdX courses for Indy and Aries
- SDK 2.0 architecture / Indy-Aries split (Sergey)
- Anxious to start moving, and iterating.
- GitLab migration (Mike and Steve G)
- Demos in the Identity Implementers WG calls
- 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.
- 5 additional objects need to be added.
- Working on the HIPE for the new Schema object.
- Warnings from rust cargo clippy (Mike and Axel)
- 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.
- Getting Ursa artifacts published that can be used by Indy Node and Indy SDK (Mike and Cam)
Other Business
- Ursa and AMCL: Discussed in the Ursa call (August 21), but no decision yet.
- Architecture questions for Indy SDK, and progress on Indy / Aries split
- Handling pull requests.
- How to handle old pull requests that failed DCO Checks? Close?
- How to handle pull requests for IOS / Swift wrappers? Close and encourage the move to Aries?
- How to handle pull requests for LibVCX? Deprecate?
- Close PR https://github.com/hyperledger/indy-sdk/pull/1048 as something that will be replaced by the advanced schema work?
- HIPE pull requests: https://github.com/hyperledger/indy-hipe/pulls
Future Calls
- Define pull request review process for Indy Node.
- Should define the process, including how we handle exceptions (emergency fixes shouldn't be blocked, but would require notification)
- What is important in a good review?
- Fully Qualified DID support in Indy SDK
- fuzzing libindy https://github.com/AxelNennker/indy-sdk/tree/fuzzing/
`cargo +nightly fuzz run fuzz_target_1 -- -only_ascii=1`
Worried about unsafe code in libindy
```
ignisvulpis@namenlos:~/development/hyperledger/indy-sdk/libindy$ find src -name \*\.rs -exec fgrep unsafe {} \; | wc -l
61
```
Action items
- HIPE #138, Issue #144 (Ken and Brent)
- Create a PR for changing status to ACCEPTED
- Check for an Aries RFC