Update Readme with Wiki Info

This patch cleans up the Readme and includes the missing information
that exists on the wiki:
 https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Running_the_election_itself

Once this patch is merged, the wiki will be updated to point to the
Readme file.

Story: 2001608
Task: 6569

Change-Id: Ie2644243f528a6e2b09a392436b6353feaae30ab

README.rst

@@ -9,14 +9,19 @@ and tooling to run elections.
 Election officials process
 ==========================
 
+=============
+PTL Elections
+=============
+
 Selecting Election Dates
 ------------------------
 
 Things to keep in mind when selecting election dates:
 
-* At least 48 hours in between cut-off of electorate and poll start
+* At least 48 hours in between email deadline and poll start
 * Consider extra-atcs approval deadlines
 * Should start around R-4 for nominations period
+* Allow at least a week for nomination period
 
 Preparation
 -----------
@@ -29,16 +34,17 @@ A month before election starts:
   * tox -evenv -- create-directories
 * Update index.rst to include ptl.rst
 * Commit to update website
+* Update Release Schedule
 
 A couple of weeks before election starts
-* Send 'First announce'
+* Send 'PTL Election Season' email
 
 
-PTL Candidacy round
+PTL Candidacy Round
 -------------------
 
 When PTL Candidacy start
-* Send 'Opening PTL candidacy round'
+* Send 'PTL Nominations Kickoff' email
 
 During the PTL Candidacy round:
 * Validate candidacy, e.g.:
@@ -46,11 +52,11 @@ During the PTL Candidacy round:
   * tox -evenv -- check-candidacy change_id
 * To +2 a candidate:
   * check commit link is indeed valid
-  * check filename is ircname
+  * check filename is email address
   * cursory check the candidacy statement
 * To +Workflow, checks the previous +2 details, find another commits using --limit 5 (optionals)
 
-* Check candidate list and fixes badly generated name using the exception.txt file
+* Check candidate list and fix badly generated names through changes to the exception.txt file
 
 Once the email deadline is reached:
 * Ask the TC chair to tag the governance repository
@@ -58,78 +64,108 @@ Once the email deadline is reached:
 A couple of days before the candidacy submission ends:
 * Render statistics and send 'Motivation call for PTL candidacy round', e.g.:
   * tox -evenv -- render-statistics
+* Send 'PTL Nominations Last Days' email
 
 When PTL Candidacy submission ends:
-* Send 'PTL nomination ending'
+* Send 'PTL Nominations End' email
-
-
-PTL Election round
-------------------
 
 When PreferredEmailDeadLine is reached:
 * Ask the TC chair to tag the governance repository with the tag defined in the configuration.yaml
 * When the tag is available, generate ATC rolls, e.g.:
   * tox -evenv -- generate-rolls
+  * Compare ATC rolls with at least one other election official
+
+PTL Election Round
+------------------
 
 When PTL Election begins:
 * Create CIVS page ( https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Running_the_election_itself )
 * Upload rolls
-* Send 'PTL election opening'
+  * CIVS has a maximum number of electorate emails you can upload at a time without crashing, limit to 500
+    at a time
+* Send 'PTL Voting Kickoff' email
 
 A couple of days before the PTL Election ends:
-* Send 'PTL vote motivation call'
+* Send 'PTL Voting Last Days' email
 
 When PTL Election ends:
 * Close the election and udpate the results:
   * tox -evenv -- close-election ptl
-  * edit doc/sources/pike/ptl.yaml
+  * edit doc/sources/pike/ptl.yaml to set election winners to True
 * Update index.rst to comment ptl.rst candidate list
 * Commit the change and review the results
-* Send 'PTL results'
+* Send 'PTL Results' email
 * Update governance repo:
   * tox -e venv update-governance -- --governance-repo ../governance/
 
+============
+TC Elections
+============
 
-TC Candidacy round
+Selecting Election Dates
+------------------------
+
+Things to keep in mind when selecting election dates:
+
+* Needs to conclude by S-3 (3 Weeks prior to OpenStack Summit)
+* Allow for at least 48 hours between email deadline and polling begininning
+* Allow at least a week for nomination and campaign periods
+
+Preparation
+-----------
+
+A month before election starts:
+
+* Edit elections details (timeline, cycle timeframe):
+  * Edit configuration.yaml
+  * Update index.rst to include tc.rst instead of ptl.rst
+* Commit to update website
+* Update Release Schedule
+
+A couple of weeks before election starts
+* Send 'TC Election Season' email
+
+
+TC Candidacy Round
 ------------------
 
 When TC Candidacy starts:
-* Send 'TC Candidacy Opening'
+* Send 'TC Nominations Kickoff' email
-* Update index.rst to include tc.rst instead of ptl.rst
 
 During the TC Candidacy round:
 * To +2 a candidate:
   * check candidate profile using https://www.openstack.org/community/members/
-  * check filename is ircname
+  * check filename is email address
   * cursory check the candidacy statement
 * To +Workflow, check the previous +2 details
 
 A couple of days before the candidacy submission ends:
-* Send 'Motivation call for TC Candidacy round'
+* Send 'TC Nominations Last Days' email
 
 When TC Candidacy submission ends:
-* Send 'TC nomiation ending'
+* Send 'TC End Nominations' email
 
-
-TC Election round
------------------
 When PreferredEmailDeadLine is reached:
 * Generate ATC rolls, e.g.:
   * tox -evenv -- generate-rolls
 
+
+TC Election Round
+-----------------
+
 When PTL Election begins:
 * Create CIVS page
 * Upload rolls
-* Send 'TC election opening'
+* Send 'TC Voting Kickoff' Email
 
 A couple of days before the TC Election ends:
-* Send 'TC vote motivation call'
+* Send 'TC Voting Last Days' email
 
 When TC Election ends:
 * close the election and update the results:
   * tox -e venv -- close-election tc
   * edit doc/source/pike/tc.yaml
 * Commit the change and review the results
-* Send 'TC results'
+* Send 'TC Results'
 * Update tc-election-summary.py with election statistics
-* Send 'TC election statistics'
+* Send 'TC Election Statistics'