2020 03 19 TSC Minutes
(7:00am - 8:00am PT)
via Zoom
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
TSC Members
Present?
- Angelo De Caro
- Arnaud J Le Hors
- Christopher Ferris
- Dan Middleton
- Gari Singh
- Hart Montgomery
- Mark Wagner
- Nathan George
- Swetha Repakula
- Tracy Kuhrt
- Troy Ronda
Resources:
Chat: chat.hyperledger.org ( use your LFID to login )
Github: www.github.com/hyperledger
Wiki: wiki.hyperledger.org /
Public lists: lists.hyperledger.org
Meetings: wiki.hyperledger.org/community/calendar-public-meetings
Announcements
Items of discussion
- Security reporting policy.
- Github now fully supports handling security bugs the way we want it to work.
- The only concern was directing security bug reports to security@ mailing list instead of Github issues.
- Can be solve with training materials.
- Christopher Ferris David Huseby and Ry Jones to create proposal to use it for security issues and a separate proposal for moving away from JIRA to Github issues entirely.
- Long Term Agenda - Framing
- James Barry William Katsak to present part of their HGF talk (~25min)
- Link to presentation TSC- Blockchains Become Composable - Final - Taekion 3-19-2020.pdf
- What would a Hyplerledger stack look like today and tomorrow?
- How can we decompose blockchains into constituent pieces to build up solutions for each workload.
- We're already starting to see pluggable components breaking out (e.g. Transact and Ursa) but what about other pieces of blockchains?
- Why don't we have well defined abstractions for consensus, crypto, block storage, smart contracts, etc...
- Standardizing on API's would take serious effort and collaboration.
Quarterly updates
- 2020 Q1 Hyperledger Grid
- Comments by Duncan Johnston-Watt: concerned that there's a dependency on Splinter that is entirely governed by Cargill.
- Splinter is Apache 2.0 licensed.
- James Barry: multiple projects now depending on Splinter: Sawtooth, Grid, and Transact.
- It looks like in this case these projects are built to run on top of Splinter instead of having a strong dependency on Splinter but the broader community is concerned that the dependency may become stronger.
- This is something we'll probably have to look into closer.