Summary
<Will add after the call>Timezone: US morning and Europe afternoon
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
- June: 1.9.0 Pluggable Request Handlers
- Testing is at risk for June
- July: 1.9.1
- Bug fix release
- August: 1.9.2
- Bug fix release
- September: 1.10.0
- PBFT view change
- June: 1.9.0 Pluggable Request Handlers
- Indy SDK
- June: Indy SDK 1.10.0
- Flexible Credential Attribute Tagging (BC.gov)
- Bugfixes
- July:
- GitLab migration alongside Jenkins (Foundation)?
- Linux should be ready, maybe Windows.
- Need a plan for mobile devices.
- Could run it right after the release.
- LibVCX without agency
- GitLab migration alongside Jenkins (Foundation)?
- August
- Platform Updates (Evernym?)
- Aries / Indy split (Evernym will help with architecture)
- Anoncreds 2.0 (Sovrin Foundation, BC.gov?
- June: Indy SDK 1.10.0
- Ursa
- June: 0.1.2
- Exposing the existing functionality over a C-API for the Aroha team.
- 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
- Initial code migration
Work Updates
- Documentation improvements: Michael B and Stephen C
- Start with new developer path through 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#
- SDK 2.0 architecture (Sergey)
- Payment decorator (Sergey)
- GitLab migration (Mike and Steve G)
- 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
- Merge this call with the Indy SDK working group calls, keeping them in the Monday slots for alternating timezones?
- Documentation improvements: (a conversation for the US / Europe group, already had it with US / Asia)
- Start with the "new developer on Aries" path, and then decide what developers need to know about Indy
- Where to document changes? HIPEs/Repo Docs/Jira Tickets
- PR's should link back to Jira tickets
- Rocket Chat questions should be pushed to Stack Overflow