Versions Compared

Key

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

...

  • Hakan Yildiz (TU Berlin) <hakan.yildiz@tu-berlin.de>
  • Richard Esplin (Evernym) <richard.esplin@evernym.com>
  • Wade Barnes (Neoteric Technologies Inc. ) <wade@neoterictech.ca>
  • Lynn Bendixsen (Indicio, PBC) <lynn@indicio.tech>
  • Philipp Schlarb(esatus), <p.schlarb@esatus.com>
  • Sean Bohan (Hyperledger) <sbohan@linuxfoundation.org>
  • Mirko Mollik (TrustCerts) <mollik@trustcerts.de>

Related Calls and Announcements

...

Future Calls

  • Plans for a new Indy-SDK release?
  • 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

...