[tc] Results of the two TC CIVS polls
Hi All, We had two votes running for the TC - V->Z naming, and the TC Chair. The results are as follows: Release Naming: 1. Tied: Do not change current model of geographic names - No review Name releases after major cities - https://review.opendev.org/#/c/677745/ 3. Name releases after the ICAO alphabet - https://review.opendev.org/#/c/677746/ Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_0a9abdadec887a6b&algorithm=beatpath TC Chair: 1. JP Evrard - https://review.opendev.org/#/c/681285/ 2. Mohammed Naser - https://review.opendev.org/#/c/680414/ Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_e6963bddd2f49d57&algorithm=beatpath Thanks all for taking the time to vote, and for the candidates and people who put forward the options for the naming poll. Thanks, Graham
On Wed, Sep 18, 2019 at 01:14:38PM +0100, Graham Hayes wrote:
Hi All,
We had two votes running for the TC - V->Z naming, and the TC Chair.
The results are as follows:
Release Naming:
1. Tied: Do not change current model of geographic names - No review Name releases after major cities - https://review.opendev.org/#/c/677745/ 3. Name releases after the ICAO alphabet - https://review.opendev.org/#/c/677746/
Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_0a9abdadec887a6b&algorithm=beatpath
The scope of this vote was not clear. This was only as far as changing the naming scheme for the remaining V-X, right? Or was it meant for anything past Ussuri? If it's the former, then I am very happy to see there was not strong support to changing the current naming scheme mid-alphabet. I believe that would have been confusing (or just out right odd) to our end users. I do hope to see a plan for what we would like to see happen once we cycle back to A though. Sean
On 18/09/2019 16:22, Sean McGinnis wrote:
On Wed, Sep 18, 2019 at 01:14:38PM +0100, Graham Hayes wrote:
Hi All,
We had two votes running for the TC - V->Z naming, and the TC Chair.
The results are as follows:
Release Naming:
1. Tied: Do not change current model of geographic names - No review Name releases after major cities - https://review.opendev.org/#/c/677745/ 3. Name releases after the ICAO alphabet - https://review.opendev.org/#/c/677746/
Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_0a9abdadec887a6b&algorithm=beatpath
The scope of this vote was not clear. This was only as far as changing the naming scheme for the remaining V-X, right? Or was it meant for anything past Ussuri?
OpenStack Release Naming for V-Z was the title of the poll. The intent was we would sort out V-Z, and then worry about the post Z names. This is proving to be harder than expected as you can see - so I am not sure what the route forward is.
If it's the former, then I am very happy to see there was not strong support to changing the current naming scheme mid-alphabet. I believe that would have been confusing (or just out right odd) to our end users.
Yes, this was driven by the lack of people willing to commit to running the poll, and people who had issues with how the TC ran the last one. Personally, I don't see a huge issue with it, (barring the issue with potentially not having a venue city to choose from for one of the 2020 and one 2021 release).
I do hope to see a plan for what we would like to see happen once we cycle back to A though.
Yes - I think that is an interesting discussion, and something that should start now - we do need to know what to expect :)
Sean
Graham
If it's the former, then I am very happy to see there was not strong support to changing the current naming scheme mid-alphabet. I believe that would have been confusing (or just out right odd) to our end users.
Yes, this was driven by the lack of people willing to commit to running the poll, and people who had issues with how the TC ran the last one.
Personally, I don't see a huge issue with it, (barring the issue with potentially not having a venue city to choose from for one of the 2020 and one 2021 release).
FWIW, I do think that was a little of an exceptional circumstance that can easily be addressed by writing down a process for when we need to make sure to get specific steps done in order to be ready in time. And have safeguards in place for someone else to step in if the current person leading it gets pulled away by outside factors. The U lettering aligning with China was just an unfortunate circumstance. But I think there's also another question that is not asked/answered by this poll. Assuming we keep with the naming scheme, that doesn't mean we need to choose those names in the same fashion we have been doing it. I'd propose we just get a collection of place names that have some kind (any kind) of meaning to folks in the community, all the way through Z. Then for each cycle, let the community vote on which names for the given letter they prefer. Even if we don't change though, I'm a little optimistic that we won't have as much trouble picking potential names like we did trying to map U to Chinese names. Anyway, my 2 yuan. Sean
Graham Hayes wrote:
On 18/09/2019 16:22, Sean McGinnis wrote:
On Wed, Sep 18, 2019 at 01:14:38PM +0100, Graham Hayes wrote:
Release Naming:
1. Tied: Do not change current model of geographic names - No review Name releases after major cities - https://review.opendev.org/#/c/677745/ 3. Name releases after the ICAO alphabet - https://review.opendev.org/#/c/677746/
Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_0a9abdadec887a6b&algorithm=beatpath
The scope of this vote was not clear. This was only as far as changing the naming scheme for the remaining V-X, right? Or was it meant for anything past Ussuri?
OpenStack Release Naming for V-Z was the title of the poll. The intent was we would sort out V-Z, and then worry about the post Z names.
This is proving to be harder than expected as you can see - so I am not sure what the route forward is.
If the best alternate options we had can't beat "keep it the same", then I'd say it means we should keep the same naming system until we can come up with something sufficiently compelling to switch to. I still support finding a simpler way to find names (for V->Z *and* for the rollover), but this is not super-urgent -- we have a few months to find a better system. -- Thierry Carrez (ttx)
participants (3)
-
Graham Hayes
-
Sean McGinnis
-
Thierry Carrez