Page History

Summary

Timezone: US morning and Europe afternoon

...

• Name (organization) <email>
• Sam Curren (Sovrin Foundation) <sam@sovrin.org>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Samuel Smith (Sovrin Foundation) sam@samuelsmith.org
• Tomislav Markovski (Streetcred) tomislav@streetcred.id

Announcements

• Indy SDK call being cancelled

Summary of Prior Call

Release Status

• Indy Node
  June
  • • Early July: 1.9.0 Pluggable Request Handlers
    Testing is at risk for June
    • • • CI / CD problems left us broken for days. Release is likely to be next week.
      • July: 1.9.1
        • Bug fix release
        • Still trying for late July
      • August: 1.9.2
        • Bug fix release
      • September: 1.10.0
        • PBFT view change
    • Indy SDK
      June
      • • Early July: Indy SDK 1.10.0
          • Flexible Credential Attribute Tagging (BC.gov)
          • Bugfixes
          • CI / CD problems left us broken for days. Release is likely to be late this week.
        • Late 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 (Evernym)
        • August
          • Platform Updates (Evernym?)
          • Aries / Indy split
      (Evernym will help with architecture)
      • • • Anoncreds 2.0 (Sovrin Foundation, BC.gov?)
      Ursa
      •  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
      Aries
      •  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.

      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#
      • SDK 2.0 architecture / Indy-Aries split (Sergey)
        • http://jira.hyperledger.org/browse/IS-1285 
      • Payment decorator (Sergey)
        • Tomislav has some feedback that should be incorporated
      • GitLab migration (Mike and Steve G)
        • Evaluated Circle CI, but it doesn't support Windows
        • Blocking various platform updates and CI / CD improvements
      • 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.
          • https://github.com/hyperledger/ursa-docs/tree/master/specs/anoncreds2
        • 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

      Other Business

      • Call mechanics:
        • Merge this call with the Indy SDK working group calls
      , keeping them in the Monday slots for alternating timezones?
      • • Timing: move afternoon call later to pick up more of Asia
          • No change at this point
        • Frequency of the call: move to every week alternating timezones
          • No change at this point
        • Will begin recording the call
      • 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 / GitHub issues
          • Goal is for each PR to link to somewhere that includes additional context / underlying motivation
          • Exclude RFC and HIPE repos
          • Need to revisit Hyperledger's policy on GitHub issues
        • Rocket Chat questions should be pushed to Stack Overflow
      • Recording transaction endorsers and INDY-1999

        • Jira
          server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key INDY-1999

      Next Week

      Action items

      Call Recording

      ...