Open Stack

I created the patch to setup the tc election:

https://review.openstack.org/#/c/591111/

-Kendall (diablo_rojo)

On Fri, Aug 10, 2018 at 9:44 AM Doug Hellmann <doug at doughellmann.com> wrote:

> Excerpts from Tony Breeds's message of 2018-08-10 07:44:42 +1000:
> > On Thu, Aug 09, 2018 at 05:20:53PM -0400, Doug Hellmann wrote:
> > > Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000:
> > > > Hello all,
> > > >     With the PTL elections behind us it's time to start looking at
> the
> > > > TC election.  Our charter[1] says:
> > > >
> > > >   The election is held no later than 6 weeks prior to each OpenStack
> > > >   Summit (on or before ‘S-6’ week), with elections held open for no
> less
> > > >   than four business days.
> > > >
> > > > Assuming we have the same structure that gives us a timeline of:
> > > >
> > > >   Summit is at: 2018-11-13
> > > >   Latest possible completion is at: 2018-10-02
> > > >   Moving back to Tuesday: 2018-10-02
> > > >   TC Election from 2018-09-25T23:45 to 2018-10-02T23:45
> > > >   TC Campaigning from 2018-09-18T23:45 to 2018-09-25T23:45
> > > >   TC Nominations from 2018-09-11T23:45 to 2018-09-18T23:45
> > > >
> > > > This puts the bulk of the nomination period during the PTG, which is
> > > > sub-optimal as the nominations cause a distraction from the PTG but
> more
> > > > so because the campaigning will coincide with travel home, and some
> > > > community members take vacation along with the PTG.
> > > >
> > > > So I'd like to bring up the idea of moving the election forward a
> > > > little so that it's actually the campaigning period that overlaps
> with
> > > > the PTG:
> > > >
> > > >   TC Election    from 2018-09-18T23:45 to 2018-09-27T23:45
> > > >   TC Campaigning from 2018-09-06T23:45 to 2018-09-18T23:45
> > > >   TC Nominations from 2018-08-30T23:45 to 2018-09-06T23:45
> > > >
> > > > This gives us longer campaigning and election periods.
> > > >
> > > > There are some advantages to doing this:
> > > >
> > > >  * A panel style Q&A could be held formally or informally ;P
> > > >  * There's improved scope for for incoming, outgoing and staying put
> TC
> > > >    members to interact in a high bandwidth way.
> > > >  * In personi/private discussions with TC candidates/members.
> > > >
> > > > However it isn't without downsides:
> > > >
> > > >   * Election fatigue, We've just had the PTL elections and the UC
> > > >     elections are currently running.  Less break before the TC
> elections
> > > >     may not be a good thing.
> > > >   * TC candidates that can't travel to the PTG could be disadvantaged
> > > >   * The campaigning would all happen at the PTG and not on the
> mailing
> > > >     list disadvantaging community members not at the PTG.
> > > >
> > > > So thoughts?
> > > >
> > > > Yours Tony.
> > > >
> > > > [1] https://governance.openstack.org/tc/reference/charter.html
> > >
> > > Who needs to make this decision? The current TC?
> >
> > I believe that the TC delegated that to the Election WG [1] but the
> > governance here is a little gray/fuzzy.
>
> OK, I'm content for the Election team to make the call I just wanted to
> make sure I gave you an opinion if you were asking me for one. ;-)
>
> > So I kinda think that if the TC doesn't object I can propose the patch
> > to the election repo and you (as TC chair) can +/-1 is as you see fit.
> >
> > Is it fair to ask we do that shortly after the next TC office hours?
>
> +1
>
> >
> > Yours Tony.
> >
> > [1] https://governance.openstack.org/tc/reference/working-groups.html
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180810/f2e1d8a5/attachment.html>