2021-03-30 Indy Contributors Call

2021-03-30 Indy Contributors Call

Summary

Planned:

  • Status of indy-node CI/CD

  • Status of Ubuntu upgrade

  • Status of indy-sdk CI/CD

  • Indy DID Method Spec – actions

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>

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

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

    • Sovrin Updates @Wade Barnes

    • 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

    • 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

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

    • Indy-Node

      • CI for Indy Node - merged

      • CD for Indy Node - patterns from plenum have been implemented waiting on Plenum

      • Stable to Master merge - ready and being reviewed by Wade.

      • Ubuntu 20.04 Upgrade

        • Can we close the RMarsh PR in favour of later PRs?  Need to get a status of later PRs

          • Richard is indicating that it is done, but not clear. Tests are running under GHAs.

          • No CI so not clear how that is indicated.

          • Should we be merging to trigger CI/CD?

    • Indy-Plenum

      • CI for Indy Plenum - merged

      • CD for Indy Plenum - ready but not merged 

        • Waiting on Wade for where to put the artifacts - decision Hyperledger Artifactory - to be setup today/tomorrow.

        • Robin is on vacation through April 20.  May need to try to get someone else to work on this. Robin to add comment on GitHub issue with status.

        • In PR is ability to run the GHAs off different branches.

      • Stable to Master merge - Merged

    • Indy-SDK

      • CI/CD for Indy-SDK looks good – ready, Wade to review - waiting for Jenkins to sign off on the build (happening as we speak)

      • Jenkins/GHAs to run in parallel for a bit, while the GHA are finalized.

        • CI – deprecating that sooner than later

        • CD – need the right triggers to fire (e.g. if PR merges to master and updates the tag, publishes artifacts)

    • Sovrin Release - @Wade Barnes

      • Working on CI/CD - Resource found for that, starting soon - Devin Smith - contractor through Sovrin

      • Dev environment fixed, build environment fixed, tests fixed, working on the Ubuntu 20.04 upgrade

      • Should be done soon.

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

    • Need to research the publishing of the artifacts from GHA to the Sovrin repos

      • Before – indy and sovrin artifacts were in Sovrin repos

      • To Be Done – indy artifacts will be hosted on Hyperledger Artifactory; Sovrin on Sovrin repositories

  • 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.

  • Indy Contribution Campaign

    • Timing – HGF coming up –  timing perhaps best is after HGF

    • Video – 3 month lead time on that – Digital Identity

    • Look at second half of the year – but we need to get started

  • Indy DID Method Spec organizing

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

      • Per Sergey K – may want to use ATTRIB storage for the item instead of adding it to the NYM on the ledger

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

  • Status of indy-sdk CI/CD

  • DONE: 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.

  • Sovrin Network Upgrade process: 

    • Inputs: New CI/CD, OS Upgrade, Post Feb. 2020 functionality (e.g. Rich Schema), indy-crypto vs. ursa-crypto

    • Today: 16.04 with no post Feb 2020, Functionality, mix of indy-crypto/ursa-crypto

    • Release 1: Another 16.04 using the new CI/CD code but no code changes plus the Post-Feb. 2020 changes

      • Concern: Have the new GHAs been made ONLY for 20.04?  Not supposed to be, but TBD.

    • Release 2: Ubuntu 20.04 matching Release 1. One at a time – create new 20.04 node, remove their 16.04 node, add their 20.04 node

    • Release 3: Post Feb. 2020 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