Add elections notes
This commit is contained in:
parent
43bcfacb54
commit
10f418e98b
1 changed files with 57 additions and 0 deletions
57
modules/pgm_guide/pages/elections.adoc
Normal file
57
modules/pgm_guide/pages/elections.adoc
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
= Elections
|
||||
|
||||
The Fedora Program Manager is responsible for conducting elections for various bodies within Fedora.
|
||||
After each release, the Fedora Council, Mindshare Committee, and Fedora Engineering Steering Committee run elections.
|
||||
Other teams may request elections if they have a need.
|
||||
|
||||
The Fedora Community Action and Impact Coordinator (FCAIC) is the backup elections wranger.
|
||||
The FCAIC & FPgM cannot be candidates for elected positions.
|
||||
|
||||
NOTE: FESCo has a https://fedoraproject.org/wiki/FESCo_election_policy[separate election policy] that requires more candidates than open seats.
|
||||
|
||||
== Pre-voting
|
||||
|
||||
WARNING: The wiki-based voting process is a giant pain.
|
||||
Perhaps you would like to extend the voting app to allow nomination and election interviews.
|
||||
|
||||
* Make sure an "I Voted" badge has been created for this election cycle.
|
||||
* Edit https://fedoraproject.org/wiki/Elections[the Elections wiki page]
|
||||
* Open a ticket with each group to see if they want to change the questions
|
||||
* Update wiki pages for each election: update the leaving members and clear the candidates
|
||||
* Open the nominations
|
||||
* Candidates will post interviews in private issues on the poorly-named https://pagure.io/fedora-magazine-proposals/issues[fedora-project-schedule] repo.
|
||||
* 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
|
||||
|
||||
TIP: Get the FCAIC to review posts to make sure nothing is misspelled or mis-copied, etc.
|
||||
|
||||
NOTE: At one time, we were hoping to have the Fedora Podcast conduct interviews with candidates as well, but that has fizzled.
|
||||
|
||||
NOTE: A long time ago, we conducted IRC town halls with candidates.
|
||||
We stopped doing that.
|
||||
|
||||
== Voting setup
|
||||
|
||||
The elections app runs on https://elections.fedoraproject.org[elections.fedoraproject.org].
|
||||
|
||||
* maximum range: # of candidates
|
||||
* URL: link to wiki page with nominations
|
||||
* “Candidates are FAS users?” validation check is buggy, don't use it
|
||||
* Admin groups: automatically includes the elections group
|
||||
* When adding users, add link to interview on commblog
|
||||
|
||||
WARNING: 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 31 elections.
|
||||
|
||||
== After elections
|
||||
|
||||
* Send results to mailing lists
|
||||
* Update pagure groups, wiki pages, mailing lists
|
||||
|
||||
TIP: Convincing teams to give you admin access to things will make life easier.
|
||||
Also, if I document these things better, that would make life easier, too.
|
||||
Maybe for Fedora 31.
|
||||
Loading…
Add table
Add a link
Reference in a new issue