toc@lists.hyperledger.org

TSC elections: electorate should include SIGs and some other suggestions.

Hi all, As a long time observer, contributor and participant in Hyperledger, I make the following comments about the TSC election process. SIGs are part of the hyperledger community. SIGs did not

By Vipin Bharathan · #2511 ·

Re: on expanding the TSC

I like this idea. Besides, we may consider an automatic opt-out for 3 continuous unexcused absences. And for the number, consider the growing size of the community and more new projects, 17, 19 or 21

By Baohua Yang · #2510 ·

Re: on expanding the TSC

Supportive of boosting tsc membership. 21 seems like reasonable number for lack of a better way to set that number. On the topic of community representation, there is a way of providing this that most

By Silas Davis · #2509 ·

Re: on expanding the TSC

yes, we had similar practice in W3C WGs I chaired, though we also had chair discretion to forgive absences due to travel or vacation. Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM

By Christopher Ferris <chrisfer@...> · #2508 ·

Re: on expanding the TSC

Hi Everyone, Chris, thanks for bringing this up. This makes a lot of sense for us as a community. We are a far bigger organization than when we started, and it only makes sense to increase

By hmontgomery@us.fujitsu.com <hmontgomery@...> · #2507 ·

Re: on expanding the TSC

I support this idea.My only concern with growing the TSC would be the risk of not reachingquorum but if we mitigate this risk with an appropriate measure I thinkwe can only gain from the

By Arnaud Le Hors · #2506 ·

Re: on expanding the TSC

Hi Chris, On August 21st of last year, I suggested to this list something very similar to Brian’s mention today that you reference below; “Brian noted that CNCF TOB has an elected tier and a

By bill · #2505 ·

on expanding the TSC

On today’s TSC call, I noted that when we established Hyperledger, we had 11 Premier members and chose the number of TSC members as a derivative of that. We now have 18 Premier members and a board

By Christopher Ferris <chrisfer@...> · #2504 ·

TSC Nominations

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

By Middleton, Dan <dan.middleton@...> · #2503 ·

Hyperledger Besu Proposal is Live

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

By Grace Hartley · #2502 ·

08-08-2019 TSC meeting minutes

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

By Dave Huseby <dhuseby@...> · #2501 ·

Burrow Q3 update is up

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

By Silas Davis · #2500 ·

Upcoming Event: Hyperledger Burrow Quarterly Update Due #tsc-project-update - Thu, 08/08/2019 #tsc-project-update #cal-reminder

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

By tsc@lists.hyperledger.org Calendar <tsc@...> · #2499 ·

Upcoming Event: Hyperledger Performance and Scalability WG Quarterly Update Due #tsc-wg-update - Thu, 08/08/2019 #tsc-wg-update #cal-reminder

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

By tsc@lists.hyperledger.org Calendar <tsc@...> · #2498 ·

Block Chain Node Communication with closed inbound Firewall ports?

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

By Scott Morgan · #2497 ·

Re: Proposal for TSC RFCs?

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

By Shawn Amundson · #2496 ·

Re: Proposal for TSC RFCs?

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

By Baohua Yang · #2495 ·

Re: Proposal for TSC RFCs?

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

By Christopher Ferris <chrisfer@...> · #2494 ·

Re: Proposal for TSC RFCs?

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

By Silas Davis · #2493 ·

Re: Proposal for TSC RFCs?

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

By Ashok Malhotra <malhotrasahib@...> · #2492 ·

Messages