Hyperledger Contributor Meeting Agenda
...
- 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
...
- the maintainer qualification rules need a refresh, we'll need to wait until Shawn Amundson comes back from vacation to do that
- we should do a poll of existing but idle maintainers to see if they would like to get back involved. Otherwise, inactive maintainers should be moved to an Emeritus section of the maintainer list to recognize their contribution while being clear about the active maintainers
- Ry Jones
- 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:
- Maintainer activity in the last year:
Toolchain
- the principal issue driving the toolchain stuff is the confusion around docker-compose v1 and v2
- v1 and v2 have slightly different YAML parsing that shows up in awkward places
- container ids are different between v1 and v2
- Where possible/necessary we should update the YAML `version` fields in the various docker-compose files which either behave identically regardless of the binary version used OR have versions which demand one or the other docker-compose releases (either too high for v1 or too low for v2)
- Switching to docker-compose v2 everywhere will require a thorough going through of the various test setups in all the projects
Documentation
- ACTION: Mark Carroll to take over reviewing the docs for RAFT references
- ACTION: Mark Carroll continuing to review documentation
SDK
- ACTION: Ryan Roberts - will publish the alternate tokio+tmq implementation for discussion ASAP
- ACTION: Ryan Robers, et al - will open a PR converting the existing sawtooth SDK to use `prost`
LR TEST
- ACTION: Kevin O'Donnell Pr a Helm chart with `test` implemented. Then the test can be run on any k8s infrastructure
Github Issues
- ACTION: discuss labels for issues if any are missing
- ACTION: various - we will review/triage all the issues, and label them