>
TSC Membership shall consist of:
…
>
Core project’s Project Technical Leaders (PTLs).
I vaguely remember we want to allow PTL
to select another person to represent the project in TSC.
It may be important as it relates to:
>
No more than 50% of the TSC seats may be held by persons employed by the same company.
It is not clear how this rule interacts with other rules.
I mean, for a single selection replacing old TSC members
with the same number of new TSC members, the multiple-candidates methods
can be understood as selecting new members "one by one",
so it is straightforward to track when a company hits the limit
(so its remaining candidates are not eligible from that point on).
But what about situations when number of TSC members decreases
(e.g. a TSC appointed member seat expiring, or a legacy member revisited)?
What if a TSC member suddenly steps down
(election for the replacement takes time)?
Or when a member changes without large enough election
(e.g. a new PTL selected by a project, or a new project becoming core)?
Some projects have secondary documents handling edge cases
(ODL has rules [1] on how to honor the company cap
when running multiple elections at once).
But for now, I think it would be better to just
add a sentence about (old) TSC members voting
on how to resolve such unforeseen rule interactions.
Vratko.
[1]
https://wiki.opendaylight.org/display/ODL/TSC+Election+Process
As part of the ongoing discussion around evolving the TSC, and in keeping with the
previously socialized slide deck. Please provide feedback on this
PR to update the FD.io Community Doc (our governance doc for how we do things like Elect TSC members).
