In a few days an official email will go out seeking nominations for the next Technical Steering Committee. When we did this last year the field of nominees did not necessarily reflect the full

Hi All, We are excited to share that PegaSys, the Protocol Engineering team at ConsenSys, submitted the Proposal for our Ethereum client, Hyperledger Besu (currently known as Pantheon), for your

The meeting minutes are here: https://wiki.hyperledger.org/display/HYP/2019+08+08+TSC+Minutes Recordings to be added shortly. Dave --- David Huseby Security Maven, Hyperledger The Linux

It's a day late, but hopefully people have a chance to take a look before tomorrow's TSC: https://wiki.hyperledger.org/display/HYP/2019+Q3+Hyperledger+Burrow Silas

Reminder: Hyperledger Burrow Quarterly Update Due #tsc-project-update When: Thursday, 8 August 2019 View Event Organizer: community-architects@... Description: The Hyperledger Burrow

Reminder: Hyperledger Performance and Scalability WG Quarterly Update Due #tsc-wg-update When: Thursday, 8 August 2019 View Event Organizer: community-architects@... Description: The

Hi All, I have been messing around with variations of what turned into this RFC for about 8 years; https://tools.ietf.org/html/draft-adligo-hybi-asbp-02 I think it might be a good way for

The mechanics of the process (git vs. wiki) should be considered a secondary concern. And while I think that the github PR workflow has many usability and technical advantages over the wiki, I'd

+1, and prefer the meeting minutes compared with the video recording, which is not easy to search. -- Best wishes! Baohua Yang

Wiki changes are recorded and can be reversed. Also, only logged in users can edit, so we know who the culprit is. If decisions are recorded in the wiki next to the link to the minutes, then makes

I don't think meeting minutes or the wiki do quite the same job as what is being proposed here. In particular: - Although meeting minutes may be canonical, and certainly votes, not all utterances

I have long argued that working groups need a simple way to answer questions like "When did we make this decision?" and "Where did this paragraph in the spec come from". I have some ideas on how

I agree, pouring through old minutes looking for decisions etc is tedious at best. I also agree that we don't need to over-engineer this. It could be implemented in the wiki pretty easily. I've been

I'm not sure wherewe ended with this discussion. I agree that we should do a better job atrecording decisions and fully support the idea of building a compilationof all the TSC decisions. For

Reminder: Hyperledger Indy Quarterly Update Due #tsc-project-update When: Thursday, 1 August 2019 View Event Organizer: community-architects@... Description: The Hyperledger Indy update

Hi Brian, I wanted to follow up and say that I think a separate graphic depicting the structure of the community would be a great idea. If we do this right, it would help new people find who they

Thank you to Vipin, Duncan, Chris and Dan for feedback. Looks like we have our taxonomy: Distributed Ledgers: Burrow, Fabric, Iroha, Indy, Sawtooth Libraries: Aries,

Hi TSC. I want to provide an update that extends Dave's quick update last week regarding the CI/CD task force, especially as new details have emerged and a few decisions made.

Hi! The link to the photo is broken but that's true, order is in Iroha's nature :) Sara

Ahead of our upcoming summit in Tokyo, I cracked open a kana/kanji reference and was immediately met by this Iroha reference. I was aware of the poem as the namesake for Hyperledger Iroha, but I did