Skip to content

Latest commit

 

History

History
39 lines (35 loc) · 3.58 KB

directors-working-agreement.md

File metadata and controls

39 lines (35 loc) · 3.58 KB

Directors Working Agreement

Our Pledge

As LineageOS Project Directors, we:

  • Commit to working among ourselves and contributors with professionalism and respect - providing well reasoned arguments for any policy decision made.
  • Commit to establishing project goals and execution plan.
  • Commit to ensuring a safe and productive working environment for our contributors - adhering to the Code of Conduct.

Our Rules:

  1. We will operate on a majority rules basis (5 out of 9) for most scenarios, with the following exceptions:
    • Device or software deviations/exceptions from our core product must be approved by no less than 3 Project Directors (see LineageOS Device support requirements).
    • Items of significant controversy or substantial change from prior project precedent will require a super-majority of 6 out of 9 Directors in favor.
      • Project Directors will decide what issues constitute the need for this measure prior to discussion on it.
      • For items requiring a super-majority, contributors will have an open response period where they may share their opinions and thoughts on the matter in a medium moderated by Project Directors.
  2. For items of legal consequence, that is direct or indirect legal and/or financial exposure to the project, veto power is reserved for LineageOS LLC owners.
  3. For items of technical nature and not covered by the above rules, prior to Directors vote, we allow input on the topic from the contributors with domain knowledge/expertise.
  4. Decisions made by Directors, if contributor facing, MUST be communicated by the following mechanism:
    • Creating an issue in the GitLab announcements project for contributor visibility.
  5. Decisions made by Directors, if user facing, SHOULD be communicated by the following mechanisms:
    • A blog post, wiki update, or other artifact for public consumption of the decision.
  6. Directors may step down on their own at any point they wish.
    • A replacement for departing Directors will be voted on by existing Directors, after soliciting feedback and recommendations from the contributor pool.
    • Replacement Directors should be evaluated on a meritocracy basis and ability to commit the time necessary to fulfill the role.
  7. A Director may be removed from the position if ALL of the following conditions are met:
    • A Director is found to be in continued violation of the Code of Conduct or this Working Agreement, after an initial warning.
    • A vote among Project Directors constituting a supermajority (6 out of 9).
    • At least one LineageOS LLC owner signs off on result of the vote.
  8. A Director will be removed due to inactivity if ALL of the following conditions are met:
    • Lack of new commits for a period of 9 months or more.
    • Lack of contribution to processes or infrastructure for a period of 9 months or more.
    • Lack of participation in chats for a period of 9 months or more.
    • Lack of remediation after no less than 3 attempts to contact the Director in question.
    • At least one LineageOS LLC owner signs off on the removal.
    • NOTE: If a Director is removed in good standing via this method, the following actions will take place:
      • They will be moved from the "Head Developers" Gerrit group to the "Retired Directors" Gerrit group, which inherits the "Committers-Inactive" group, thus retaining global Code-Approval permissions.
      • Their GitHub/GitLab permissions will be restricted to that of a Maintainer.
      • They will remain in any/all private Directorial communication channels with retained ability to provide thoughts on project direction/decisions.