Page tree
Skip to end of metadata
Go to start of metadata

Projects

Distributed Ledger
Client Tool
Shared Components

Project Health

Indy is a healthy project, particularly at the deployments and business interest level, but continues to be short on contributors.  Interest has increased in the quarter, with more contributors on the specific initiatives of the team, and a lot more participation as the bi-weekly the Contributors meeting. The current work focuses on modernizing the CI/CD process to use GitHub Actions (and eliminate reliance on specific people and infrastructure) for indy-node, indy-plenum and indy-sdk, and upgrading the dependencies for indy-node artifacts to run on Ubuntu 20.04. Coming soon will be a code-focused effort to add support for the new "did:indy" DID Method that will align Indy with the pending W3C DID Core Specification.

A new repository was added to indy, contributed by the Government of British Columbia – indy-shared-rs – which is a client library that provides in Rust a set of utilities for interacting with an Indy ledger. It is part of the process of breaking up the indy-sdk.

Per the Indy Activity Dashboard (2020-11 to 2021-01), there were 52 commits from 15 contributors. which is in line with the last quarter. I don't think those statistics include the indy-shared-rs library.

Questions/Issues for the TSC

Issues from previous reports:

Build Pipelines

Update: Good progress is being made on converting the CI/CD pipelines from Jenkins to GitHub Actions, for indy-node, indy-plenum and indy-sdk. This has been the focus of the community during this period as without this, the ability to release products is extremely limited.

Diversity of Contributor Community

Update: This remains a top of mind issue with the maintainers.  On the last Indy Contributors call, we are considering a "Contributor Campaign" in conjunction with Hyperledger Staff to build attention to both Indy and the new "did:indy" DID Method.

Releases

None.

Overall Activity in the Past Quarter

In the past quarter, ledger code development has slowed as we focus on code management – upgrading the Indy Node and Plenum CI/CD pipeline and upgrading Indy Node to run on Ubuntu 20.04.  The main code related activity was done by a team focused on being able to remove ledger plugins from a running instance of Indy.

Work continues on defining the Indy DID Method, with some good progress being made.  We're nearing completion of that work – and nearing a need for some new ledger code development efforts, particularly in Indy Node.

A release of the Indy SDK has been prepared and will be released shortly. As well, the Indy SDK CI/CD pipelines have been migrated to GitHub Actions and the existing pipelines will soon be retired.  As well, the Verifiable Credential Exchange (VCX) component of the Indy SDK has been pulled from the Indy SDK and moved to it's own repo in Aries. The code was focused on Aries protocols, and so the move makes a lot of sense.  This continues to the trend towards Indy just being a ledger for decentralized identity and the Trust over IP stack vs. covering the Agent and above layers of the stack.

As noted above, a new component, indy-shared-rs was contributed to better support agents that want to interact with Indy ledgers without depending on the entire Indy SDK.

Current Plans

The push will continue this quarter to complete the new CI/CD Indy Node and Plenum pipelines, and the Ubuntu 20.04 upgrade. In parallel, we'll try to wrap up the "did:indy" DID Method specification and generate a backlog of work to be added to Indy Node.  We anticipate that next quarter, with the ability to easily release code, addressing the DID Method backlog will be the focus.

Maintainer Diversity

The bi-weekly Indy Contributors call continues to be the medium by which maintainers coordinate work, discuss critical issues to the Indy codebase, and agree on HIPEs. The core maintainers are in close contact, and the new maintainers are gaining experience and confidence with the components.

Contributor Diversity

We've had several organizations join the Indy Contributors call and some are doing the work on the upcoming release (code changes) and the CI/CD pipeline. Interest in Indy has been rising because of the demand for verifiable credentials related to the various COVID-19 use cases, such as travel and back to work plans.

Additional Information

Reviewed by