Publish Directors Working Agreement

Change-Id: Ied7e44e3a6c4a5eeea1a7bccbd7ef16ce20a894d

2 files changed, 32 insertions, 2 deletions

diff --git a/README.md b/README.md
index 14dd4c3..30868b9 100644
--- a/README.md
+++ b/README.md
@@ -5,5 +5,6 @@ This repository contains a set of governance documents for the LineageOS Project
 
 Current documents are listed below.
 
-[Device Support Requirements](device-support-requirements.md) - a set of requirements for a device to recieve LineageOS officially.
-[Code of Conduct](code-of-conduct.md) - a set of guidelines for how contributors are expected to treat each other.
+[Device Support Requirements](device-support-requirements.md) - a set of requirements for a device to recieve LineageOS officially.  
+[Code of Conduct](code-of-conduct.md) - a set of guidelines for how contributors are expected to treat each other.  
+[Directors Working Agreement](directors-working-agreement.md) - guidelines for LineageOS Project Directors.  
diff --git a/directors-working-agreement.md b/directors-working-agreement.md
new file mode 100644
index 0000000..4b31cdb
--- /dev/null
+++ b/directors-working-agreement.md
@@ -0,0 +1,29 @@
+# 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: 
+    * Slack #_announcements as “Announcement: [here]” so as to copy to JIRA ANNOUNCE 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.