Versions Compared

Old Version 2

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version Current

changes.mady.by.user Kevin Griffin

Saved on

Key

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

...

Excerpt

Planned:

  • Status of Ubuntu 20.04 work
  • Status of upcoming indy-node release, Rich Schema Feature Flag, and CI/CD Progress
  • Status of upcoming indy-sdk release

The call recording is available here:

...

 20201124 Indy Contributors Call Recording

Remember the Hyperledger Code of Conduct

...

Related Calls and Announcements

...

  • Indy Node
    • Next release in progress, led by this team
    • Ubuntu 20.04
  • Indy SDK
  • Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
  • Indy/Aries Shared Libraries
  • Ursa
  • Evernym's next items (over next two months should have more people on the project, but most will be new)won't be adopting shared libraries, will probably maintain LibIndy as a fork)
    1. Current releases of Indy Node and Indy SDK
    2. Remove the Sovrin Token from Sovrin MainNet.
    3. Having LibIndy use Indy-VDR-Aries, or using Indy-VDR-Aries directly.
    4. Migrating the LibIndy wallet to an Aries wallet and addressing performance concerns.
    5. Revocation 2.
      1. Mattr has  some new thinking on this.
    6. 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.

Meeting Topics

  • Ubuntu 20.04 for Indy Node / Indy Plenum
  • Indy Plenum PR Review - the consensus code - Any updates to status?
    • Brent's fix for INDY-827 (PR 1486)  - not to be merged into main until reviewed and tested by another
      • Decision: Will not be merged into this release because of the manual testing effort.
    • Need to accept PR 1482 - Evernym can do that.
    • What is the difference between STABLE and MASTER? 
      • Stephen to review the last call recording
    • Arrange a meeting to get the CI/CD done, or perhaps merge the code bases to enable a single pipeline.
      • Plenum PR created
      • One test is failing – likely not because of the CI/CD – failed previously
      • Plan is to get this done entirely
  • Indy Node Release Status Updates:
    • Replace indy-crypto with ursa-crypto – build failing, Wade Barnes investigating.
      • PR to fix, but there is a dependency to indy-plenum in order to proceed.
      • Still stuck on indy-plenum
    • Alexander Jonsson is implementing the Rich Schema feature flag (Pull Request found here)
      • New PR needed because first not based to Master branch – take 2 coming soon.
      • Alex K is working on this
      • Reviewed and changes suggested
    • CI/CD Progress being made (awesome!!)
      • Paused – indy-plenum will go first and work will resume here
      • 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.
        • One failing test – 33,000 lines of output, which breaks the test output handler. Figuring out how to fix that.
          • auth test case
      • 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. Volunteers?
  • 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.
    • RC branch ready to go, release notes updated, everything is almost ready to go
    • Problem: IOS branch is not building.  What do we do?
      • Sergey has a PR that seemed to work, and build is in progress for that.
      • If so – Master to RC and we're good to go.
      • Could drop IOS, but we'd really rather not do that.
      • Point people: Sergey, Ian, Steve McCowan, Wade
    • One commit in Master Branch is not DCO signed.
      • Someone manually bypassed the DCO which allowed us to proceed – a very bad practice.
        • Separate issued – Ry to be asked if that button can be turned off. 
      • Fixed in the RC branch – not touched in the Master Branch
      • How to address in the Master Branch?
      • Ian, Wade and Ry to discuss.
    • Should we release now or get more features in?
      • No one requested more be added
    • Should this be the last indy-sdk release?
      • Evernym would like to free up the team to do other things, so would like to know if more effort is to be put into the indy-sdk?
      https://github.com/hyperledger/indy-sdk/issues/2249
  • Progress: Indy DID Method (did:indy) Specification -
  • 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

...