Skip to content

Latest commit

 

History

History
64 lines (32 loc) · 5.5 KB

STEERING.md

File metadata and controls

64 lines (32 loc) · 5.5 KB

Steering Committee

The Paketo Steering Committee is the set of individuals who are responsible and accountable for guiding the Paketo project in a holistic manner towards achieving its goals. It currently consists of three members who help to administer the project and provide feedback and guidance on proposals that have project-wide impact.

Composition

The composition of the Steering Committee will align to the following specifications, which is similar to what is in the Cloud Foundry Foundation Charter Section 7.b.

  1. The Steering Committee will be composed of three (3) members.

  2. Each Steering Committee member will be elected to a two-year term.

  3. There will be an annual election to determine the composition of the Steering Committee for the following year. Two seats will be up for election in one year and one will be up for election the following year.

  4. Employees from the same company or Related Companies (as defined in Section 9) should not hold more than one Steering Committee seats.

    a. During any Steering Committee election, if the Steering Committee membership would exceed this limit even after the natural cycle of Steering Committee seat term expirations, enough Steering Committee members must resign for it to be possible for the election to yield a diverse enough Steering Committee.

    b. If a Steering Committee election cannot produce a diverse enough Steering Committee, the limit will not apply until the next election cycle.

    c. When a change in employment of a Steering Committee member causes the Steering Committee membership to exceed this limit, that Steering Committee member will NOT be required to resign their Steering Committee membership.

  5. One Steering Committee seat is reserved for a “community champion”, defined as a person NOT working for a corporation that is a paying member of the Cloud Foundry Foundation. If there is no champion candidate in a given election, this requirement is nullified.

Election Participation

Eligibility to participate in the Steering Committee elections process will align to the following specification, which is similar to the Cloud Foundry Foundation Charter Sections 7.e.i and 7.e.ii.

Candidate Eligibility

  1. Current Paketo Buildpacks Steering Committee members, Subteam Maintainers or Contributors who have maintained that status for at least 3 months immediately preceding the voting.

  2. If a community member is nominated as a candidate but does not meet these requirements, they may petition the Steering Committee for eligibility. In a case where the Steering Committee declines an eligibility request, the requestor may appeal that decision to the Cloud Foundry Governing Board.

  3. Candidates, if eligible, may self-nominate or be nominated by an individual who is qualified as a Steering Committee voter as outlined in that section.

Voter Eligibility

  1. Any individual who has contributed to Paketo Buildpacks in the twelve months prior to the election is eligible to vote in the Steering Committee election.

  2. Contributions include, but are not limited to, opening PRs, reviewing and commenting on PRs, opening and commenting on issues, writing design docs, commenting on design docs, participating in mailing list discussions and participating in working groups.

  3. Each election cycle, an initial set of voters will be identified through automated reporting. Any individual who has at least 10 measurable contributions in the last 12 months will be automatically added to the eligible voter list.

  4. If a community member has contributed over the past year but is not captured in automated reporting, they will be able to submit an eligibility form to the current Steering Committee who will then determine whether this member will be eligible. In a case where the Steering Committee declines an eligibility request, the requestor may appeal that decision to the Cloud Foundry Governing Board.

Election Method and Tools

  1. If the number of candidates is equal to or less than the number of Steering Committee seats available to be elected, the candidates shall be approved after the nomination period has closed.

  2. If there are more Qualified Nominees than open Steering Committee seats available for election, all eligible voters shall elect the Steering Committee members using a time-limited Condorcet ranking using the Schulze method.

  3. Elections may be run either via the Condorcet Internet Voting Service or via a deployment of Elekto administered by the CFF staff.

Steering Committee Member Resignations or Removal

The process for handling Steering Committee member resignations or removal will align to the following specification which is similar to the Cloud Foundry Foundation Charter Sections 7.f.

  1. In the case where a Steering Committee member resigns or is removed from the Steering Committee by the Governing Board, the remaining members of the Steering Committee will work with the Governing Board to determine whether the vacant seat either will remain vacant until the next annual election cycle, or will be filled by using the results of the latest election.

  2. When making this decision, the remaining members of the Steering Committee should consider whether too much time has elapsed since the latest election cycle for its results to represent the community adequately.