You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Summary

Planned:

  • Status of indy-node CI/CD
  • Status of Ubuntu upgrade
  • Status of completed indy-sdk release and follow up tasks
  • Indy DID Method Spec – actions

Recording from the call: <To Be Added>


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

Related Calls and Announcements

Release Status and Work Updates

Meeting Topics

  • Update: 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 - waiting on Plenum
    • CI for Indy Plenum - merged
    • CD for Indy Plenum - draft done - the publishing is not added, but will be – fairly easy - Issue 1526 (Robin - DCO)
    • CI/CD for Indy-SDK looks good – paused - ready to move forward (ABSA work).
    • Sovrin Release - Wade Barnes
      • Working on CI/CD
      • Will be adding Ubuntu 20.04 support
    • 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 – 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.04Renata Toktar and 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
  • 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)
  • 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.
  • 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









  • No labels