/
2021-03-02 Indy Contributors Call

2021-03-02 Indy Contributors Call

Mar 02, 2021

Summary

Planned:

  • Indy Contribution Campaign

  • Status of indy-node CI/CD

  • Status of Ubuntu upgrade

  • Status of completed indy-sdk release and follow up tasks

  • Questions from the Indy DID Method Spec team

Recording from the call: 20210302 Indy Contributors Call Recording



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

  • @name (Employer) <email>

  • @Richard Esplin(Evernym) <richard.esplin@evernym.com>

  • @Alexander Jonsson (Laniakea Health) <alex@seropass.me>

  • @Sebastian Schmittner (EECC) <sebastian.schmittner@eecc.de>

Related Calls and Announcements

Release Status and Work Updates

  • Indy Node

    • Functionality to remove tokens led by @Richard Esplin

      • Blocked by system test dependency on sovrin.deb

      • Will split Sovrin specific tests in indy-test-automation into separate repo in sovrin-foundation org

        • Will break the Sovrin Jenkins pipelines further. Best fix is to setup GitHub Actions pipeline for Sovrin deb.

    • GitHub actions led by @Kevin Griffin @Wade Barnes

      • We need a GHA pipeline for Ubuntu 16.04 and Ubuntu 20.04 so that we can test in both.

      • The Ubuntu upgrade must interoperate with the then-current 16.04 release, so that we can organize the "one node at a time" Steward OS upgrades.

    • Ubuntu 20.04 upgrade led by @Robin Klemens and@Ryan Marsh

    • New branching model led by @Wade Barnes

      • Documenting plan (HIPE?)

      • Merging Stable to Master (@Renata Toktar has a PR done)

      • Rename Master to Main

      • Releasing what is currently in Master

      • Evernym can help merge and test.

  • Indy SDK

    • Recent release in progress, led by @Ian Costanzo @Wade Barnes

      • Release done?

    • GitHub actions led by @Patrik Stas

    • Indy Node release needs a build of Indy SDK with freeze ledgers to do system tests. Currently blocked with publishing to pypi.

  • Indy Monitoring - https://github.com/hyperledger/indy-node-monitor

  • Indy/Aries Shared Libraries - donated to Hyperledger (indy-vdr, indy-shared-rs, aries-askar)

  • Ursa

  • Hyperledger Contribution Campaign (@Richard Esplin @Stephen Curran )

Meeting Topics

  • GitHub actions led by @Kevin Griffin @Wade Barnes  - We need a GHA pipeline for Ubuntu 16.04

    • CI for Indy Node - merged

    • CD for Indy Node - active development - no official PR ready

    • CI for Indy Plenum - merged

    • CD for Indy Plenum - draft done - the publishing is not added, but will be – fairly easy.

    • CI/CD for Indy-SDK looks good – ready to move forward (ABSA work).

    • Completion of Sovrin release to produce final artifacts – Alex K working on this.

      • PR-based pipelines now enabled by Wade

      • Sovrin CI/CD needed using the same pattern.

    • indy-test-automation – had been working, but it is dependent on the Sovrin packages that are not made yet.

    • We need to add someone to help with the Sovrin CI/CD based on the patterns established with Node and Plenum.

    • Need to research the publishing of the artifacts from GHA to the Sovrin repos – it's magic right now, needs to be brought into the open.

  • Next Indy-Node release – need CD completed.  Once done, then we can plan the final steps to produce a release.

    • Wade to work on a checklist for what is needed, and who is doing what for the initial release.

  • Ubuntu 20.04 Ryan Marsh (had a baby today – w00t!!) – @Renata Toktar taking the work, @Robin Klemens

    • Working on tests related to Python 3.8 upgrade – most are running, 4-5 to go, parallel looking at specific packages to be updated

  • PR from Indy-Node and Indy-Plenum Stable to Master - PR is ready for review - @Wade Barnes and others with experience.

    • Renata finished that – timely to shift to the Ubuntu release.

    • Can't test fully right now because of the Sovrin dependency.

    • Biggest challenge – handling DCO-less commits.

  • Indy Contribution Campaign

  • Questions from the Indy DID Method Spec team:

    • Adding to the NYM transactions (write and read) a "diddocContent" item, instead of putting it into an associated ATTRIB

      • Client left to assemble the DIDDoc, but need only read a single object

      • History Lesson: Why was the ATTRIB added vs. allowing optional data in the NYM?

      • Old Indy-SDK epic, old Indy epic, (must login to see epics)

  • Indy-SDK – done.  1.1.16 is in the wild!  Merge still needs to be done, but it's ready.  All other steps are done.

  • Can we merge HIPEs for helpers to remove plugins: PR 162 ?

  • Indy Node Maintainers.md, and CODEOWNERS in Indy Node and Indy Plenum

    • Updated CODEOWNERS list: WadeBarnes Toktar brentzundel esplinr sergey.khoroshavin, udosson, m00sey, ianco, and askolesov

    • Hyperledger standard Maintainers document?

    • Use GitHub groups instead of CODEOWNERS? Ry set this up. We just need to approve his changes.

Future Calls



Next call:

Future:

  • Changed to indy-node as 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