...
Items of discussion
- TSC Size
- ProposalProposed: Extend the size of the TSC to 15 (pending Board approval).
- Motioned and seconded. 0 nays, 1 abstaining (Gari), approved.
- Proposed: Accept the next 4 vote winners into the TSC immediately.
- Motioned and seconded. unanimously rejected.
- Proposed: New size of TSC to take effect for the next election.
- Motioned and seconded. 0 nays, 1 abstaining (Gari), approved.
- ProposalProposed: Extend the size of the TSC to 15 (pending Board approval).
- TSC Term length
- Proposal: Keep TSC term length to 1 year.
- Motioned and seconded. 0 nays, 0 abstaining, approved.
- Proposal: Keep TSC term length to 1 year.
- TSC Term limits
- Proposal: No limit to TSC term
- Motioned and seconded. 0 nays, 0 abstaining, approved.
- Proposal: No limit to TSC term
- Should the TSC have a secretary role?
- Proposal: no TSC secretary role
- Motioned and seconded. 0 nays, 0 abstaining. approved.
- Proposal: no TSC secretary role
- TSC Membership Diversity
Quarterly updates
- 2019 Q4 Architecture WG
- 2019 Q4 Fabric Project
- 2019 Q4 Sawtooth Project
- Sawtooth is being rewritten in Rust and they are reporting some performance impact issues. Is this temporary?
- Yes, the added overhead of doing Python ↔ Rust calls is causing the performance regressions. Eventually everything will be in Rust and performance will improve.
- How can we foster the reuse of the Sawtooth PBFT implementation in other projects?
- Consensus is difficult to reuse right now because of how the different platforms link into the smart contracts layer.
- Sawtooth is being rewritten in Rust and they are reporting some performance impact issues. Is this temporary?
Upcoming items
- 2019 Q4 Identity WG
- 2019 Q4 Iroha Project
...
- TSC Term limits
- TSC Term length
- TSC Size
- WGs scope
- WGs product
- TSC Election voters selection
- Subprojects not formally defined
- Decision Log
- TSC Membership Diversity
- Should the TSC have a secretary role?
- Security reporting policy on GH repos
- TSC Election observers