toggle quoted messageShow quoted text
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 are good candidates.
On Thu, Aug 8, 2019 at 4:18 PM Arnaud Le Hors <lehors@...
I support this idea.
My only concern with growing the TSC would be the risk of not reaching
quorum but if we mitigate this risk with an appropriate measure I think
we can only gain from the expansion.
For what it's
worth, OASIS has to that end a notion of Voting Rights that you lose after
missing 2 meetings and gain back after attending 2 meetings that is easy
to implement and works well in my experience:
Arnaud Le Hors - Senior Technical Staff Member, Blockchain &
Web Open Technologies - IBM
[Hyperledger TSC] 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 that has 21 members. We have grown from one to now twelve projects
and we have 3 proposed projects in the pipeline. We also have a growing
number of WGs that may also be underrepresented. Yet, we have not grown
the TSC beyond the original 11. This means that the TSC may not adequately
represent the full breadth of our community.
We talked about the prospect of expanding
the TSC to enable greater diversity of projects and WGs, as well as of
Brian noted that CNCF TOB has an elected
tier and a provision in their charter that the elected members may also
choose a number of individuals from within the community to serve
as well. This might be a good model to emulate.
Any change in the number of TSC members
will, of necessity, require a Hyperledger charter revision requiring a
2/3 vote of the board.
I’d like this email to serve as a continuation
of today’s discussion hopefully leading to a formal proposal to a charter
I’ll start by suggesting that we find
a way of growing the TSC beginning this year, but after the scheduled TSC
election, by at least six members. As was also expressed by Mic, we probably
also should keep the size manageable, so maybe no more than 21 total.
Ry and Arnaud also suggested maybe adopting
a quorum rule that penalized absentee members by removing them from quorum
calculation and suspending voting privs following repeated unexcused absences
as a device to encourage participation and diminish potential that we not
achieve quorum (this seems not to have been a problem excepting in the
summer months, but we might consider something as a prophylactic measure.
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/
508 667 0402