Re: TOC moving to 11 seats, and how to stand

Chris Aniszczyk

Please wait until Monday for us to publish the post as stated before, there will be a maintainer election policy put forth that was discussed at the last GB meeting and will be published to

On Wed, Dec 4, 2019 at 10:23 AM Matt Farina <matt@...> wrote:
While the GB and End User TAB have processes in place to create a list of nominees for which to vote on, the non-sandbox project maintainers do not. This is new for them.

Can you please outline how that will work? For example, does each maintainer on each project have the opportunity to nominate someone to be voted on or will it be from each project? These are the sorts of details I'm curious about.

- Matt Farina

On Wed, Dec 4, 2019, at 1:11 PM, Chris Aniszczyk wrote:
The process is baked into the charter here (6)(e):

I don't have a problem in publicizing the "Qualified Nominees" before they are voted upon (this is after the GB/TOC vets+qualifies the nominations anyway), there is nothing that prevents that directly in the charter and I believe the spirit of the document is to leave it up to each respective "Selecting Group"

In terms of publishing more than that or asking for public comment, we can ask each Selecting Group to make the call as we are really empowering each Selecting Group to make the decision.

On Wed, Dec 4, 2019 at 10:05 AM Alexis Richardson <alexis@...> wrote:
+1 I think this is an excellent suggestion 

On Wed, 4 Dec 2019, 10:02 Matt Klein, <mattklein123@...> wrote:
During this nomination cycle, is there any reason that we can't:
  • Make all nominations public, with who / what org nominated the nominee.
  • Some ability for a public comment period on the nominees. If there is concern around public comments, the comments could only go to those who will vote on the nominee (though I would greatly prefer everything be fully public).
This would apply to all types of seats (GB/TOC/End user/etc.).

I think this would vastly increase transparency and community trust in the process.


On Wed, Dec 4, 2019 at 8:45 AM Davanum Srinivas <davanum@...> wrote:
Thanks Chris!

On Wed, Dec 4, 2019 at 8:29 AM Chris Aniszczyk <caniszczyk@...> wrote:
There will be 11 seats total:

- 6 nominees from the Governing Board (GB)
- 2 nominees from the End User Community (up from 1)
- 1 nominee from the non-sandbox project maintainers (up from 0)
- 2 nominees from the other 9 members of the TOC

For the End User TOC seats, it will be the end user members:

For the non sandbox maintainer seat, it will be the non-sandbox maintainers here (

For the GB selected seats, it's the GB:

Amye will have a post out Monday describing all of this in more detail with the timeline.

Hope this helps, there's a lot of constituents that make up the TOC now.

On Wed, Dec 4, 2019 at 8:23 AM Davanum Srinivas <davanum@...> wrote:

Thanks for the blog post. Do we have numbers for how many people are eligible to cast votes in each "Selecting Group"? As i read it, just 3 of the seats (2 from EUC and 1 from non-sandbox) are where the "general community" have a say in. Is that correct?


On Wed, Dec 4, 2019 at 8:16 AM Chris Aniszczyk <caniszczyk@...> wrote:
We are working on a blog post, PR that should go out next week describing the election process, we will open nominations this month with results coming here:

The TOC election schedule has always been described here openly on GitHub:

On Wed, Dec 4, 2019 at 8:12 AM Alexis Richardson <alexis@...> wrote:
Chris, Amye, et al

With the TOC adding 2 seats, what do people do if they want to stand?
More generally as we discussed at Kubecon, how are we making the TOC
process more open & inclusive?


Chris Aniszczyk (@cra) | +1-512-961-6719

Davanum Srinivas ::

Chris Aniszczyk (@cra) | +1-512-961-6719

Davanum Srinivas ::

Chris Aniszczyk (@cra) | +1-512-961-6719

Chris Aniszczyk (@cra) | +1-512-961-6719

Join { to automatically receive all group messages.