Closed caniszczyk closed 7 years ago
cc: @opencontainers/runc-maintainers @opencontainers/image-spec-maintainers @opencontainers/image-tools-maintainers @opencontainers/runtime-spec-maintainers @opencontainers/runtime-tools-maintainers
SGTM
On Wed, Dec 14, 2016 at 5:49 PM Chris Aniszczyk notifications@github.com wrote:
cc: @opencontainers/runc-maintainers https://github.com/orgs/opencontainers/teams/runc-maintainers @opencontainers/image-spec-maintainers https://github.com/orgs/opencontainers/teams/image-spec-maintainers @opencontainers/image-tools-maintainers https://github.com/orgs/opencontainers/teams/image-tools-maintainers @opencontainers/runtime-spec-maintainers https://github.com/orgs/opencontainers/teams/runtime-spec-maintainers @opencontainers/runtime-tools-maintainers https://github.com/orgs/opencontainers/teams/runtime-tools-maintainers
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/opencontainers/tob/issues/20#issuecomment-267181870, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEF6W1bs4B1itZIkWeb3ob4luhFIAfTks5rIHKPgaJpZM4LL_Kq .
@caniszczyk Where do nominations go again? I forget the process.
@philips I'll simply create a google form or just use a github issue, let me know if you have a strong preference
no preference
On Thu, Dec 15, 2016 at 1:43 PM Chris Aniszczyk notifications@github.com wrote:
@philips https://github.com/philips I'll simply create a google form or just use a github issue, let me know if you have a strong preference
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/opencontainers/tob/issues/20#issuecomment-267407162, or mute the thread https://github.com/notifications/unsubscribe-auth/AACDCA7wXdN_7tw_V5wQlOzwZoK9l73Hks5rIYpogaJpZM4LL_Kq .
@philips we'll use a google form, it's a bit easier to track data that way, I'll shoot an email to dev@ letting people know. I'll also open nominations today to give people a longer amount of time. Here is the google form: https://goo.gl/forms/WRVqwE1ePj3P2SIi2
Note that TDC maintainers (everyone in a MAINTAINERS file across projects) maintainer may nominate up to two (2) candidates for election, except that only one (1) nominee may be employed by the TDC maintainer’s own company.
Today is Jan 16th 2017; Nominations Close today.
Friendly ping for the @opencontainers/image-spec-maintainers @opencontainers/runtime-spec-maintainers @opencontainers/runtime-tools-maintainers @opencontainers/image-tools-maintainers
So far 12 people have given me their list of nominations, so thank you for that.
Thanks, 16 people have responded so far with a great set of candidates.
I will close nominations at the end of today UTC time.
I sent out a reminder email to all those who haven't voted too.
@caniszczyk After the close of nominations, will you be posting the list of all nominated candidates?
@RobDolinMS I will post it later tonight here and the voting emails will go out to all qualified TDC maintainers.
Here is the final list of candidates:
The voting will happen via CIVS (http://civs.cs.cornell.edu/) and every official TDC maintainer (exists in a MAINTAINERS file will receive an email to do a ranking vote).
Just as a heads up, I will start voting tomorrow.
I emailed the list of candidates to see if anyone wants to opt out from a nomination.
Appreciate the nomination - where's the summary of exactly what are the responsibilities and time commitment?
@thockin the time commitment is fairly minimal, the TOB doesn't formally meet unless they decide to call a meeting (e.g., if a major conflict arises). I believe @philips or the rest of the @opencontainers/tob can speak to the level of commitment.
In terms of responsibilities: https://github.com/opencontainers/tob#technical-oversight-board-tob
The TOB is responsible for managing conflicts, violations of procedures or guidelines and any cross-project or high-level issues that cannot be resolved in the TDC for OCI Projects. The TOB shall also be responsible for adding, removing or reorganizing OCI Projects.
More info found in the charter section 6: https://www.opencontainers.org/about/governance
In terms of mailing list activity, you can see the level of activity here (fairly minimal): https://groups.google.com/a/opencontainers.org/forum/#!forum/tob
On Tue, Jan 17, 2017 at 04:51:30PM -0800, Chris Aniszczyk wrote:
I emailed the list of candidates to see if anyone wants to opt out from a nomination.
I'm happy to stand for election if folks want (and thanks for the nomination, whoever that was), but I'm not sure I (or the other non-maintainers: @estesp, @gregkh, @rhatdan, @RobDolinMS, and @thockin) are eligible. More on this in #24 to avoid distracting from this election if folks don't want to get into it now.
Sent out the CIVS poll to all maintainers, look for an email from Condorcet Internet Voting Service civs@cs.cornell.edu
cc: @opencontainers/image-spec-maintainers @opencontainers/runtime-spec-maintainers @opencontainers/runtime-tools-maintainers @opencontainers/image-tools-maintainers)
Results are in, thanks to everyone who voted and took part in the process:
https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/uE7-41-fevA
The top 4 results are:
The process of electing a new TOB chair will start soon, which happens annually: https://github.com/opencontainers/tob/issues/25
FYI @opencontainers/tob, just a friendly reminder that some 4 spots will open up in the TOB early next year:
@crosbymichael, @gregkh, @xemul and @vbatts spots will open up. They are free to nominate themselves and run again though if they so wish. A simple reminder that nominations will come from the TDC maintainers (everyone in a MAINTAINERS file).
We will also elect a new TOB chair directly afterwards and by Feb 11th.
My proposed schedule is this:
Let me know if you have any comments.