2022-03-01 Indy Contributors Call
Summary
Before this meeting: did:indy DID Method Meeting
Status of indy-node CI/CD and the Ubuntu upgrade
Tentative: new indy-node-container repo
Recording of Call:
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
@Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
@Lynn Gray Bendixsen(Indicio, PBC) <lynn@indicio.tech>
@Hakan Yildiz (Technische Universität Berlin) <hakan.yildiz@tu-berlin.de>
@Sean Bohan (Hyperledger) <sbohan@linuxfoundation.org>
@Philipp Schlarb (esatusAG) <p.schlarb@esatus.com>
Related Calls and Announcements
The move to Discord is done...
Invitation: https://discord.gg/hyperledger
Release Status and Work Updates
Indy Node
GitHub actions led by @Wade Barnes
Phillip Schlarb has joined Wade and Robin to help here. Thanks!
Decluttering and outsourcing of the GHA tasks to be reusable with different Pipelines
Ubuntu 20.04 upgrade led by @Robin Klemens
mixed env issues are being worked on (16.04 and 18.04 nodes) if the issues persist there will be upgrade concerns.
Sovrin Updates @Wade Barnes
New branching model led by @Wade Barnes
old branching model was cumbersome and error prone. New model will keep branching to a minimum. (fewer conflicts expected)
indy-node-container Crisitan Kubis ( https://github.com/tsurai ), has created a Node Controller Container (docs), allows containerized indy nodes to participate in pool restart and upgrade
Indy SDK
GitHub actions led by @Patrik Stas
Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
has been split to a fully api model: https://github.com/hyperledger/indy-node-monitor/issues/36
Indy/Aries Shared Libraries - Hyperledger (indy-vdr, indy-shared-rs, aries-askar)
Ursa
Hyperledger Contribution Campaign ( @Stephen Curran )
Indy DID Method – https://hyperledger.github.io/indy-did-method/
Meeting Topics
Before the meeting: "did:indy" DID Method
Separate meeting held prior to this one.
Update on CI/CD Update and Ubuntu Upgrade: Status Document
Indy-Plenum Status:
Done, 16.04, 20.04, Jenkins and GHA
Indy-Node Status:
Done, 16.04, 20.04, Jenkins and GHA
One 20.04 running in the IDUnion network of 16.04 nodes
Preparing and executing the automated release process.
indy-test-automation Status:
Working systemd image for 20.04, but the tests are not working – client messages not getting to the server.
Developer tools
indy-node-container (moved to Hyperledger) and GitPod tools available (node and plenum)
On plenum – error with building the dev containers about Indy SDK version – need to get the metadata version correct (https://github.com/hyperledger/indy-sdk/issues/2473)
Philip raised a question on this, but no one had the info for an answer yet.
Indy-SDK build progress
Unblocked – builds are going and PRs are being reviewed (and rebasing PRs).
AnonCreds Standardization Working Group
Future Calls
Issues that could impact indy-node on 20.04
indy-sdk: needs an upgrade to OpenSSL 1.1 to properly support Ubuntu 18.04/20.04. For indy-node, just using indy-sdk as is.
Multiple libsodium versions could impact consensus – intermittent issue on a mixed network.
Plans for a new Indy-SDK release?
A few people from the community have asked.
The most recent request has been for a release to include this feature; https://github.com/hyperledger/indy-sdk/pull/2400
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.