/
2022-08-30 Indy Contributors Call

2022-08-30 Indy Contributors Call

Aug 30, 2022

Zoom Link: https://zoom.us/j/99220079317?pwd=OHk0U05ITnBkSmZ0aXlIQzFDYWg3UT09

Summary

  • Update on the Indy Ubuntu 20.04 Upgrade: Done?

  • Update on the "mixed node" problem

  • Update to DID Indy Method: Use a domain name for the "name" segment

  • Q&A

Recording of Call: dummyfile.txt



Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome and Introductions

Attendees

@Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

@Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>

@Christian Bormann (Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>

@Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>

@Char Howland (Indicio PBC) <char@indicio.tech>

Related Calls and Announcements

Release Status and Work Updates

Meeting Topics 

  • Update on the Indy Ubuntu 20.04 Upgrade – Done?

    • New release candidate – dev build is available, further updates are needed found from 16.04 release, needs to be tagged for RC

      • Add in recent updates to Indy

      • Review commit differences between main and 20.04 branches.

    • Sovrin Build – might be this week – should be copy/paste, although the pipelines take a long time to run (but 1/2 the time of the Jenkins pipelines!!!)

  • Root cause and solution to the "mixed node" problem: Indy Node issue 1769

    • Discussion of the short and long term handling of the issue.

    • Option 1: Just use the new "compat_set" merging from now on.

    • Option 2: Add a config transaction with a transaction number and use "compat_set" for earlier transactions, "sort" for ones after

    • Option 3: Versioning of transactions

    • Option 4: Option 1  for now, and revisit after we are live

  • Using a domain name (e.g. "sovrin.org") as the name segment of a `did:indy` identifier, per this GitHub Issue

    • Make it optional – the challenge for some will be in retaining a long lasting domain name

    • How to keep the two versions (domain hosted, one in did-indy-networks repo) of the genesis file in sync?

      • Idea – GHA that compares the two files and if they differ, creates a Pull Request to update the one in GitHub repo to match the one on the domain name.

      • Pull request must be reviewed and merged by the editors according to the governance – ensures there is a human step in the process

  • Action item: work on did-indy-networks

    • Include a static web generator so that we can publish a human friendly version of the information.

    • Include the governance guidance for the repo — who can merge and when?

  • Odd pipeline behaviour – test export jobs failing – perhaps a missing/wrong token?  Fail showing because of export fail but the tests are passing.

    • exports being used so that debugging can occur when tests fail.

    • Could we disable for PRs, but allow for internal builds.

  • Need to update the Indy read-the-docs documents

    • Project needed to provide updated docs

    • Would like to be on GH-Pages

    • Need to redirect from read-the-docs when the transition occurs

Future Calls

  • GDPR and the right to be forgotten – mitigations and approaches.

  • Status of Indy-SDK

    • Statement on the future of the Indy SDK: PR 2329

    • Plans for future of Indy CLI (move to Indy VDR?)

    • Indy SDK in test for Indy Node (move to Indy VDR?)

    • Status of GitHub Actions for the Indy-SDK

  • Indy bugs

    • Using GitHub tags "Good First Issue" and "Help Wanted" 

    • Node 1490: problems with large catch-up

    • Plenum 1506: view change message consensus calculation error

Action items