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
...
- Release status: Pam/Joe: Dashboard:
- New 1.4.9/2.1.2/2.2.1 Releases planned for next week - bug fixes (Service discovery not working with old lifecycle, TLS cert improvements and fixes, HSM session caching)
- Ledger checkpoint testing started && taking perf measurements
- Channel Participation API (System Channel removal) update is planned for the next Contributors Call.
- New release cadence being considered - Every 4 months (3x/year) instead of every 3 months (quarterly)
- Asia Pacific Study Circle
- International languages(standing topic)
- Remind translators that if they are maintainers that after they approve a PR they can user the `doc-merge` label on a PR to merge it.
- Malayalam translation update - Annena
- Japanese translation update - Tsujita-san
- Brazilian Portuguese translation update - Renato
- French Translation update - Oumar
- Spanish translations update - Maria/Claudio
- We had discussed having a Translator badge (among other possible badges) and it sounds like that may be too specific. I wanted to check back in about what type of badge would work better?
- One option would be to have a Fabric Documentation badge that could be issued to people making a range of documentation related contributions
- Another option would be to have a Fabric Contributor badge that could be issued to people making documentation contributions or other Fabric related contributions
- Example of pages from other open source projects:https://make.wordpress.org/meta/handbook/documentation/profile-badges/
- "contributor badges are generally assigned to anyone who has contributed to a particular team"
- There is a documentation badgeRussian Language update - Arseny
- Remind translators that if they are maintainers that after they approve a PR they can user the `doc-merge` label on a PR to merge it.
- Samples status - Chris
- New token samples - use the same exact scenario so that people can evaluate both models side-by-side
token account-based sample and tutorial: https://github.com/hyperledger/fabric-samples/pull/318
token utxo sample and tutorial: https://github.com/hyperledger/fabric-samples/pull/319
- New token samples - use the same exact scenario so that people can evaluate both models side-by-side
- Retiring Fabric docs versions 1.1/1.2/1.3 - Banner now working in RTD - see test here: https://hyperledger-fabric.readthedocs.io/en/v2.1.1/ Thank you Brett!
- Peer deployment guide PR https://github.com/hyperledger/fabric/pull/1803
- Google Analytics update - Joe/Pam
...