Date: Fri, 29 Mar 2024 12:04:44 +0000 (UTC) Message-ID: <1287654816.12047.1711713884306@aws-us-west-2-hyp-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12046_2118671739.1711713884306" ------=_Part_12046_2118671739.1711713884306 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Indy is a healthy project. Indy=E2=80=99s codebase has
A recent focus has been on breaking up the single indy-sdk client = tool into separate components:
These new libraries provide an easier, more modular integration fo= r Aries Agents (the primary consumers of indy client artifacts) and are mor= e accessible for developers wanting to contribute to the project and use th= e artifacts of the project. Work has started on an Aries Secure Storage rep= ository that on completion will enable the depreciation of the indy-sdk in = favour of these new components.
Work has also begun on the number one request from the Indy commun= ity=E2=80=94a =E2=80=9Cjurisdiction-scale=E2=80=9D verifiable credential re= vocation mechanism.
As well, a plan has been formulated (but not yet executed) for mig= rating the Indy (especially the indy-sdk) CI/CD pipelines from their curren= t Jenkins-basis to GitHub Actions.
We continue to track some of the same issues as in previous quarters.
Update:
Modest progress with this effort in the past quarter.
Future work planned:
Update:
A plan was for= mulated for transitioning from the current Jenkins-based pipeline to GitHub= Actions with the option of tactical deployment of Azure Pipelines. T= he necessity to get off of Jenkins has increased because of the current rel= iance on Sovrin Foundation=E2=80=99s AWS resources that are at risk because= of the financial status of the Foundation. Resources from BC Gov have been= identified for the first part of the work, but it=E2=80=99s not their high= est priority, and little progress has been made to date. Access to resource= s from other teams have decreased for the next few months because of COVID-= 19 related projects.
Future work planned:
Update:
As agent implementers have moved to the Aries project, Indy was le= ft with few contributors to the ledger, mostly from a single organization. = The health of the project requires broadening this list. Progress on that g= oal was made this quarter as many of the contributions have come in from ne= w core developers and project leads from other organizations (notably, BC G= ov, Kiva and Mattr Global). The transition off of Jira and onto GitHu= b Issues was a step in trying to expand contributions by making it easier t= o see where contributions would be welcomed. The first GitHub issues = raised have attracted some attention, so initial feedback on the change is = positive.
Future work planned:
February 2020:
In the past quarter, efforts have been largely focused on creating= replacement components for the indy-sdk, enabling its depreciation of favo= ur of several separate components. Verifiable Credential Revocation 2.0 wor= k has started, building on the cryptography built into Ursa. A preliminary = design has been defined and tech spikes started to evaluate the feasibility= of that plan. Plans for migrating from Jenkins to GitHub Actions-based CI/= CD have been formulated but not executed.
Revocation, continued working on breaking up the indy-sdk, and the= migration of CI/CD pipelines will be the primary focus of efforts this qua= rter. Most of the work will have to be done with limited input from the pre= vious core team (who are busy on other projects in the space), which will b= e an interesting experiment. That said, Indy is very stable right now, and = there is not a pressing need from the community for a lot more than is bein= g planned.
The bi-weekly Indy Maintainers call continues to be the medium by = which maintainers coordinate work, discuss critical issues to the Indy code= base, and agree on HIPEs. A recent increase in the number of participants o= n the call has been encouraging, although that has yet to translate into mo= re commits from outside developers.
COVID-19 efforts have restricted Evernym from being able to contri= bute significantly to the code base in recent weeks and that is anticipated= to go on for the next few months. The Sovrin Foundation was forced to let = go of their paid staff (including Indy contributors) and is operating on a = volunteer basis. While that has slowed down efforts on the project, t= he current highest priority items (mentioned earlier - revocation, the brea= k-up of the indy-sdk and the CI/CD migration) continue to move forward thro= ugh the efforts of other contributors and key guidance from the Evernym tea= m.
Join the Indy Mailing List: https://lists.hyperledger= .org/g/indy