Page Comparison

Summary

Recording from the call:

...

 dummyfile.txt

Welcome and Introductions

...

• Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
• Ry Jones (Linux Foundation) rjones@linuxfoundation.org
• Richard Esplin(Evernym) richard.esplin@evernym.com
• Sebastian Schmittner (EECC) sebastian.schmittner@eecc.de

Related Calls and Announcements

...

• Update on CI/CD Update and Ubuntu Upgrade: Status Document
  • GitHub Issues
    • Indy-Plenum - issues – "2004" tag, including some help wanted
  • Indy-Plenum
    • Basically done CI/CD, 16.04 PR has been merged.  Artifact were published to https://hyperledger.jfrog.io/ui/repos/tree/General/indy%2Fpool%2Fdev%2Fi%2Findy-plenum%2Findy-plenum_1.13.0~dev106_amd64.deb
    • Python packaging is being added to the 16.04 branch
    • 20.04 PR ready to merge – final reviews for debian publishing
    • Next up is PyPi publishing (done for 16.04, repeat for 20.04 and update)
    Once done, we'll move to indy-nodeand 20.04
    • Still need to adjust the 20.04 publishing structure because of package collisions. - Robin
    • To be done post-publishing: https://github.com/hyperledger/indy-plenum/issues/1554
      • Things in Jenkins and not in GHA
    • Security issue around Pygments – but it is only used in the docs, not in the code.
  • Indy-Node
    • Work on Node was delayed due to the investigation of the hanging tests and the collaboration on the Python packaging.Work on Node should commence again this weekis happening here now
    • A loop in the test automation – need Sovrin packages to test node, but need node to release Sovrin packages.
      • Devin started on this, but it's not working yet.  Wade is focusing on that next.
  • indy-test-automation
    • Enable node testing without Sovrin dependencies.
    • Work will continue as/when needed.
    • TBD from Devin Smith – where was this left off.
  • Sovrin Release - Wade Barnes
    • Work will resume following the work on Plenum and Node.
    • Once it's complete, Evernym can test the release candidate.
    indy-test-automation
    • Work will continue as/when needed.
    • TBD from Devin Smith – where was this left off.
• Indy Plenum issuer reported: IC Queue getting quite large
  • Evernym has provided feedback and Dom is looking into things further on his end.
• Indy SDK
  • Async libindy https://github.com/hyperledger/indy-sdk/pull/2319 - what's the plan?
  • IndySDK LibVCX - should be removed from IndySDK?
    • Consensus - Yes 
    • PR for removal: https://github.com/hyperledger/indy-sdk/pull/2416
  • Should Indy CLI be part of indy-node or put into it's own repository.
    • Could it pulled out and put on indy-vdr?
    • Possibly post as a help wanted – pulling out of indy-sdk and into indy-cli
• Plan for migrating Ubuntu 20.04 from a branch in Indy-Node and Indy-Plenum into Main.
  • This release is the last release that will support Ubuntu 16.04.
  • Need pipelines that support Ubuntu 20.04 LTS and Ubuntu 22.04 LTS.
  • After this release we can start decommissioning Jenkins.
• Issue with Indy Sandbox BCovrin Test
  • Had been running for years, used by developers
  • Yesterday - crashed
  • On restart, it went into a startup crash loop – recovering and then aborted.
    • All nodes had the same issue.
  • Could read the config and pool ledger, but could not read the domain ledger.
  • Forced to reset the ledger to make it available again.
  • Backup taken and needs to be investigated.  How did we lose the ledger across all nodes?
• Invitation for Indy to participate in the Linux Foundation Grace Hopper Day (Oct 1, 9-5am PT).
  • A project with 30-100 triaged, non-documentation, “good first issues” labeled and ready two weeks before each event.
  • Provide 2 project representatives who are also maintainers of your project (e.g. can merge PRs), preferably women.
    • Renata Toktarhas volunteered to represent Indy
  • Should hear back next week on whether Indy is selected.
• Important bug in Indy SDK impacts Android wallets: https://github.com/hyperledger/indy-sdk/issues/2382
• Process for supporting IDunion Network
  • Contact Main Incubator to become an endorser.

Future Calls

• Indy Contributor Campaign
  • Focus: Indy Generation Next
    • Audience: Organizations building Indy Instances, applications built on Indy
      • Not going for casual, independent developers, more on organizations that can assign developers to work on the project for a set chunk of time (e.g one month)
    • Key Features:
      • Indy network of networks support
      • Indy support for W3C DID Standard 1.0
    • Tasks:
      • Update NYM to support new "diddoc_content" data element
      • Indy-sdk, indy-vdr support for new "diddoc_content" data element
      • Indy DID Resolver support for new "diddoc_content"
      • indy-sdk, indy-vdr support for multiple ledgers
      • Support for new ledger object identifiers
      • Handling cred_defs that references schema on other ledgers
      • Possible: support for NYM "keri_keystate" data element, indy-sdk/indy-vdr support and DID resolver support
      • Other?
    • Foundational Work:
      • did:indy spec. as a spec.
      • Tasks in GitHub Issues - tagged for campaign
      • Getting started with developing indy-plenum and indy-node
        • Tutorial: Sample feature to add to indy-node
          • Example: rich schema feature flag
    • Campaign work
      • Landing page
      • Video: Intro to Indy Generation Next
      • Meetup channels

• Changes to indy-node needed for did:indy
• 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
• Hyperledger campaign to recruit additional developers.

...