Summary
Excerpt |
---|
Planned:
|
Recording from the call:
...
20210316 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. |
---|
Welcome and Introductions
...
- 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 - active development - no official PR ready - waiting on Plenum
- Stable to Master merge
- In process, but reintroducing things that were deleted, reverting state
- Indy-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) - PR1526
- Stable to Master merge
- In process - some issues found, but PR resolves them - waiting for review
- Indy-SDK
- CI/CD for Indy-SDK looks good – paused - ready to move forward (ABSA work).
- Sovrin Release - Wade Barnes
- Working on CI/CD - Resource found for that, starting soon - Anmol Singh - contractor through Sovrin
- 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.
- Indy-Node
- 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
- All tests resolved
- CI-CD changes for plenum Ubuntu in progress / getting close
- Do we still need to build the deb files of rocksdb or can we directly use https://packages.ubuntu.com/source/focal/rocksdb at v. 5.17.2? In Ubuntu 16.04 we use rocksdb v. 5.8.8
- 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)
- Adding to the NYM transactions (write and read) a "diddocContent" item, instead of putting it into an associated ATTRIB
- 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.
- 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.
- repolinter - needs
...
- 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.
...