Pele Suite Governance

The Pele Suite is led under an open governance model with three bodies: a Steering Committee, a Technical Committee and an Advisory Panel. Their roles, members and decision processes are described below.

Steering Committee

Oversees the organization: administrative settings, repositories and the governance structure itself. It can veto Technical Committee decisions.

Technical Committee

The core governance and action body. Discusses the direction of the suite and decides implementation priorities and strategies.

Advisory Panel

Recommends future directions for the suite to maximize its scientific and industrial impact.

Steering Committee

Current roster

  • Marc Day (chair)
  • Bruce Perry
  • Jackie Chen
  • John Bell
  • David Montgomery
GitHub team

Role

Members of the Steering Committee (SC) can change organizational settings of the software and perform administrative operations such as renaming, moving or archiving repositories and changing branch protection rules.

SC members can call votes for decisions or requests for input from technical, governance or advisory groups. The SC can veto decisions of the Technical Committee (TC) by a majority vote within the SC; the TC can override an SC veto with a two-thirds majority vote. The SC can change the governance structure by unanimous SC vote.

SC decisions are documented in developer meeting notes and/or on the GitHub repository.

Decision process

Decisions of the SC usually happen in the developer meetings, via e-mail or public chat. Decisions are made in a non-confidential manner by the majority of votes cast by SC members. Votes can be cast asynchronously, e.g., over a period of 1–2 weeks. In a tie, the chair of the SC breaks it.

Appointment process

A chair and new members of the SC can be appointed by unanimous vote of the current SC members. SC members are expected to attend and contribute to regular developer meetings. SC members can resign, and they can be removed by majority vote, e.g., due to inactivity, inappropriate or otherwise negative behavior, or other reasons.

Technical Committee

Current roster

  • Marc Day (chair)
  • Bruce Perry
  • Weiqun Zhang
  • Thomas Howarth
  • David Montgomery
  • Anne Felden
  • Bruno Savard
  • Martin Rieth
  • Lucas Esclapez
  • Andy Nonaka
  • Ann Almgren
  • Jon Rood
GitHub team

Role

The Technical Committee (TC) is the core governance and action body. Under normal operations, most ideas regarding the direction of the Pele Suite are discussed here, and decisions are made about implementation priorities and strategies.

TC members are valued, vetted developers of the Pele Suite. Their contributions include, but are not limited to, code and algorithms, pull requests, support on issues and user discussions, documentation and tutorials, visualizations, testing and benchmarking, and gathering poll data from the Advisory Panel.

TC members:

  • are expected to attend and contribute to regular developer meetings;
  • can triage (add and remove labels on) pull requests, issues and GitHub discussions, and comment on and review pull requests;
  • are expected to seek approval from another maintainer for their own changes, except under exigent circumstances;
  • lead and weigh in on technical discussions and, if needed, can call for a TC vote on a technical decision;
  • can merge or close pull requests and issues, and moderate (including blocking or muting) bad actors.

The TC can propose governance changes to the SC.

Decision process

Discussion in the TC usually happens in the developer meetings or by e-mail. Developer meetings can be proposed by any member of the SC or TC, and should be announced to the entire SC and TC by the TC chair with enough lead time to maximize attendance.

If a TC member calls for a vote, it is decided by the majority of votes cast, provided that at least half of the TC members participate. If fewer than half of the TC members vote, the SC makes the decision. Votes are cast in a non-confidential manner, and decisions are documented in the developer meeting notes maintained in the GitHub repository.

Individual TC members can suggest actions by the TC. A suggestion must be seconded by another TC member. Any TC member has the right to oppose the suggestion and call for a TC vote on the decision.

Appointment process

New TC members can be suggested by SC or TC members. Confirming a new TC member requires a majority of votes cast by either the SC or the TC, and the SC can veto any new appointment. SC members can also be TC members.

TC members can resign, or be removed by majority vote of either the TC or the SC, due to inactivity, inappropriate or otherwise negative behavior, or other reasons.

Advisory Panel

Current roster

  • Fabrizio Bisetti
  • Suo Yang
  • Heinz Pitsch
  • Andrew Aspden
  • Andrea Gruber
  • Jackie Chen
  • Haiou Wang (Zhejiang)
  • Aditya Konduri
GitHub team

Role

Members of the Advisory Panel (AP) are encouraged to give regular recommendations to the TC on future directions for the Pele Suite, such as infrastructure capabilities, physical and modeled processes to incorporate, and validation and verification activities, to maximize the scientific and industrial impact of the software.

The SC and TC poll the AP by e-mail one to two times per year for updated recommendations on Pele development. AP recommendations should be shared publicly and documented on GitHub. The TC responds to the AP on the feasibility of suggestions, plans for implementation, and the status of previous suggestions.

Decision process

Input from the AP is usually gathered via e-mail or public chat and forwarded to the TC for consideration and response. Group input from the AP is given in a non-confidential manner by the majority of votes cast by AP members, and should be addressed by the TC as described above. AP input can be gathered asynchronously, e.g., over a period of 1–2 weeks.

Appointment process

New members of the AP can be appointed by unanimous vote of the current AP members. AP members are expected to respond to e-mailed polls for input initiated by other AP members and by the TC. AP members can resign, or can be removed by majority vote, e.g., due to inactivity, inappropriate or otherwise negative behavior, or other reasons.

Former members

Former (e.g., inactive) members of the SC, TC and AP play no role in the governance of the Pele Suite and are not kept on the rosters. They are instead acknowledged in GitHub contributor tracking, the Pele Suite documentation, references and elsewhere as appropriate.