...

Indy is a healthy project. Indy’s codebase has 23962 commits from 177 unique contributors. This represents an increase of 7 contributors this quarter and about 2,000 additional commits. We had commits from 41 different authors in the last three months. Forums and chat channels are monitored and a variety of participants are contributing helpful responses to questions.

...

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

Incompatible agent implementations

Update:

The launch of project Aries had the intended effect of focusing attention on standards for agent implementations. We will continue to support that effort as we migrate portions of Indy SDK into Aries core libraries. We will not be tracking this as an issue in our future quarterly reports.

Measuring the size and make-up of our user community

We are paying attention to key metrics, but have not yet established a formal method of tracking specific progress. This is an area where Hyperledger could assist.

Progress made:

...

Update:

We played a bit with tools for counting contributors, but no other significant progress.

Future work planned:

• We expect that the Indy contributor community will continue to shrink as much of the attention shifts to Aries.
• Work with Hyperledger to get analytics about web sites, and Rocket Chat usage. 
• Begin measuring usage of the Sovrin forums: new contributors, questions asked, and questions answered
• We will also explore the use of Githubs Github's contributor tool. 

Build Issues

Update:

Our We continue to transition to a the GitLab CI build pipeline using resources contributed by the developer community and managed by the Sovrin Foundation .

Progress made:

• The team at the Sovrin Foundation is making progress reimplementing the pipeline for Indy-SDK using Gitlab CI.

Further remediation planned:

is going slower than expected. The Indy SDK pipeline is complex, and GitLab's integration with GitHub is not yet mature. We have found credible solutions to the problems we have seen, but the project has not had sufficient developer focus to come to completion. We are still relying on the Jenkins instance managed by the Sovrin Foundation for our production CI / CD pipeline.

Future work planned:

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

Visibility of Plenum as a Ledger

Over the past year, Indy has successfully spun out Ursa and Aries as stand-alone projects. Each of these projects benefited from new contributors and increased enthusiasm. Indy also benefited from increased focus on its role as an identity ledger. We would like to see the same benefits accrue to the Plenum ledger. Plenum is a mature, general purpose, distributed ledger. Its features, performance, and production stability compares favorably with other ledgers. Yet we currently only talk about it in terms of Indy Node, limiting the users and contributors to those with an interest in identity use cases. We have found that there are currently very few people in the identity ecosystems with the skills and interest necessary to contribute to Plenum, and we need to broaden the base of users and contributors in order to ensure its viability.

If Plenum leaves Indy, then Indy is a smaller and more focused project. Indy will consist of the identity primitives and server configuration for Plenum. It will be easier to understand and contribute to.

Future work planned:

• Complete the New Project Proposal for Plenum.
• Recruit additional contributors.
• Improve the ease of running Plenum independent from Indy NodeOther teams are committed to help move the other Indy pipelines to the GitLab infrastructure.

Releases

August 2019:

Indy SDK 1.11.0

...

• Minimal EXPERIMENTAL support of Fully-Qualified identifiers:
  • omit or set "1.0" to use unqualified identifiers.
  • set "2.0" to use fully qualified identifiers.
  • added correspondent did qualify command to Indy-CLI.
• general format of fully-qualified identifier is <prefix>:<method>:<value>.
• extended did_info parameter of indy_create_and_store_my_did function to accepts optional method_name filed. This field should be used to create fully qualified DID.
• all functions can work with fully-qualified identifiers (new way) as well as with unqualified.
• added a new function -- indy_to_unqualified -- that gets unqualified form of a fully qualified identifier.
• proof requests now support versioning (ver field) -- now it specifies whether restrictions are full qualified or not.
omit or set "1
• .
0" to use unqualified identifiers.
• set "2.0" to use fully qualified identifiers.
• The same format of identifiers will be used in generated proof and must be used for proof verification.
• added a new function -- indy_qualify_did -- that updates DID stored in the wallet to make it fully qualified, or to do other DID maintenance.
• added correspondent did qualify command to Indy-CLI.
• all functions in Ledger API can accept fully-qualified identifiers but always return results in an unqualified form.
• extended VCX provisioning config to accept optional did_method filed. This field should be used to create fully qualified DIDs.
• Migrated Android onto the API v21 and NDK 20.
• Supported MacOS builds for Indy CLI.
• The default value of Protocol Version was changed on 2. Henceforth indy_set_protocol_version function should be called if you are going to work with Indy-Node 1.3 and less.
• Bugfixes

...

Overall Activity in the Past Quarter

Our contributor community collaborates a lot on Jira issues, in pull requests, using Rocket Chat, and in weekly meetings. But we don't use the mailing list very much. We do not have clear analytics, but the majority of questions asked appear to receive answers within a few days.

Current Plans

Maintainer Diversity

...