Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct
Announcements
Discussion
...
- How should we handle maintainers becoming unresponsive to communications (in PRs and in other communication channels)?We have a section in governance that says "Maintainers designated for review are required to review PRs in a timely manner" but this doesn't seem to be specific enough because some pull requests are stuck without feedback for months on end. What can we specify further in the requirements to make the situation better without making it worse (overly bureaucratic) could we improve pull request review velocity?
- FUJITSU proposal: Cactus_dev_planning-2021-04-05.pdf
- Explanation of VerifierFactory behavior (abstraction of Validator IF) (postponed agenda from previous week)
- Consortium Management Plugin
- Smart Contracts in Cactus (HTLCs, Federated Validation, Trusted Relays, etc.)
- refactor: dangling package.json inside packages directory #682 #719
- Commit message format in contributing.md (point 6 of the PR Checklist section => https://github.com/hyperledger/cactus/blob/main/CONTRIBUTING.md#pr-checklist---contributordeveloper)
