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
- The Hyperledger /dev/weekly developer newsletter goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please leave a comment for consideration on the upcoming newsletter wiki page.
Quarterly reports
- 2021 Q4 Hyperledger Burrow (due )
- 2021 Q4 Hyperledger Explorer (due )
- 2021 Q4 Hyperledger Avalon (due )
- 2021 Q4 Hyperledger Ursa (due )
- 2021 Q4 Hyperledger Besu (due )
- 2021 Q4 Hyperledger Caliper (due )
Upcoming reports
- 2022 Q1 Hyperledger Cactus (due )
- 2022 Q1 Hyperledger Fabric (due )
- 2022 Q1 Hyperledger Sawtooth (due )
Decision
- Moving Burrow to Dormant state - we have been notified by Casey Kuhlman at Monax that they would like to move Burrow to a Dormant state
- Approved by voice vote
Discussion
Project Proposals (from hyperledger/hyperledger-hips)
Backlog (from hyperledger/tsc)
Recordings
Attended by:
- Angelo De Caro
- Arnaud J Le Hors
- Artem Barger
- Arun S M
- Bobbi Muscara
Danno Ferrin- David Enyeart
- Grace Hartley
- Hart Montgomery
- Jim Zhang
- Kamlesh Nagware
- Nathan George
Peter Somogyvari- Tracy Kuhrt
- Troy Ronda
3 Comments
Arun S M
Dormant state definition in the TSC states "ones in which the normal functions are suspended or slowed down for a period of time". It could mean that a new code can go in the Dormant state project. Other projects within Hyperledger have integrations with Burrow. Probably, need to inform each of those projects to be prepared for the unforeseen situations or at least get an agreement from the Burrow team to support critical issues.
Tracy Kuhrt
Messages sent via chat:
Tracy Kuhrt
From Shawn Amundson: