2021-09-28 Indy Contributors Call

Summary

• Status of indy-node CI/CD and the Ubuntu upgrade
• Indy DID Method – Review of the spec and getting started on the work

Recording from the call: dummyfile.txt

Welcome and Introductions

Attendees

• Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
• Robin Klemens (Institute for Internet Security) <klemens@internet-sicherheit.de>
• Lynn Gray Bendixsen(Indicio, PBC) <lynn@indicio.tech>

Related Calls and Announcements

Release Status and Work Updates

• Indy Node
  • GitHub actions led by Wade Barnes
  • Ubuntu 20.04 upgrade led by Robin Klemens 
  • Sovrin Updates Wade Barnes 
  • New branching model led by Wade Barnes
• Indy SDK
  • GitHub actions led by Patrik Stas
  • LibVCX tests are failing. Proposal is to deprecate LibVCX in the Indy SDK, and focus on aries-vcx.
• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
• Indy/Aries Shared Libraries - Hyperledger (indy-vdr, indy-shared-rs, aries-askar)
• Ursa
  • Appears that refactor has stalled? Need volunteers.
• Hyperledger Contribution Campaign ( Stephen Curran )
• Indy DID Method – https://hyperledger.github.io/indy-did-method/

Meeting Topics

• Update on CI/CD Update and Ubuntu Upgrade: Status Document
  • GitHub Issues to track:
  • Indy-Plenum
    • Status: 
      • Done
  • Indy-Node
    
    • Status:
      • Done
  • indy-test-automation
    • Status:
      • The circle is not (almost) broken – no Sovrin dependencies.
        • Need to find some docker-in-docker images – deprecated.
        • Need systmd as well – need to figure out how to beat.
      • Authentication issue – permissions on the .ssh files, also seeing permissions on GHAs
      • No dependencies on Sovrin, so that part is done.
  • Sovrin Release - Wade Barnes
    • Status:
    • ETA: ??
• Indy DID Method specification repo: indy-did-method and the published spec: https://hyperledger.github.io/indy-did-method/
  • What is in it?
    • A presentation of the highlights - Stephen Curran
  • Discussion:
    • What changes to Indy Node are needed?
    • Indy VDR?
    • Indy Node?

Future Calls

• Indy Contributor Campaign
  • Focus: Indy Generation Next
    • Audience: Organizations building Indy Instances, applications built on Indy
      • Not going for casual, independent developers, more on organizations that can assign developers to work on the project for a set chunk of time (e.g one month)
    • Key Features:
      • Indy network of networks support
      • Indy support for W3C DID Standard 1.0
    • Tasks:
      • Update NYM to support new "diddoc_content" data element
      • Indy-sdk, indy-vdr support for new "diddoc_content" data element
      • Indy DID Resolver support for new "diddoc_content"
      • indy-sdk, indy-vdr support for multiple ledgers
      • Support for new ledger object identifiers
      • Handling cred_defs that references schema on other ledgers
      • Possible: support for NYM "keri_keystate" data element, indy-sdk/indy-vdr support and DID resolver support
      • Other?
    • Foundational Work:
      • did:indy spec. as a spec.
      • Tasks in GitHub Issues - tagged for campaign
      • Getting started with developing indy-plenum and indy-node
        • Tutorial: Sample feature to add to indy-node
          • Example: rich schema feature flag
    • Campaign work
      • Landing page
      • Video: Intro to Indy Generation Next
      • Meetup channels

• Changes to indy-node needed for did:indy
• Status of Indy-SDK
  • Statement on the future of the Indy SDK: PR 2329
  • Plans for future of Indy CLI (move to Indy VDR?)
  • Indy SDK in test for Indy Node (move to Indy VDR?)
  • Status of GitHub Actions for the Indy-SDK
• Indy bugs
  • Using GitHub tags "Good First Issue" and "Help Wanted" 
  • Node 1490: problems with large catch-up
  • Plenum 1506: view change message consensus calculation error
• Hyperledger campaign to recruit additional developers.

Action items