Changes per discussion:

- added Values section
- added bootstrap section for new subprojects
- changed no contribution period

Signed-off-by: Josh Berkus <[email protected]>

CONTRIBUTOR_LADDER.md

@@ -143,8 +143,8 @@ Process of becoming a maintainer:
 It is important for contributors to be and stay active to set an example and show commitment to the project. Inactivity is harmful to the project as it may lead to unexpected delays, contributor attrition, and a loss of trust in the project.
 
 * Inactivity is measured by:
-    * Periods of no contributions for longer than 12 months
-    * Periods of no communication for longer than 6 months
+    * Periods of no contributions for longer than 18 months
+    * Unannounced periods of no communication for longer than 4 months
 * Consequences of being inactive include:
     * Involuntary removal or demotion
     * Being asked to move to Emeritus status

GOVERNANCE.md

@@ -7,7 +7,7 @@
   * [Steering Committee Elections](#steering-committee-elections)
 * [Code of Conduct Committee](@code-of-conduct-committee)
 * [Adding New Subprojects](#adding-new-Subprojects)
-* [Remocing Projects](#removing-projects)
+* [Removing Projects](#removing-projects)
 
 The Open Cluster Management umbrella project is composed as a federation of individual projects,
 some independent and some interdependent, each of which focuses on some aspect
@@ -17,14 +17,24 @@ of Kubernetes cluster and multicluster management.  Our governance reflects this
 
 Open Cluster Management and its leadership embrace the following values:
 
-* [TODO: List of Values]
+* Openness: Communication happens in the open and is archived for future reference. 
+  As much as possible, all discussions and work take place in public forums and 
+  open repositories.
+
+* Community over Product or Company: Sustaining and growing our community takes 
+  priority over shipping code or sponsors' organizational goals.  Each contributor
+  participates in the project as an individual.
+
+* Inclusivity: We innovate through different perspectives and skill sets, which 
+  can only be heard in a welcoming and respectful environment.
+
+* Participation: Responsibilities within the project are earned through 
+  participation, and there is a clear path up the ladder into leadership positions.
+
+* Modularity: OCM's community, like its technology, operates on a modular basis, 
+  where projects and components are developed independantly and coordinate where 
+  necessary or beneficial.
 
-<!-- 
-This is where you put the core values or principles of your project, like
-openness, distributed design, fairness, diversity, etc.
-See https://contribute.cncf.io/maintainers/governance/charter for guidance 
-and examples.
--->
 
 ## Individual Subproject Governance
 
@@ -56,7 +66,7 @@ majority vote of the Steering Committee.
 The overall Open Cluster Management umbrella project is governed by a Steering
 Committee, which is selected as follows:
 
-* Two Maintainer representatives from each member Subproject
+* One Maintainer representatives from each member Subproject
 * Two general "Community Representatives"
 
 ### Steering Committee Duties
@@ -111,7 +121,8 @@ community meeting.
 ## Code of Conduct Committee
 
 In order to review and enforce the Code of Conduct, the Steering Committee selects
-3 people to be on the Code of Conduct Committee.  
+3 people to be on the Code of Conduct Committee.
+
 These individuals will be chosen based on their community management and code of conduct
 experience, with diverse representation across the committee, including employer, gender,
 race, background, and region of the world.  To avoid fatigue, the Steering Committee will
@@ -154,11 +165,19 @@ Members of Open Cluster Management, but the Subproject is not entitled to a repr
 Steering Committee.  Steering will review Experimental Subprojects at least twice
 per year to determine if they have matured to full Subproject status.
 
+New Subprojects will be initialized with a set of maintainers, reviewers, 
+contributors, and other roles assigned based on the people doing the work before
+the Subproject was accepted. The appropriate contributors will be added as 
+Organization Members without the regular process.
+
 ## Removing Projects
 
 In some cases, projects will become inactive or unmaintainable, or wish to separate
 from Open Cluster Management. Any Steering Committee member may propose removal of a project on
-these grounds, and Steering can confirm this with a majority vote.
+these grounds, and Steering can confirm this with a majority vote. The CNCF will
+determine which, if any, assets of those subprojects will be removable should a
+project leave OCM.
 
-Projects which still have contributors will then be moved to a repository in their
-own namespace.  Projects which have ceased all activity are moved to an archive namespace.
+Where possible, Projects which still have contributors will then be moved to a 
+repository in their own namespace.  Projects which have ceased all activity are 
+moved to an archive namespace.