|
| 1 | +# Astropy Election Procedures |
| 2 | + |
| 3 | +## Overview |
| 4 | + |
| 5 | +Astropy votes are managed with the [Helios Voting platform](https://heliosvoting.org) and |
| 6 | +announced publicly via the astropy-dev mailing list and the OpenAstronomy Discourse forum. |
| 7 | + |
| 8 | +## Procedure for creating an election |
| 9 | + |
| 10 | +1. Set a date for the election and announce the election |
| 11 | + - This sets various deadlines that must be followed by nominees and voting members / CoCo nominees |
| 12 | + - Election start date must be at least 4 weeks after the announcement email |
| 13 | + - In announcement email, call for additional nominees |
| 14 | + - Deadline for nominations at least 2 weeks before election |
| 15 | + - The election is open for 2 weeks once it’s open |
| 16 | + - [See template email below](#Email-templates) |
| 17 | + - Send email to list of voting members (not just astropy-dev) - the email list in the |
| 18 | + Google drive. That way, you see if emails bounce and can hunt down a corrected email address |
| 19 | +2. Collect nominees for new voting members / CoCo members and inform them |
| 20 | + - Collect nominations from roles survey and emails to coordination committee |
| 21 | + - Email nominees to inform them of nomination |
| 22 | + - Deadline to accept nomination 1 day before election opens |
| 23 | + - Inform nominees that to accept the nomination, they must send a few sentence description of |
| 24 | + their contributions to astropy and justification for voting member status to the CoCo |
| 25 | + [See template email below](#Email-templates) |
| 26 | +3. Post nominee statements to voting-members topic in OpenAstronomy Astropy Discourse |
| 27 | + - The election manager posts the nominee statements in the OpenAstronomy Discourse |
| 28 | + voting-members topic (private to only voting members, as described in APE0) |
| 29 | + - One post per nominee |
| 30 | +4. Collect any additional ballot measures to be voted on (e.g., changes to APE0, etc...) |
| 31 | + - Post the ballot measures in the OpenAstronomy Discourse voting-members |
| 32 | + - One post per ballot measure |
| 33 | +5. Set up the election on Helios Voting (see next section) |
| 34 | + |
| 35 | +## Running an election with Helios |
| 36 | + |
| 37 | +1. Log into [helios](https://vote.heliosvoting.org/) |
| 38 | +2. Click “Create an election” |
| 39 | + - Short name convention: astropy-\<description\>-\<month\>-\<year\> |
| 40 | + For example: astropy-voting-members-july-2022 |
| 41 | + - Name convention: Astropy \<description\> — \<month\> \<year\> |
| 42 | + For example: Astropy Voting Members — July 2022 |
| 43 | + - Description: Write a one sentence description of the election |
| 44 | + - Check “Private?” to ensure that only registered voters can see the ballot |
| 45 | + - Voting starts at: select the predetermined date for the election to start |
| 46 | + (12:00 UTC for the time) |
| 47 | + - Voting ends at: two weeks after the start date |
| 48 | + - All other field left as default values |
| 49 | +4. Now we have to add questions to the ballot. Click the “questions(0)” link to add a new question |
| 50 | + - Add one question for each nominee: “Do you support adding \<NAME\> as an Astropy voting member?” |
| 51 | + - Make each required by selecting “select between 1 and 1 answers” |
| 52 | + - Add “Yes”, “No”, “Abstain” as possible answers |
| 53 | + - Add one question for each ballot measure |
| 54 | + - Make each required by selecting “select between 1 and 1 answers” |
| 55 | + - Add “Yes”, “No”, “Abstain” as possible answers |
| 56 | +5. Make sure the list of current voting members is complete |
| 57 | + - The list is in [google sheets](https://docs.google.com/spreadsheets/d/18VOl-EAwefcwi1aNLWXnZ0-a9WTBx4ry_QB8t23tYKw/edit#gid=0) (permission required). |
| 58 | + - Download the list as a CSV, remove the first row (the headers), and upload as registered voters |
| 59 | +6. Freeze the ballot and set it to open voting at the start time |
| 60 | + - Go to the “voters & ballots” link and prepare / send an email with voting |
| 61 | + information to all voters |
| 62 | + - DO NOT copy paste to fill the “Body” section of the form, instead use that space to add |
| 63 | + any additional info you want to send to all voters. |
| 64 | +7. After the ballot closes, “compute encrypted tally” and then “compute results” |
| 65 | + - Send the results email |
| 66 | +8. Add newly voting members to organization |
| 67 | + - Create a PR to add any newly-added voting members to https://github.com/astropy/astropy.github.com |
| 68 | + (see https://github.com/astropy/astropy.github.com/pull/496 for an example) |
| 69 | + - Add new voting members and their emails to the google sheet |
| 70 | + |
| 71 | + |
| 72 | +## Email templates |
| 73 | + |
| 74 | +**Note:** any text in “\<\>” should be updated for future emails. |
| 75 | + |
| 76 | +### Election announcement |
| 77 | + |
| 78 | +Subject: Announcing Astropy Voting Member Election: \<July 2022\> |
| 79 | + |
| 80 | +Dear Astropy Community, |
| 81 | + |
| 82 | +The next Astropy Voting Member election will be on \<July 8, 2022.\> |
| 83 | + |
| 84 | +We have already received some nominations from the Roles survey, but are accepting additional |
| 85 | +nominations for new voting members until the end of \<June 21\> (anywhere on Earth). |
| 86 | +To nominate someone (or yourself) to be a voting member, please fill out this form: |
| 87 | +https://forms.gle/f1hi6MNEmw1RzYPY7 |
| 88 | + |
| 89 | +For the Coordination Committee, |
| 90 | +\<sender name\> |
| 91 | + |
| 92 | +<hr/> |
| 93 | + |
| 94 | +Subject: Announcing Astropy Coordination Committee Election: \<September 2022\> |
| 95 | + |
| 96 | +Dear Astropy Community, |
| 97 | + |
| 98 | +The next Astropy Coordination Committee (CoCo) election will begin on \<September 25, 2022\>. |
| 99 | +One seat is available as \<name's>\ terms is coming to an end. The new member will serve a |
| 100 | +3-year term. More details about the process are described in APE0. |
| 101 | + |
| 102 | +Nominations are open now and will close on \<Friday, September 23\> (anywhere on Earth). |
| 103 | +Anyone is welcome to nominate. To nominate someone (or yourself) to be a CoCo Member, |
| 104 | +please fill out the Nomination Form: \<link\>. |
| 105 | + |
| 106 | +Nominees will be asked via email whether they wish to accept their nomination. |
| 107 | +If they accept, the nominee will be asked to provide a short statement on the |
| 108 | +Open Astronomy Discourse. |
| 109 | + |
| 110 | +For the Coordination Committee, |
| 111 | +\<sender name\> |
| 112 | + |
| 113 | +### Inform nominees |
| 114 | + |
| 115 | +Subject: Accepting Nomination as an Astropy Voting Member |
| 116 | + |
| 117 | +Dear \<NOMINEE\>, |
| 118 | + |
| 119 | +Congratulations, you have been nominated to be a new voting member for the Astropy Project! |
| 120 | +If you are not sure about the election process, or the expectations of the role, we encourage you |
| 121 | +to look over APE0 (https://github.com/astropy/astropy-APEs/blob/main/APE0.rst#the-voting-members). |
| 122 | +Being a voting member principally means agreeing to vote in Astropy elections, which occur at most |
| 123 | +a few times per year (i.e. this is not a serious time commitment on top of your existing role(s) |
| 124 | +within the project). |
| 125 | + |
| 126 | +If you wish to accept this nomination, please respond to this email indicating whether you would |
| 127 | +like to accept this nomination. If you do accept the nomination, please write a few sentence |
| 128 | +description of your contributions to the Astropy Project that demonstrates the points defined |
| 129 | +in APE0 (https://github.com/astropy/astropy-APEs/blob/main/APE0.rst#membership) and send them to |
| 130 | +the election managers (reply-all to this email). |
| 131 | + |
| 132 | +If you do not reply by the end of the day \<July 7\>, we will assume you do not wish to accept |
| 133 | +this nomination. You can also explicitly decline by responding to this email. |
| 134 | + |
| 135 | +For the Coordination Committee |
| 136 | +\<sender name\> |
| 137 | + |
| 138 | +<hr/> |
| 139 | + |
| 140 | +Subject: Nomination to be an Astropy Coordination Committee Member |
| 141 | + |
| 142 | +Dear \<NOMINEE\>, |
| 143 | + |
| 144 | +Congratulations, you have been nominated to be a new member of the Coordination Committee |
| 145 | +(CoCo) for the Astropy Project! If you are not sure about the election process, or the |
| 146 | +expectations of the role, we encourage you to look over APE0 |
| 147 | +(https://github.com/astropy/astropy-APEs/blob/main/APE0.rst#the-coordination-committee). |
| 148 | +Being a CoCo member has a number of responsibilities that are outlined in APE0, but feel |
| 149 | +free to reach out to current CoCo members with any questions. |
| 150 | + |
| 151 | +Please respond to this email indicating whether you would like to accept or decline |
| 152 | +this nomination. If you accept the nomination, you must also post a candidate statement on |
| 153 | +the OpenAstronomy Discourse forum. A direct link to start a new post in the Astropy category |
| 154 | +with the “Astropy” and “CoCo-Election” tags is: https://community.openastronomy.org/new-topic?title=2022%20CoCo%20Election:Name&category=Astropy&tags=astropy,coco-election . |
| 155 | +If you don’t already have an account, you can sign up first and then follow the link to |
| 156 | +auto-fill your post. You don’t need to do anything other than posting a candidate statement to |
| 157 | +accept this nomination and stand in the election. Voters will be directed to this candidate |
| 158 | +statement at the time of the election. |
| 159 | + |
| 160 | +To accept the nomination, you must post a candidate statement by the end of the day |
| 161 | +\<September 24, 2022\>. |
| 162 | + |
| 163 | +For the Coordination Committee, |
| 164 | +\<sender name\> |
0 commit comments