Versions Compared

Old Version 1

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version Current

changes.mady.by.user Troy Ronda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Projects

Distributed Ledger
Client Tool
Shared Components

...

Per the Indy Activity Dashboard, Indy’s codebase has 21,028 commits from 238 unique contributors. This quarter there were 61 commits from 8 contributors.

Questions/Issues for the TSC

We continue to track some of the same issues as in previous quarters.

Measuring the size and make-up of our user community

Update: Thanks to the awesome work of Ry Jones, the Indy Activity Dashboard shows the activity in the Indy community.

Build Issues

Update: No Progress - issue repeated.

...

  • We need a new commitment from the various teams who have expressed interest.

Diversity of Contributor Community

Update: No progress - issue repeated.

...

Releases

June 2020:

Indy Node 1.12.3
  • A response to an identified security vulnerability that if exploited could take down an Indy network instance.

Overall Activity in the Past Quarter

In the past quarter, ledger development has slowed to the release of a security fix. Some work has occurred in the indy-sdk, but no releases are planned. The difficulty in releasing is a challenge for the community.

Current Plans

There is little ledger activity occurring. Previous work on "rich schemas" to support W3C VCs has been put on hold and will likely be replaced with a focus on BBS+ ZKPs, which likely has the benefit of eliminating (well, deprecating) features from Indy vs. adding. Our focus for client libraries is to break LibIndy into separate components that can be evolved to fit the proposed Aries architecture. Work on an improved revocation has progressed slowly, delayed within the Ursa community.

We are planning an "Indy Interop-a-thon - Making "Network of Networks" Real" virtual conference.  Details of the goal of the conference can be found in the link.

The need for a better CI/CD solution is rising. There are currently no active maintainers available to drive releases. Resources can be called on for help, but there are no active participants available to do that independently.

Maintainer Diversity

The 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 Maintainers who work exclusively on Indy is decreasing as many of them move on to help with the Hyperledger Aries project. We are hoping the Indy virtual conference in September will trigger an increase in maintainers.

Contributor Diversity

The team at British Columbia Government is leading the effort to evolve LibIndy, although that is largely at the lower levels – not yet in Indy (e.g. at the Rust crates layer). ABSO continues to contribute, as do members of several other organizations.

Additional Information

Reviewed by

  •  Angelo De Caro
  •  Arnaud J Le Hors
  •  Christopher Ferris
  •  Dan Middleton
  •  Gari Singh
  •  Hart Montgomery
  •  Mark Wagner
  •  Nathan George
  •  Swetha Repakula
  •  Tracy Kuhrt
  •  Troy Ronda