Open Stack

Doug Hellmann <doug at doughellmann.com> writes:

> Ed Leafe <ed at leafe.com> writes:
>
>> On Feb 12, 2019, at 12:22 PM, Doug Hellmann <doug at doughellmann.com> wrote:
>>> 
>>> Assuming no prolonged debate, you'll need 7-10 days for the change to be
>>> approved. If the team is ready to go now, I suggest you go ahead and
>>> file the governance patch so we can start collecting the necessary
>>> votes.
>>
>> Done: https://review.openstack.org/#/c/636416/
>>
>> -- Ed Leafe
>
> After consulting with the election officials during the most recent TC
> office hour [1], I have proposed shifting the PTL election deadline out
> 2 days to allow the TC time to approve the new team [2]. Thank you to
> Tony, Jeremy, and Kendall for accommodating the change.
>
> [1] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-02-13.log.html
> [2] https://review.openstack.org/#/c/636510/
>
> -- 
> Doug

Since I've had a question or two about this, I want to clarify exactly
what happened and what changed.

First, two points to clarify the source of the issue:

1. The rules for voting on a governance change that would add a new team
   require us to give at least 7 days of consideration, regardless of
   the vote count, in case there are objections from the community.

2. The election officials had previously set 19 Feb as the deadline for
   defining the electorate for PTL elections for teams.

The TC rule and election deadline combined mean that the Placement team
would not have been approved in time, and so would not be able to
participate in "normal" PTL elections for Train.

We explored a few options:

Changing the TC voting rule would have taken us at least as long as
approving Placement under the current rules, at which point we'd still
be past the deadline.

We could create the Placement team and have them run a special election
during Train, and the election officials were open to that approach.
However, that's a lot of extra work for them just because of missing a
deadline by 1 day for something we knew was coming, to which there is
not a lot of objection, but that we let slip.

So, in order to avoid creating that extra work, and to have Placement
participate in the normal Train cycle PTL election process like the
other teams, we've proposed moving the deadline for defining the
electorate to 22 Feb.

The patch change the deadline in the election repo is modifying a file
that currently defines the TC election schedule, so it's a bit confusing
about why that file is being changed. I'm not an expert in the tools,
but from what I understand that same setting in that file is used for
both elections, but only one election can be listed at a time. Since the
TC election comes first, the other dates in that file are about the TC
election, and the file contents will be changed when the PTL election
starts.

In any case, the change won't affect the TC election because the
repositories moving under the new team are already part of an official
team, and so contributors will already be able to participate in the TC
election.

The change also will not affect the dates of the PTL election process in
which most people participate (nominations, voting, etc.), because the
election officials have agreed to a smaller buffer between the deadline
and the start of the election.  So, they'll be building the election
rolls in a shorter amount of time in order to allow the rest of the
schedule to stay the same.  Thanks again, Tony, Jeremy, and Kendall, for
going the extra mile for us.

Based on the current votes on the governance change to create the
Placement team, we are on track to have it approved in time to meet the
new deadline.

Let me know if anyone has further questions about this; I'll be happy to
make sure it's clear for everyone.

-- 
Doug