Hyperledger Contributor Meeting Agenda
When: Wednesday, June 28, 2023
10:00am to 11:00am Eastern Time - New York
(UTC - 5:00)
Location:
https://zoom.us/j/96206016357?pwd=TnlQWWJmQzhKeWZ3YU1nMmNKblE4dz09
Agenda
Review of actions from the last meeting
- TOC update for last quarter James Barry Ry Jones Kevin O'Donnell
- The previous report has not been merged as there are outstanding questions that need addressed
- TOC update for next quart coming soon
- How can we do this better next time?
- Maintainer activity in the last year:
- Active:
- agunde406 vaporos peterschwarz rbuysse cianx shannynalayna isabeltomb jsmitchell dcmiddle
- Inactive:
- RyanLassigBanks TomBarnes aludvik chenette dplumb94 eloaverona danintel ltseeley rberg2 ineffectualproperty
- Active:
- Joseph Livesey - work to refresh and fix the
sawtooth-poetbuild is ongoing. - Kevin O'Donnell - long-running testing
- we need a solid description of the toolchain in use by the projects (docker, docker-compose, etc.)
- James Barry will scan the available documentation and media for mentions of the RAFT consensus to identify what needs to be touched when we deprecate/decommission it
- Mark Carroll - In order to get ahead of the types of questions we are getting on #sawtooth, Mark will review the documentation for the setups of the various "getting started" and identify the gaps
- Ryan Roberts - check the impact of migrating to prost on
sawtooth-sdk-rust - Ryan Roberts - check the impact of incorporating/enhancing sawtooth-sdk-with the tokio+TMQ version
- Ryan Roberts - get the tokio+TMQ SDK published somewhere so it can be poked at
"Important" Bugs & Issues
Housekeeping
PRs in need of review
- https://github.com/hyperledger/sawtooth-core
- https://github.com/hyperledger/sawtooth-sdk-rust
- https://github.com/hyperledger/sawtooth-docs
- https://github.com/hyperledger/sawtooth-sdk-java
- trivial dependabot updates but build is failing
CI jobs that need kicking
Discord/Community Care & Feeding
- Let's not forget the issues
- Current survey of issue counts
- https://github.com/hyperledger/sawtooth-core/issues - 26
- https://github.com/hyperledger/sawtooth-sdk-rust/issues -3
- https://github.com/hyperledger/sawtooth-docs/issues - 5
- https://github.com/hyperledger/sawtooth-sdk-java/issues - 5
- https://github.com/hyperledger/sawtooth-lib/issues - 2
- https://github.com/hyperledger/sawtooth-sdk-go - 9
- https://github.com/hyperledger/sawtooth-pbft - 3
- https://github.com/hyperledger/sawtooth-poet/issues - 1
- https://github.com/hyperledger/sawtooth-sdk-javascript/issues - 5
- https://github.com/hyperledger/sawtooth-sdk-python/issues - 2
- https://github.com/hyperledger/sawtooth-sdk-swift/issues - 1
- Need volunteers to triage
- Other projects use issue & pr labels to govern the process - should we? Is there an example of a project that does it well and relatively painlessly.
- Current survey of issue counts