can i suggest that the working group comments be moved to the page where we are trying to capture all of these discussions? the role of wg's is really not relevant to the besu proposal

Many thanks for blazingly quick turnaround time here Ry ! Jonathan https://unbounded.network

More people have been nominated. Please read the biographies carefully. https://wiki.hyperledger.org/display/HYP/2019+Nomination+Statements Three nominees asked to be removed; they were nominated by

comments in-lined, below. I would agree with Shawn, here. There could be a bit more alignment, across projects but we do have plug-able consensus. However, I will remind people that code doesn't write

> Every recent project proposal has had to justify itself in relation to other Hyperledger projects. :) Sounds reasonable. Besu has some valuable things to contribute to the Hyperledger ecosystem,

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

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

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

We already have really good pluggable consensus within Hyperledger that supports both voting and lottery style consensus that is very close to being suitable for cross-project use. The next step is

Team, The 2019 Q3 Hyperledger Transact quarterly update is now available for review. Here is the link: https://wiki.hyperledger.org/display/HYP/2019+Q3+Hyperledger+Transact Thanks, -Mark

Vote early and vote often! Get Outlook for iOS From: tsc@... <tsc@...> on behalf of Brian Behlendorf via Lists.Hyperledger.Org <bbehlendorf=linuxfoundation.org@...> Sent: Monday, August 26, 2019

It was brought to our attention that the TSC election deadlines had an off-by-one error: nominations open until August 26th, but voting was scheduled to start the same day, so it meant we opened

Thanks Dan, very kind. I agree that Andi, Gari, and Tracy would be excellent TSC representatives. In addition, here is a shout out for all the other code-contributing maintainers as well: please vote

If you did not get a ballot, and you think you should have, please reach out to me directly. If you did get a ballot - please

I would like to highlight a few of the candidates who have not previously been on the TSC, but whom I would be happy to see on the TSC based on my direct knowledge of their extensive contributions.

Hi Jon, Thanks for the thoughtful response. Pluggable consensus has been in active discussion in the Architecture working group. Unfortunately participation in such cross dlt architectural

Thanks Vipin, that does bring some clear points to draw the discussion around. However if you consider the parallel thread about architecture it’s quite possible to see these virtues as vices. If

Hello all, The current discussion focusing on the main differentiators of Besu is missing the point. Two camps: one asserting that these differentiators are not compelling enough to welcome Besu,

Hi Silas, Thanks for this write-up; I found it helpful. All, I hope nobody minds my joining this discussion but I think the framing of the proposed contribution of Besu provides the

Okay this is interesting, thanks Richard. Firstly: > Like I said near the start, I know my position as CTO of a firm with an open source permissioned blockchain means what I write can’t be seen as