Summary
- <Planned Topics>
Timezone: Europe afternoon and US morning
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
Summary of Prior Call
Release Status
- Indy Node
- Late July: 1.9.1
- Bug fix release
- Authors vs Endorsers (INDY-1999)
- Public write access (INDY-2171)
- Bug fix release
- August: 1.9.2
- Bug fix release
- September: 1.10.0
- PBFT view change
- Late July: 1.9.1
- Indy SDK
- Late July: 1.11.0
- Usability improvements to Indy CLI and Payments (Sovrin Foundation and Evernym)
- Requires concurrent release with libsovtoken
- Proof of possession of payment address
- LibVCX without agency (Evernym)
- Usability improvements to Indy CLI and Payments (Sovrin Foundation and Evernym)
- August:
- Finish Authors vs Endersors
- GitLab migration alongside Jenkins (Foundation)?
- Platform Updates (Evernym?)
- Future
- Aries / Indy split
- Anoncreds 2.0 (Sovrin Foundation, BC.gov?)
- Late July: 1.11.0
- Ursa
- June: 0.1.2
- Exposing the existing functionality over a C-API for the Aroha team.
- Not tagged in GitHub
- July: 0.2.0
- Refactor internal plumbing for anoncreds 2.0, shouldn't impact external interfaces
- Multi-signature BLS instead of aggregated signature
- June: 0.1.2
- Aries
- Agent from Indy Catalyst migrated to aries-cloudagent-python (BC.gov)
- Initial code migration from SDK repositories
- Indy Catalyst
- Migration from BC repos this week.
- Indy WG call - proposal to rebrand to Identity WG or Sovrin call to cover cross-project concerns (keep it every week and report on various project WG status and talk about cross-project issues and end-to-end integrations).
Work Updates
- Documentation improvements: Michael B and Stephen C
- Start with new developer path through Aries.
- First draft in aries-cloudagent-python from 0 to coding in Aries
- 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#
- Start with new developer path through Aries.
- SDK 2.0 architecture / Indy-Aries split (Sergey)
- Aries Working Group 2019-07-31-A
- http://jira.hyperledger.org/browse/IS-1285
- GitLab migration (Mike and Steve G)
- Evaluated Circle CI, but it doesn't support Windows
- Blocking various platform updates and CI / CD improvements
- Advanced Schemas and W3C creds (Ken)
- Warnings from rust cargo clippy (Mike)
- IS-1270 through IS-1274
- Will look at again in July
- 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
- Schedule for future calls
- Maintainership requirements for Indy Node and Indy SDK
- Ursa and AMCL
- New pack / unpack requires disclosure of recipient
- Proposed improvements to Indy Node architecture and PBFT view change