Skip to content

Commit 12f2ee8

Browse files
authored
Merge pull request #96 from hpc-carpentry/elections
SC and Elections
2 parents 36110e6 + 636e46a commit 12f2ee8

File tree

1 file changed

+78
-10
lines changed

1 file changed

+78
-10
lines changed

pages/governance.md

Lines changed: 78 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,83 @@ title: "HPC Carpentry Governance"
44
permalink: /governance/
55
---
66

7-
HPC Carpentry is a community effort. We meet 1200 UTC and 2200 UTC on the first
8-
and third Thursday of every month to coordinate lesson development efforts,
9-
share teaching experiences, and discuss feedback. We use a streamlined extract
10-
of [Martha's Rules](https://github.com/hpc-carpentry/coordination/issues/28)
11-
for asynchronous decision-making. Matters requiring acute executive action are
12-
addressed by our [Steering Committee](
13-
https://github.com/hpc-carpentry/coordination/issues/36), which is also the
14-
collective point of contact for The Carpentries proper.
7+
HPC Carpentry is a community effort. We meet twice on the first and third
8+
Thursday of every month to coordinate lesson development efforts, share
9+
teaching experiences, and discuss feedback.
10+
11+
We use a streamlined extract of [Martha's Rules][hpc-martha] for asynchronous
12+
decision-making. Matters requiring acute executive action are addressed by our
13+
Steering Committee which is also the collective point of contact for The
14+
Carpentries proper.
1515

1616
Unless otherwise specified, the style, governance, and rules of HPC Carpentry
17-
default to the [The Carpentries Bylaws](
18-
https://docs.carpentries.org/topic_folders/governance/bylaws.html).
17+
default to the [The Carpentries Bylaws][cc-bylaw].
18+
19+
## Steering Committee
20+
21+
HPC Carpentry is a global volunteer community. Executive decisions are made by
22+
a five-member Steering Committee, which also serves as the point of contact for
23+
The Carpentries.
24+
25+
As of June 22, 2023, the Steering Committee members are:
26+
27+
* Trevor Keller, NIST ([@tkphd](https://github.com/tkphd))
28+
* Andrew Reid, NIST ([@reid-a](https://github.com/reid-a))
29+
* Alan O'Cais, CECAM ([@ocaisa](https://github.com/ocaisa))
30+
* Annajiat Alim Rasel, BRAC ([@annajiat](https://github.com/annajiat))
31+
* Wirawan Purwanto, ODU ([@wirawan0](https://github.com/wirawan0))
32+
33+
## Elections
34+
35+
HPC Carpentry holds Steering Committee elections each June.
36+
37+
Interested parties must have an active GitHub account.
38+
39+
As a small volunteer organization, our aim is to make elections
40+
straight-forward and reasonably secure. The process is as follows.
41+
42+
1. Towards the end of May, a Committee member posts a notification to the
43+
various and sundry communications channels that "June is Election Month!"
44+
The message should encourage people who have not served to consider
45+
doing so.
46+
2. On or before the first Thursday of June, a Steering Committee member shall
47+
create an Issue on [hpc-carpentry/coordination][hpc-coord] to take
48+
nominations for Steering Committee membership.
49+
3. Interested persons should add a comment on the Issue beginning with their
50+
name. Nomination replies may optionally include a brief statement of
51+
interest, intent, suitability, etc.
52+
4. Any person whose nomination reply receives at least one &#128077 `:+1:`
53+
reply is duly nominated, and shall appear on the election ballot.
54+
5. The nomination period will end _one week_ after it opens, to allow for
55+
asynchronous online engagement.
56+
6. On the second Thursday of June, a Steering Committee member shall close the
57+
Nomination thread and use [ElectionBuddy][eb] or equivalent online service
58+
to create a ballot with the name and GitHub user handle of each nominee.
59+
* The ballot should represent a "plurality" vote, with many candidates for
60+
the same position.
61+
* Voters should select at least 3 candidates, and at most 5 candidates.
62+
* The ballot closes one week after it opens.
63+
7. After the regularly scheduled meeting ends on the third Thursday of June,
64+
a Steering Committee member shall confirm the Election has closed and review
65+
the outcome. In case of fraudulent activity, the entire Steering Committee
66+
will confer and decide the best course of action.
67+
8. Candidates who receive at least one vote will be assigned to the open seats
68+
in descending order of votes. The result shall be announced promptly on all
69+
available communications channels, and this page of the Website shall be
70+
updated with their names, contact information, and relevant media, such as
71+
photos.
72+
9. The new Steering Committee shall assume responsibility for all meetings and
73+
activities from July 1 onward.
74+
75+
## By-Elections
76+
77+
In the event a Steering Committee seat is vacated outside the month of June, a
78+
by-election shall be conducted within sixty (60) days. The procedure will be the
79+
same as the annual election, except that voters may select only one (1)
80+
candidate.
81+
82+
<!-- links -->
83+
[eb]: https://electionbuddy.com
84+
[hpc-coord]: https://github.com/hpc-carpentry/coordination
85+
[hpc-martha]: https://github.com/hpc-carpentry/coordination/issues/28
86+
[cc-bylaw]: https://docs.carpentries.org/topic_folders/governance/bylaws.html

0 commit comments

Comments
 (0)