RFC: TOC Election Schedules


Brian Grant
 

Thanks. Seems workable.

On Tue, Sep 5, 2017 at 2:28 PM, Dan Kohn <dan@...> wrote:
I added a section saying:

Vacancies

Any vacancies will be filled by using the original selection method for that seat and the replacement will serve the remainder of the original term.


This covers both the chair position (if the chairperson isn't reappointed, the chair is vacant and will be selected by the new 9 members of the TOC) as well as vacancies of a TOC seat. As with the rest of the document, this is in keeping with the spirit and text of the charter but is still worth stating explicitly.


--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Tue, Sep 5, 2017 at 5:18 PM, Brian Grant <briangrant@...> wrote:
On Sat, Sep 2, 2017 at 4:17 AM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
I've added a set of changes, marked as suggested text, to include election of the TOC Chair every two years.

Mostly makes sense, though if we elected someone with a term that didn't align with the Chair term, such as a member with one of the initial 3-year terms, then presumably we'd also need to appoint a new chair in the event the existing chair weren't re-elected.
 

If no other concerns are raised, I'll be posting the revised text to https://github.com/cncf/toc next week. Thanks.

--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Fri, Sep 1, 2017 at 12:30 PM, Dan Kohn <dan@...> wrote:
Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000



_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc





Dan Kohn <dan@...>
 

I added a section saying:

Vacancies

Any vacancies will be filled by using the original selection method for that seat and the replacement will serve the remainder of the original term.


This covers both the chair position (if the chairperson isn't reappointed, the chair is vacant and will be selected by the new 9 members of the TOC) as well as vacancies of a TOC seat. As with the rest of the document, this is in keeping with the spirit and text of the charter but is still worth stating explicitly.


--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Tue, Sep 5, 2017 at 5:18 PM, Brian Grant <briangrant@...> wrote:
On Sat, Sep 2, 2017 at 4:17 AM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
I've added a set of changes, marked as suggested text, to include election of the TOC Chair every two years.

Mostly makes sense, though if we elected someone with a term that didn't align with the Chair term, such as a member with one of the initial 3-year terms, then presumably we'd also need to appoint a new chair in the event the existing chair weren't re-elected.
 

If no other concerns are raised, I'll be posting the revised text to https://github.com/cncf/toc next week. Thanks.

--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Fri, Sep 1, 2017 at 12:30 PM, Dan Kohn <dan@...> wrote:
Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000



_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc




Brian Grant
 

On Sat, Sep 2, 2017 at 4:17 AM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
I've added a set of changes, marked as suggested text, to include election of the TOC Chair every two years.

Mostly makes sense, though if we elected someone with a term that didn't align with the Chair term, such as a member with one of the initial 3-year terms, then presumably we'd also need to appoint a new chair in the event the existing chair weren't re-elected.
 

If no other concerns are raised, I'll be posting the revised text to https://github.com/cncf/toc next week. Thanks.

--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Fri, Sep 1, 2017 at 12:30 PM, Dan Kohn <dan@...> wrote:
Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000



_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc



Dan Kohn <dan@...>
 

I've added a set of changes, marked as suggested text, to include election of the TOC Chair every two years.

If no other concerns are raised, I'll be posting the revised text to https://github.com/cncf/toc next week. Thanks.

--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Fri, Sep 1, 2017 at 12:30 PM, Dan Kohn <dan@...> wrote:
Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000



Bernstein, Joshua <Joshua.Bernstein@...>
 

Thank you for clarifying this and sending it out.

-Josh

On Sep 1, 2017, at 9:30 AM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:

Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc


Brian Grant
 

LGTM. Thanks much for clarifying this.

On Fri, Sep 1, 2017 at 9:30 AM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@...g>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000


_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc



Dan Kohn <dan@...>
 

Here is the proposed TOC election schedule. In September, the End User Community will be appointing their member. Then in March 2018, Brian and Solomon will be reappointed or replaced by the TOC. And in January 2019, the 6 GB-appointed TOC members will be reappointed or replaced.


Thanks.
--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000