Versions Compared

Old Version 1

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version 2

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 Contributor Campaign

Recording from the call: 


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>
  • Richard Esplin(Evernym) <richard.esplin@evernym.com>

Related Calls and Announcements

...

  • Update on CI/CD Update and Ubuntu Upgrade: Status Document
    • Indy-Plenum
      • 16.04 PR ready to merge/being reviewed (Ian, Renata, Kevin W., ABSA person, Ry)
      • 20.04 PR will be added (Robin working on this)
    • Indy-Node
      • Wade starting this week to repeat what was done on Plenum – ETA 1-2 weeks.
    • Sovrin Release - Wade Barnes
    • indy-test-automation
  • Indy Plenum issuer reported: IC Queue getting quite large
    • Dom to add more details; Evernym to look further
  • Indy SDK
    • Indy CLI is part of the Indy SDK
    • 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
  • 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
        Indy SDK
            • Landing page
            • Video: Intro to Indy Generation Next
            • Meetup channels

      Future Calls


      Next call:

      Future:

      ...