Page History

Summary

Recording from the call: 

...

20210202 Indy Contributors Call Recording

...

Attendees

• @name (Employer) <email>
• Kevin Griffin (Scoir) <kg@scoir.com>
• Richard Esplin(Evernym) <richard.esplin@evernym.com>
• Alexander Jonsson (Laniakea Health) <alex@seropass.me>
• Robin Klemens (DB Systel GmbH) <robin.klemens@deutschebahn.com>
• Ry Jones (Hyperledger) <rjones@linuxfoundation.org>
• David Boswell (Hyperledger)
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>
• Ryan Marsh(Evernym) <ryan.marsh@evernym.com>

Related Calls and Announcements

...

• Indy Node
  • GitHub actions led by Kevin Griffin
    • Indy Node CI - https://github.com/hyperledger/indy-node/pull/1622 (Awaiting review) Kevin Griffin 
      • DONE w00t! Alex K to review (Monday), Renata (perhaps earlier) and Sergey looked at it.
      • Does not remove Jenkins still required – just adds GHA as optional – move to swapping those
      • Broad consensus that we should accept the PRs, and improve them over time instead of waiting for thorough review.
    • Indy Plenum CI - https://github.com/hyperledger/indy-plenum/pull/1505 (WIP) Wade Barnes Wrapping up, almost DONE - confident
      • Similarly happy to accept PRs quickly.
    • Indy Plenum CD - Ian Costanzo - First pass done, clean up in process
    • Indy Node CD - need clarification around rocket chat comments
      • Which system tests are the right ones? "Just run PyTest" says Alex
      • How to run system tests?
      • Should we remove since deprecated tests and scripts?
  • Ubuntu 20.04 upgrade led by Robin Klemens (help from Richard Esplin / Ryan Marsh )
    • Work needed
      • Python 3.8 upgrade
      • Reviewing pinned dependencies
      • Indy SDK upgrade?
    • Create a branch for collaborating, then a single PR to merge to Master / Main
  • New branching model led by Wade Barnes
    • Documenting plan (HIPE?)
    • Merging Stable to Master
    • Rename Master to Main
    • Releasing what is currently in Master
    • Evernym can help merge and test.
    Ubuntu 20.04 upgrade led by Richard Esplin
    • Python 3.8 upgradeReviewing pinned dependencies
• Indy SDK
  • Next release in progress, led by Ian Costanzo
    • Proposal: Ready to release? Yes
      • Standard testing done
      • Tested with all BC Gov apps
      • Question: Issue with account to PyPi?  Has that been resolved?
        • Hyperledger has ownership of the accounts, with secrets in GitHub repo, but need to check that it is still possible to publish from Jenkins
  • GitHub actions led by Patrik Stas
• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
• Indy/Aries Shared Libraries - donated to Hyperledger (indy-vdr, indy-shared-rs, aries-askar)
• Ursa

Meeting Topics

• Status of Indy Node (et. al) CI/CD and Ubuntu upgrade
  • Sovrin needs:
    • Next release should be 16.04 only, and (more or less) exactly as currently in production so we can verify the CI/CD process by a doing "a few nodes at a time" upgrade.
    • The Ubuntu upgrade must interoperate with the then-current 16.04 release, so that we can organize the "one node at a time" Steward OS upgrades.
    • Richard: Could be cheaper to do more QA on fewer releases.
• Hyperledger support for finding new contributors
  • Contribution Campaigns
  • Hyperledger could plan a developer recruitment marketing campaign for some point this year.
    • Example: Blockchain Automation Framework lab
    • https://lfanalytics.io/projects/hyperledger%2Findy/dashboard
    • Good project would be new Indy DID method
• HIPEs for helpers to remove plugins: PR 162
  • Freeze ledgers
  • Fees in Indy

Future Calls

Next call:

• HIPEs for helpers to remove plugins: PR 162
  • Freeze ledgers
  • Fees in Indy
• New branching model led by Wade Barnes
  • Documenting plan (HIPE?)
  • Merging Stable to Master
  • Rename Master to Main
  • Releasing what is currently in Master
  • Evernym can help merge and test.

Future:

• Status of Indy-SDK release
  • 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?)

Future Calls

Next call:

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

...

Action items