2020-10-27 Indy Contributors Call

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

• @name (Employer) <email>

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

• @Richard Esplin (Evernym) <richard.esplin@evernym.com>

• @Wade Barnes (Wade Barnes/BC Gov) <wade.barnes@shaw.ca>

• @Alexander Jonsson (Laniakea Health) <alex@laniakeahealth.com>

• @Lynn Gray Bendixsen (Indicio.tech) <lynn@indicio.tech>

• @Ian Costanzo (Ian Costanzo/BC Gov) <iancostanzo@gmail.com>

• @Michael Bailey (Paramount Software) <mbailey@paramountsoft.net>

• @Steve McCown (Anonyome Labs) <smccown@anonyome.com> 

• TBD 

• Indy Node

  • Next release in process

• Indy SDK

  • Interest in organizing a release by @Ian Costanzo

• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor

• Indy/Aries Shared Libraries

  • Current status: creating a branch of ACA-Py with these components and without indy-sdk 

  • Indy Shared:

    • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr

    • indy-credx - https://github.com/andrewwhitehead/indy-credx

    • indy-shared-rs - https://github.com/bcgov/indy-shared-rs

  • Aries Shared:

    •  

      • aries-credx

      • aries-askar - Aries Storage - https://github.com/andrewwhitehead/aries-askar

    Open

    

    askar slide

• Ursa

• Evernym's next items (over next two months should have more people on the project, but most will be new)

  1. Remove the Sovrin Token from Sovrin MainNet.

  2. Having LibIndy use Indy-VDR-Aries, or using Indy-VDR-Aries directly.

  3. Migrating the LibIndy wallet to an Aries wallet and addressing performance concerns.

  4. Revocation 2.

     1. Mattr has  some new thinking on this.

  5. Make progress on Rich Schemas and BBS+ signatures.
     In addition, we want to support releases of Indy Node and Indy SDK that are being organized by the community.

• Indy Node Release Status Updates:

  • Replace indy-crypto with ursa-crypto – build failing, @Wade Barnes investigating.

    • Need help.

  • @Alexander Jonsson is implementing the Rich Schema feature flag (Pull Request found here)

    • Need review; cyclical warning in the static analysis – what to do?

  • CI/CD Progress being made

    • PyTest tags added – not yet merged – in draft.  Need to make sure that every test has a mark on it.  Some tests may be lost until the tags are added. Merge after that check.

      • Need a review and approvals.

    • Github Actions on a branch for CI – running and working, but need to keep them running in parallel to current method before moving forward.

    • GitHub Actions for CD still to be done.

• Call for Participation: Indy DID Method (did:indy) Specification

  • Follow up from IIW

  • Current hackmd.io Document

  • Plan for Weekly Meetings

• Request for indy-sdk release

  • Driver – restrictions on predicates

    • LibVCX not planned as part of this

  • Driver - (Evernym) fixes to indy-sdk and libvcx

  • Driver - Stable release before wrapping Aries Shared Libraries (and deprecating components)

  • Plan: mid-November release

    • Review what has been merged already

    • Knowledge transfer from Evernym team to Ian, Wade, others on how to tag, build and release - call to be setup this week. Sergey M. - Friday at 6AM Pacific

    • Join Zoom Meeting (Friday 6am pacific time)
      https://us02web.zoom.us/j/88652458257?pwd=Z2xmdFpQbVBFTThWTVlOYm9ieitwUT09
      Meeting ID: 886 5245 8257
      Passcode: 534767

    • Possible resources – UBC Students if there are things that can be done.

  • iOS wrapper - can we include this in the release? Latest:

    • Drop 32-bit (no issue there)

    • Follow instructions - doing build from scratch  – works fine, but link fails iosarch64 binaries not found (arm versions).

      • Issue - libsodium, SSL, ZMQ installation via homebrew; Mac binaries installed, not universal or iOS. Must install them manually - build and package. Some prebuilt ones can be installed via homebrew. Instructions need to be added - questionable source.

      • Need to decide if people should build it themselves or install via the pre-built or from a package manager (CocoaPods)  Update the instructions one way or the other.

      • Produce artifacts that can be put on CocoaPods package manager.

  • https://github.com/hyperledger/indy-sdk/issues/2249

• Request for volunteer to lead Indy Plenum PR Review: Richard to find a "volunteer"

• Request from Hyperledger – reach out to HL Staff to help getting some contributors – has been successful in the past – can anyone step up from the project to drive that from the project side?  Contact @Marta Piekarska-Geater

Next call:

Future: