...
- 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.
- Sovrin needs:
- 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?)
- Status of GitHub Actions for the Indy-SDK
Future Calls
Next call:
...
- 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
...