Versions Compared

Old Version 1

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version Current

changes.mady.by.user Richard Esplin

Saved on

Key

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

Summary

Excerpt
  • Status of indy-node CI/CD
  • Status of Ubuntu upgrade
  • Indy Contributors Campaign

Recording from the 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.

Welcome and Introductions

...

  • Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
  • Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
  • Robin Klemens (Institute for Internet Security) <klemens@internet-sicherheit.de>
  • Richard Esplin(Evernym) <richard.esplin@evernym.com>
  • Lynn Gray Bendixsen(Indicio) <lynn@indicio.tech>

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
      • Status: <To be complete> 
        • PRs to be merged - lint, and latest image, structure change for Artifactory - review for merge assigned to Wade
      • Security issue around Pygments – but it is only used in the docs, not in the code.
    • Indy-Node
      • Status: <To be completed> 
        • Main focus of work
        • Philipp created docs on new Indy node network, several other PRs
          • Catch-22 – update base images for builds, but the images need the changes to be tested. Oh my...
            • Pull images, make images updates local, push locally
        • Moments ago – Robin: CI working with all but one test working.
    • indy-test-automation
      • Status: <To be completed>
        • Relies on docker-on-docker, which is challenging; working on getting it running
        • Circular dependencies, even for indy-node testing (trying to pull in post-release Sovrin dependencies)
          • Breaking the dependencies could break some tests
          • Idea is to move those tests to later in the process
    • Sovrin Release - Wade Barnes
      • Status: <To be completed>
      • ETA: ??
  • 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
    • Release needed for Android issue #2382?
  • Issue with Indy Sandbox BCovrin Test
    • Update from Wade Barnes
    • No ledger corruption (pheww...)
    • Issue tied to RocksDB and/or Python Wrapper that was deployed
    • By updating one/downgrading the other got the ledger running again.
    • Issue not just RocksDB/Wrapper (version) but also how they are used in the plenum startup code, yet the latest Read Ledger code either one works
      • TBD: What is different in the Read Ledger code and the Indy startup code?  Digging into that to see if there is not a hidden issue
      • Read Ledger is a script in Indy Node to read the ledger offline.
  • Update: Invitation for Indy to participate in the Linux Foundation Grace Hopper Day (Oct 1, 9-5am PT).
      A project with 30-100
    • Hyperledger accepted as a group: Indy and Fabric
    • Indy needs 10-20 triaged, non-documentation, “good first issues” labeled and ready two weeks before each event.
      • Perhaps a number of the did:indy effort.
    • Provide 2 1 project representatives who are also maintainers of your project (e.g. can merge PRs), preferably women.
  • Indy Contributor Campaign
    • Perhaps a foundation for this:
      • Indicio and Hyperledger talking about a joint venture for Indy
      Should hear back next week on whether Indy is selected
      • certification
      • Perhaps an Indy workshop to get them through initial questions
    • Need a guide to setup dev environment, change a line of code, test locally, submit PR.
      • With the CI/CD to cover a lot of the details.

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
      • 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.

...