Elecciones

La Gestión del Programa Fedora es la responsable de dirigir las elecciones de los diversos cuerpos dentro de . Después de cada revisión, Fedora Council, Mindshare Committee y Fedora Engineering Steering Committee hacen elecciones. Otros equipos pueden pedir elecciones si lo necesitan.

El Coordinador de Impacto y Acción Comunitaria de Fedora (FCAIC) es el encargado de las elecciones de respaldo. La FCAIC y FPgM no pueden ser candidatos para cargos electos.

FESCo tiene una política de elección separada que requiere más candidatos que asientos disponibles.

Votación previa

El proceso de votación basado en wiki es un gran dolor. Quizás deberíamos extender la app de votación para permitir entrevistas de nominación y elección.

Antes del período de nominación

  • Asegurar que se ha creado una insignia "I Voted" para este ciclo de elección.

  • Edit the election banner template in the wiki to update the dates and current status

  • Edit the Elections docs page

  • Open a ticket with each group to see if they want to change the questions

  • Update wiki pages for each election:

    • Update the list of leaving members

    • Clear the candidates table

    • Remove edit protection

  • Open the nominations by announcing to the Community Blog and mailing lists

During/after the nomination period

  • Update the templates/* files in the repo (ssh://git@pagure.io/tickets/fedora-project-schedule.git) with the new questions

  • Edit the election banner template in the wiki to update the dates and current status

  • Candidates will post interviews in private issues on the poorly-named fedora-project-schedule repo.

  • If the Community Blog post announcing nominations is set to "sticky", un-sticky it.

After the interview period

  • Convert interviews to community blog

    • One post per-candidate

    • Include FAS acocunt, IRC, wiki page (see previous examples)

    • Set the candidate as the author

  • Write a wrap-up post (look at 2017 elections interview as example). link to interview post and user wiki

Get the FCAIC to review posts to make sure nothing is misspelled or mis-copied, etc.
At one time, we were hoping to have the Fedora Podcast conduct interviews with candidates as well, but that has fizzled.
A long time ago, we conducted IRC town halls with candidates. We stopped doing that.

Voting setup

The elections app runs on elections.fedoraproject.org.

  • maximum range: # of candidates

  • URL: link to wiki page with nominations

  • Admin groups: automatically includes the elections group

  • When adding users, add link to interview on commblog

  • Edit the election banner template in the wiki to update the dates and current status

The “Candidates are FAS users?” validation check is buggy, don’t use it. Ben Cotton hopes to have this fixed before the Fedora 32 elections.
The logic to enforce FESCo’s CLA+1 requirement is too strict. Council and Mindshare do not have that requirement. Ben Cotton hopes to have this fixed before Fedora 32 elections.

After elections

  1. Post the results to the Community Blog

  2. Send results with a link to the Community Blog to the announce mailing list

  3. Send individual election results to the council-discuss, devel-announce, and mindshare mailing lists

  4. Update Pagure groups, wiki pages, mailing lists as described below

  5. Edit the election banner template in the wiki to update the dates and current status

  6. Edit the Elections docs page

Council

FESCo (Engineering)

Mindshare

Convincing teams to give you admin access to things will make life easier.