Page Comparison

Summary

The call recording is available here: (Richard forgot to hit the button. Whoops!)

Remember the Hyperledger Code of Conduct

...

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>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Wade Barnes (Wade Barnes / BC Gov) <wade.barnes@shaw.ca>
• aStephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
• Kevin Griffin (Scoir) <kg@scoir.com>
• Lynn Gray Bendixsen (Indicio.tech) <lynn<lynn@indicio.bendixsentech>
• Alex Alexander Jonsson (Laniakea Health) <alex@laniakeahealth.com>
• Sergey Khoroshavin (Evernym) <sergey.khoroshavin@evernym.com>
• Ajay Jadhav (AyanWorks) <ajay@ayanworks.com>

...

Current PRs in:

• Indy Node
• Indy Plenum
• Sovrin
• Sovrin Token

Open issues

Release plan

• Release workflow doc Renata put together for us; https://docs.google.com/presentation/d/1iYIIlkZUcgfVh8SvrzQXPgPyUUNubgUAomTTpcJ9J_Q/edit?usp=sharing
• Ensure all commits in Stable are merged back to Master - 
  • indy-node
  • indy-plenum
  • sovrin
  • sov-token
• Test Indy Node built from Master against Indy Plenum built from Master
  • Test Rich Schema transactions
    • Add system level tests for the new rich schema transactions: https://github.com/hyperledger/indy-test-automation/tree/master/system
      • Probably means adding support for new Rich Schema transactions to LibIny
      • Or wrap Indy-VDR into Indy-SDK to use the Rich Schema support in Indy-VDR (https://github.com/hyperledger/indy-sdk/pull/2120)
    • Rich Schema transactions are unlikely to break existing functionality, but bugs in the new transaction type could crash the network if triggered.
      • Could introduce a feature-flag to turn off handling the new transaction type until it is fully tested.
• Replace Indy Node with Ursa:
  
  • https://github.com/hyperledger/indy-node/pull/1607
  • https://github.com/hyperledger/indy-plenum/pull/1369
  • https://github.com/hyperledger/indy-plenum/pull/1481
  • Summary: work is  done in Plenum, but we need to complete the CI / CD work in Indy Node
• Continue this conversation on next Indy Contributors call.

Future Calls

Next call:

Future:

Action items

• Migrating to Ursa (Indy Node)
• Recover when Audit Ledger is out of sync with other ledgers: https://github.com/hyperledger/indy-node/issues/1618