diff --git a/pages/governance.md b/pages/governance.md index 8d58aa280..d45e968ed 100644 --- a/pages/governance.md +++ b/pages/governance.md @@ -4,15 +4,174 @@ title: "HPC Carpentry Governance" permalink: /governance/ --- -HPC Carpentry is a community effort. We meet 1200 UTC and 2200 UTC on the first -and third Thursday of every month to coordinate lesson development efforts, -share teaching experiences, and discuss feedback. We use a streamlined extract -of [Martha's Rules](https://github.com/hpc-carpentry/coordination/issues/28) -for asynchronous decision-making. Matters requiring acute executive action are -addressed by our [Steering Committee]( -https://github.com/hpc-carpentry/coordination/issues/36), which is also the -collective point of contact for The Carpentries proper. +HPC Carpentry is a community effort. We meet at 13:00 CET and 17:00 EDT on the +first and third Thursday of every month to coordinate lesson development +efforts, share teaching experiences, and discuss feedback. Matters requiring +acute executive action are addressed by our Steering Committee, which is +also the official interface between the HPC Carpentry community and +The Carpentries Executive Committee and Core Team. Unless otherwise specified, the style, governance, and rules of HPC Carpentry -default to the [The Carpentries Bylaws]( -https://docs.carpentries.org/topic_folders/governance/bylaws.html). +default to [The Carpentries Bylaws][carpentries-bylaws]. Where the two are in +conflict, The Carpentries Bylaws take precedence. + +## Charter of the HPC Carpentry Steering Committee + +Approval date +: 2023-07-00 + +Status +: pending + +### Statement of Scope + +The Steering Committee is established to provide community leadership for the +High Performance Computing Carpentry ("HPC Carpentry") lesson program. +Committee members represent the interests of the HPC Carpentry community, +overseeing project strategy and informing the actions of the Core Team and +Executive Council as they relate to the lesson program. + +### Objectives/Purpose + +Members of the Committee will share responsibility for: + +* Prioritizing lesson development and driving engagement by scheduling + brainstorming sessions, hackathons, and work parties. +* Reviewing new workshop registrations and executing on bids for assistance: + identifying experienced instructors, providing cloud resources, and assisting + with site-specific lesson materials. +* Expanding the qualified instructor pool by pairing experienced members of the + community with interested novices for mentorship and guidance. + +### Roles and Responsibilities + +1. Co-Chairpersons, responsible for: + * Leadership in advancing the aims and objectives of the Committee. + * Organizing, convening, and chairing Committee meetings: setting dates and + times, preparing agenda items and shared note documents, and notifying + Committee members and the HPC Carpentry community ahead of time. + * Updating Committee documents and bylaws. + * Direct communication with The Carpentries Executive Council and Core Team. + * Alternating duties and stepping in for co-chairs when the other is + unavailable. + * All responsibilities of a Member, outlined below. + +2. Members, responsible for: + * Participating in Committee meetings and asynchronous discussions on Slack + and GitHub. + * Recording action items and paraphrasing discussions in shared documents + for meetings discussions, hackathons, and Committee events. + * Contributing to lesson materials, directly or in an advisory capacity. + +### Operational Procedures + +Processes for recruiting new members for the committee, onboarding and +offboarding of members, and succession planning for officer roles, are detailed +in The Carpentries' [Lesson Program Governance handbook][lpgc-handbook]. + +#### Decision making process + +We use a streamlined extract of Martha's Rules for asynchronous +decision-making [[1][martha],[2][martha-3b]. + +1. Anyone may sponsor a proposal by filing an issue in the + [Coordination Repository][coordination] tagged "[proposal][proposals]". + * The sponsor of a proposal is not necessarily responsible for implementing + it, though they can volunteer for that role. + * As a worldwide team, a lot of discussion will be asynchronous. Clear and + complete presentation of the Proposal in the sponsoring Issue is + encouraged. + * The sponsor is encouraged to announce their proposal in the + `#hpc-carpentry` channel of The Carpentries' Slack server and a new thread + in the [discuss-hpc][discuss-hpc] mailing list on TopicBox. The + announcements must link to the GitHub issue where the proposal is + defined, as that is the primary forum for discussion. +1. Proposals must include: + * a one-line summary (the subject line of the issue) + * any required background information, including linked issues + * the full text of the proposal + * pros and cons + * possible alternatives +1. Members of the community are invited to indicate their sense of the + proposal: + * Who likes the proposal? React with 👍 (`:+1:`) + * Who can live with the proposal? React with 👀 (`:eyes:`) + * Who is uncomfortable with the proposal? React with 👎 (`:-1:`) +1. Asynchronous discussion of the proposal can occur as comments on the Issue, + in the Slack channel, on the TopicBox mailing list, and during the next + Coworking Hours. +1. At least 24 hours prior to the next Coordination Meeting, check to make sure + the proposal is included in the agenda for discussion. +1. When the proposal comes up, if the sponsor is present, they will be given + time to present it. Time will be allowed for participants to + read the proposal and review any written discussion. +1. Every meeting attendee will review and update their vote on the proposal. +1. If any members are uncomfortable 👎, time will be allowed to hear their + objections; discussion will be moderated by the meeting chairperson. +1. Following the discussion, each attendee shall update their vote. +1. If this is the last of the Coordination Meetings for the day, and all votes + are either in favor 👍 or not opposed 👀, then the proposal is + accepted. +1. If any votes are in opposition 👎, the proposal is referred back to the + sponsor for further work. + +#### Meetings + +Meetings of the Steering Committee are public. They are scheduled on a shared +calendar, which is maintained [online][gcal]: it can be added to any calendar +app using its live `ics` link, + +``` html +https://calendar.google.com/calendar/ical/mjtehtfa2recdfm6fcte01eatc%40group.calendar.google.com/public/basic.ics +``` + +Minutes of past meetings are available in [the `minutes` directory][minutes] of +the Coordination repository. + +### Core Team Liaison + +Toby Hodges, Director of Curriculum for The Carpentries + +### Elected Members + +The [last election][nominees23] concluded on 22 June 2023, with nine unique +voters, via [ElectionBuddy][election23]. Rohit Goswami separated from the +Steering Committee, and no additional community members were nominated. + +| Member | Role | Term Began | +| --- | --- | --- | +| Trevor Keller | Co-chair | 2021-05-20 | +| Andrew Reid | Co-chair | 2021-05-20 | +| Alan O'Cais | Co-chair | 2021-05-20 | +| Annajiat Alim Rasel | Co-chair | 2021-05-20 | +| Wirawan Purwanto | Co-chair | 2021-05-20 | + +#### Past Elections + +* The [2022 election][election22] concluded on 17 June 2022, with six unique + voters. The inaugural Committee members were all re-elected, + and Rohit Goswami was inaugurated. +* The [first election][election21] concluded on 20 May 2021, with sixteen + unique voters. The inaugural Steering Committee members were Alan O'Cais, + Andrew Reid, Annajiat Alim Rasel, Trevor Keller, and Wirawan Purwanto. + + + +[nominees23]: https://secure.electionbuddy.com/results/4565C4LKQ29G +[election23]: https://github.com/hpc-carpentry/coordination/issues/124 +[election22]: https://github.com/hpc-carpentry/coordination/issues/114 +[election21]: https://github.com/hpc-carpentry/coordination/issues/44 + + + +[carpentries-bylaws]: https://docs.carpentries.org/topic_folders/governance/bylaws.html +[coordination]: https://github.com/hpc-carpentry/coordination +[discuss-hpc]: https://carpentries.topicbox.com/groups/discuss-hpc +[gcal]: https://calendar.google.com/calendar/?cid=bWp0ZWh0ZmEycmVjZGZtNmZjdGUwMWVhdGNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ +[gcal-ics]: https://calendar.google.com/calendar/ical/mjtehtfa2recdfm6fcte01eatc%40group.calendar.google.com/public/basic.ics +[lpgc-handbook]: https://docs.carpentries.org/topic_folders/governance/lesson-program-policy.html +[martha]: https://doi.org/10.1177/088610998600100206 +[martha-3b]: https://third-bit.com/files/2020/08/marthas/ +[minutes]: https://github.com/hpc-carpentry/coordination/minutes +[proposals]: https://github.com/hpc-carpentry/coordination/labels/proposal +[topicbox]: https://carpentries.topicbox.com/groups/maintainers-hpc