2021-09-14 Indy Contributors Call

2021-09-14 Indy Contributors Call

Summary

  • Status of indy-node CI/CD

  • Status of Ubuntu upgrade

  • Indy DID Method Repo

Recording from the call: 

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

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 (@Richard Esplin @Stephen Curran )

Meeting Topics

  • Update on CI/CD Update and Ubuntu Upgrade: Status Document

    • GitHub Issues

      • Indy-Plenum - issues – "2004" tag, including some help wanted

    • Indy-Plenum

      • Status: 

        • Adjusted pipelines to use the same flow, removed async parts

        • Updated Indy-SDK

    • Indy-Node

      • Status:

        • Updated per plenum, almost completed.

        • Both 16.04 and 20.04 are (almost) done

        • Next: PRs to be merged to update and remove pip<10 dependency, tricky to merge

    • indy-test-automation

      • Status:

        • Breaking the dependencies between this and Node/Plenum

        • Uses docker-in-docker to spin off the tests, run ledgers, etc.

          • Wade trying to get that to run locally, and then remove the circular dependency

            • Move tests from Node to Sovrin – where they should be. Eliminates the circular issue.

            • Make it a dependency only in Sovrin, not in Node

            • Wade to provide details on what needs to be done, opening up getting help from Robin and team and Philipp.

    • Sovrin Release - @Wade Barnes

      • Status: <To be completed>

      • ETA: ??

  • Indy DID Method specification repo: indy-did-method and the published spec: https://hyperledger.github.io/indy-did-method/

    • Huge thanks to Bosch for getting the work done! 

    • Needs some cleanup – the logo link and the Spec-Up dependabot updates.

    • And it needs to be reviewed, a backlog created and code written...

  • Indy SDK

  • Update: Indy to participate in the Linux Foundation Grace Hopper Day (Oct 1, 9-5am PT).

    • Hyperledger accepted as a group: Indy and Fabric

    • Indy needs 10-20 triaged, non-documentation, “good first issues” labeled and ready two weeks before each event.

      • Perhaps a number of the did:indy effort.

    • Provide 1 project representatives who are also maintainers of your project (e.g. can merge PRs), preferably women.

      • @Renata Toktarhas volunteered to represent Indy

  • Indy Contributor Campaign

    • Perhaps a foundation for this:

      • Indicio and Hyperledger talking about a joint venture for Indy certification

      • Perhaps an Indy workshop to get them through initial questions

    • Need a guide to setup dev environment, change a line of code, test locally, submit PR.

      • With the CI/CD to cover a lot of the details.

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

      • 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