Summary
Excerpt |
---|
|
Recording from the call:
...
dummyfile.txt
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>- Wade Barnes (Neoteric Technologies Inc. ) <wade@neoterictech.ca>
- Robin Klemens (Institute for Internet Security) <klemens@internet-sicherheit.de>
- Sebastian Schmittner (EECC)<sebastian.schmittner@eecc.de >
- Philipp Schlarb
- Hakan Yildiz
- Paul Bastian
- Ayush Raj
Related Calls and Announcements
...
- Update on CI/CD Update and Ubuntu Upgrade: Status Document
- Indy-Plenum Status:
- Done
- Indy-Node Status:
- Done
- indy-test-automation Status:
- Progressing. Tests are passing.
- Missing a systemd images for Ubuntu 20.04
- May need to create our own or updated the tests to not require the service arch.
- The image is used to mimic a real network as closely as possible.
- Sovrin Release - Wade Barnes Status:
- No schedule yet. Work needs to restarted.
- Indy-Plenum Status:
- Docker Container for Indy Node Server + Controller
- Crisitan Kubis ( https://github.com/tsurai ) of the Institute for Internet Security, member of ID Union, has created a Node Controller Container in order to let containerized indy nodes participate in pool restart and upgrade
- Modified controller files + Dockerfile: https://github.com/IDunion/indy-node-container/tree/main/controller
- Runtime Setup: https://github.com/IDunion/indy-node-container/blob/main/run/README.md#node-controller
Future Calls
- 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
- Indy Contributor Campaign
- Focus: Indy Generation Next
- Audience: Organizations building Indy Instances, applications built on Indy
- Not going for casual, independent developers, more on organizations that can assign developers to work on the project for a set chunk of time (e.g one month)
- Key Features:
- Indy network of networks support
- Indy support for W3C DID Standard 1.0
- Tasks:
- Update NYM to support new "diddoc_content" data element
- Indy-sdk, indy-vdr support for new "diddoc_content" data element
- Indy DID Resolver support for new "diddoc_content"
- indy-sdk, indy-vdr support for multiple ledgers
- Support for new ledger object identifiers
- Handling cred_defs that references schema on other ledgers
- Possible: support for NYM "keri_keystate" data element, indy-sdk/indy-vdr support and DID resolver support
- Other?
- Foundational Work:
- did:indy spec. as a spec.
- Tasks in GitHub Issues - tagged for campaign
- Getting started with developing indy-plenum and indy-node
- Tutorial: Sample feature to add to indy-node
- Example: rich schema feature flag
- Tutorial: Sample feature to add to indy-node
- Campaign work
- Landing page
- Video: Intro to Indy Generation Next
- Meetup channels
- Audience: Organizations building Indy Instances, applications built on Indy
- Focus: Indy Generation Next
- Changes to indy-node 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.
...