Should Indy CLI be part of indy-node or put into it's own repository.
Could it pulled out and put on indy-vdr?
Possibly post as a help wanted – pulling out of indy-sdk and into indy-cli
Plan for migrating Ubuntu 20.04 from a branch in Indy-Node and Indy-Plenum into Main.
This release is the last release that will support Ubuntu 16.04.
Need pipelines that support Ubuntu 20.04 LTS and Ubuntu 22.04 LTS.
After this release we can start decommissioning Jenkins.
Future Calls
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