Proposed governance and maintenance policy

new/governance_policy.md

@@ -0,0 +1,159 @@
+---
+RFC: unassigned
+Author: Adam Jacob <adam@getchef.com>
+Status: Draft
+Type: Process
+---
+
+# Chef Board of Governance
+
+Chef was designed from the outset to have a very open structure, including open design, open contribution, and consistent use of tools across the project. Given the large numbers of contributors, users, and companies with a stake in the future of the project, Chef leadership is looking to establish an advisory board, as part of its long term commitment to open governance.
+
+The purpose of this RFC is to create that governance board and define how it will work.
+
+## Definitions
+
+Before talking about certain roles and ideals, we want to make sure we’re clear about what we mean:
+
+<dl>
+<dt>CBGB</dt><dd>Means the Chef Board for Governance – the group of up to 12 representatives who will advise on the roadmap and core criteria of the Project.</dd>
+
+<dt>Company Leadership</dt><dd>Means the CEO of Chef Software Inc.</dd>
+
+<dt>Corporate Contributor</dt><dd>Means a company that (a) is one of the top eight companies in terms of non-trivial pull requests in the past six months as measured by contributions by all employees; (b) a company that has employees as Maintainers who make significant contributions to the Project; and (c) has committed to integrate Chef software into its products.</dd>
+
+<dt>Leadership</dt><dd>Means the CBGB, Company Leadership, and Project Maintainers.</dd>
+
+<dt>Lieutenant</dt><dd>Means someone who (a) is willing to perform the duties of a Lieutenant; (b) receives an absolute majority of affirmative votes of existing Lieutenants; and (c) is approved as a Lieutenant by the Project Lead.</dd>
+
+<dt>Project</dt><dd>Means the Chef open source software and all applicable policies and procedures and guidelines.</dd>
+
+<dt>Project Lead</dt><dd>means a leader in the Chef Community.  The initial Project Lead will be Adam Jacob.</dd>
+
+<dt>Project Maintainers</dt><dd>means the current list of maintainers, lieutenants, and project lead as defined in the Maintenance Policy.</dd>
+
+<dt>Scope</dt><dd>Means the issues under the CBGB purview such as:  (a) advising on the long term roadmap; (b) project policies and procedures around maintenance and contributions; and (c) long term governance model.  All initiatives within the Chef Project are required to reside within the Scope.</dd>
+
+<dt>User/Contributor</dt><dd> Means (a) an organization that uses Chef and that has published at least one use case; and/or (b) an individual contributor to the Project who is not a Company employee or Corporate Contributor.</dd>
+</dl>
+
+## Purpose
+
+The primary purpose of the CBGB is to advise the Leadership on matters related to supporting the long-term governance, structure, and roadmap of the Project.
+
+## What’s Included
+
+The following main areas are included in this proposal:
+
+* Provide a forum for individuals, users, and companies to discuss the issues within the CBGB Scope.
+
+* Provide guidance and input to Leadership, and where possible, present a consistent and consolidated opinion from the broader Chef community.
+
+* Produce a formal, twice yearly report to the Leadership and broader Chef community of the status of and progress made in all areas under the purview of the CBGB.
+
+* Promote and support the use of Chef in a manner consistent with the Scope.
+
+## What’s NOT Included
+
+The CBGB is not:
+
+* Intended to serve as a decision-making governance board. The CBGB advises, but does not manage, the Leadership.
+
+* Intended to replace existing mechanisms for community input, governance, or contribution.
+
+* Intended to assume a formal, fiduciary role with respect to the Project. The CBGB membership will not be asked to provide funds to the Project, assume liabilities with respect to the Project or their activities, or assume responsibility for enforcing either trademarks or CBGB recommendations.
+
+## Scope
+
+The CBGB is expected to provide input and formal recommendations regarding the project Scope.  It can modify its Scope by a majority vote of its members.
+
+### Membership and Voting:
+
+The CBGB will have up to 12 members.
+
+Composition of CBGB:
+
+* (1) Project Lead:  Adam Jacob
+
+* (4) Users/Contributors
+
+* (4) Corporate Contributors:
+
+* (3) Lieutenants:
+
+#### Membership Term
+
+Except for the Project Lead, who will serve an indefinite term unless replaced as provided herein, each member of the CBGB will serve a term of 12 months and no member will serve more than two consecutive terms.
+
+#### Voting and Selection Process
+
+The selection process is intended to be open, transparent, and guided by objective criteria for membership.
+
+* The CBGB shall elect a Chair and Vice Chair from amongst their members to serve a renewable 6 month term.
+
+* The Chair or Vice-Chair shall prepare an agenda for and preside over regular meetings of the CBGB. These meetings shall occur as frequently as the CBGB determines is in the project’s best interest, but no less than quarterly
+
+* The Project Lead will appoint a temporary chair to set the agenda for the first meeting and preside until the election shall occur.
+
+* The CBGB may fill any vacancy arising by removal or resignation by a simple majority vote to fill the remainder of the term of the vacating member.
+
+* The rules of election and membership outlined in this section may be varied by a resolution of the CBGB supported by more than two thirds of its voting membership.
+
+* All Project contributors are welcome as participants and observers at CBGB meetings
+
+#### Selection and Succession
+
+##### Selection
+
+* Project Lead:  Initial Project Lead will be Adam Jacob.  Any new Project Lead candidate will be selected by a majority vote of the Lieutenants, and approved by Company Leadership. This selection will happen according to the Maintenance Policy.
+
+* All Other Seats:  Candidates who meet the criteria for each group identified above will be elected by at least a majority vote of all qualified voters: +1
+
+##### Succession
+
+(i)	Project Lead:  If a new Project Lead is nominated and receives majority vote of the Lieutenants, and not vetoed by Company Leadership.
+
+(ii)	All Other Seats:  All other members of the CBGB will be replaced upon any of the following:  (1) End of term; or (2) majority vote of all other members of the CBGB. 
+
+## Operation
+
+The CBGB is authorized to seek advice and counsel from other interested parties and invited experts as appropriate
+
+Any outside party wishing to bring an issue before the CBGB may do so by emailing the CBGB mailing list
+
+The CBGB shall provide transparent and timely reporting (through any mechanism it deems appropriate) to the Community at large on all of its activities, subject to the right of any individual to designate their comments and the ensuing discussion as "in confidence," in which case the public report shall contain only a note of the request and an agreed summary (if any) of the substance.
+
+The CBGB is being formed at the discretion of the Company Leadership. The Company Leadership alone may decide to terminate the CBGB in its sole discretion; provided however, that the Company Leadership shall first consult the CBGB Chair.
+
+The CBGB and its members shall abide by appropriate antitrust guidelines.
+
+### Open Governance Principles
+
+The CBGB will formulate recommendations in conjunction with the following, open governance principles:
+
+#### Open participation
+
+Throughout the project:  anyone should be able to participate and contribute. All bugs and tasks will be tracked in a public tracker and all of the source code and all of the tools needed to build it will be available under an open license permitting unrestricted use
+
+Open technical value: technical value over pride of authorship. Code is contributed for the express purpose of advancing technologies relevant to the project, effectively separating technology advancement from individual or commercial intent.
+
+Open design: Roadmaps are discussed in the open, and design receives input from all contributors and maintainers
+
+Influence through contribution: organizations and individuals gain influence over the project through contribution.
+
+IP Cleanliness: Steps are taken to ensure that all incoming code is legally contributed (CLAs, terms-of-use, etc.), that use of approved third party libraries does not create incompatible dependencies
+
+Open Licensing: code should be licensed using approved, standard, open-source licenses. (Chef is currently licensed under Apache 2.0).
+
+## Grievance Handling
+
+When a member has a concern about the Chef Project, the member may raise that concern with the CBGB.  If the member is not satisfied with the result, the member can raise the concern directly with the Project Lead.   All appeals and discussions will be open, transparent and public.
+
+Please help us improve this draft by sending your comments and feedback to governance@getchef.com.
+
+## Copyright
+
+This work is in the public domain. In jurisdictions that do not allow for this,
+this work is available under CC0. To the extent possible under law, the person
+who associated CC0 with this work has waived all copyright and related or
+neighboring rights to this work.

new/maintenance_policy.md

@@ -0,0 +1,212 @@
+---
+RFC: unassigned
+Author: Adam Jacob <adam@getchef.com>
+Status: Draft
+Type: Process
+---
+
+# Maintenance Policy
+
+The Maintenance Policy defines how we make decisions about what happens with Chef, and associated software projects. It provides the process by which:
+
+* Roadmaps are decided
+* Patches are merged
+* Disputes are resolved
+
+It is intended to be short, flexible, and clear.
+
+This file is related to the MAINTAINERS file in Chef. During the draft period, the first version of that file is included in this RFC.
+
+# How the project is maintained
+
+This file is the canonical source for how the Chef project is maintained.
+
+# Roles
+
+## Project Lead
+
+Resolves disputes
+Provides vision and roadmap
+Has universal veto power
+
+## Lieutenants
+
+Publish a roadmap (two quarters out)
+Release calendar for code outside of chef client/chef server
+Resolves disputes within their subsystem
+Has localized veto power
+Plus all responsibilities of a maintainer
+
+## Maintainer 
+
+Handle contributions on GitHub - first response to a PR within 48 hours
+Be available on IRC
+Attend the developers meeting (do not miss more than 3 in a row - special dispensation can be made for difficult time zones)
+Be available to answer mailing list questions within 48 hours
+Weekends and local holidays in the maintainer’s jurisdiction are not counted for timeliness requirements. Absences for reasonable causes such as vacations, illness, etc. are also acceptable; Maintainers should notice of absences via the development mailing list whenever possible.
+Committed to 100% tests passing for your component
+Has full commit/merge access to the relevant repositories
+Has ops on IRC
+
+# How a patch gets merged
+
+* Open Pull Request (anyone)
+* Sign a CLA on Supermarket, tied to your github account.
+* Code reviewed by a maintainer, lieutenant, or project lead. Approval is indicated by :+1: on the pull request.
+* Merged on :+1: by an absolute majority of maintainers for the subsystems affected by your patch with no vetoes
+
+# How to become a...
+
+## Maintainer
+
+* Have patches merged into the relevant subsystem
+* Be willing to perform the duties of a maintainer
+* Issue a pull request adding yourself to the MAINTAINERS file for your component
+* Receive an absolute majority of existing maintainers and lieutenants for your component :+1:
+* No veto from the component lieutenant
+* No veto from the current project lead
+
+## Lieutenant
+
+* Issue a pull request to the MAINTAINERS file making yourself the lieutenant
+* Be willing to perform the duties of a lieutenant
+* Receive an absolute majority of existing lieutenants :+1:
+* No veto from the current project lead
+
+## Project Lead
+
+* Issue a pull request to the MAINTAINERS file making yourself the project lead
+* Be willing to perform the duties of the project lead
+* Receive an absolute majority of existing lieutenants :+1:
+* No veto from Chef Software, Inc, as held by their current Chief Executive Officer.
+
+# Removing a Maintainer, Lieutenant or Lead
+
+If a Maintainer, Lieutenant or Lead consistently fails to maintain their responsibilities or becomes disruptive, they can be removed by:
+
+* Issue a pull request removing them from the MAINTAINERS file
+* Receive an absolute majority of existing lieutentants :+1:
+* No veto from the current project lead
+
+OR
+
+* Issue a pull request removing them from the MAINTAINERS file
+* The current project lead unilaterally decides to merge pull request
+
+# How to add a component
+
+* Issue a pull request to the MAINTAINERS file describing the component, and making yourself lieutenant
+* Be willing to perform the duties of a lieutenant
+* Receive an absolute majority of existing lieutenants :+1:
+* No veto from the current project lead
+
+# How to change the rules by which the project is maintained
+
+* Issue a pull request to this file.
+* Receive an absolute majority of existing lieutenants from the Chef repository MAINTAINERS file :+1:
+* No veto from the current project lead
+
+# Where can I find the community?
+
+The broader Chef community gathers in a small number of designated places. Participants in these places should be considered as operating on their own opinion, and representing nothing further than their own point of view. While some members of the community may be participating via their employment at Chef Software, when in these spaces, their authority and voice is equal to any other participant based on the guidelines in this file.
+
+## IRC
+
+You can find a large set of community members in IRC, within the #chef channel on irc.freenode.net. Development updates and conversations also happen on #chef-hacking. In both channels, those with “ops” are the maintainers, lieutenants, and the project lead. Those with “voice” are MVPs for Chef releases.
+
+## Mailing Lists
+
+* [Chef Users](http://lists.opscode.com/sympa/info/chef) - is the primary async communications channel for all users of Chef, regardless of how they participate.
+* [Chef Developers](http://lists.opscode.com/sympa/info/chef-dev) - is the primary async communications channel for those concerned with developing Chef.
+
+# Where can I find Chef Software Inc?
+
+[The history of the Chef Project](http://www.getchef.com/blog/2014/07/03/chef-as-a-community/) is linked to the existence of a for-profit company, [Chef Software](http://www.getchef.com). Many employees of the company are active members of the community. When they participate in the community, they do so as individuals subject to the guidelines in this file. 
+
+If you would like to speak to, or understand the position of, someone at Chef Software - feel free to drop a line to [info@getchef.com](mailto:info@getchef.com) - and we’ll get back to you. Or simply ask for the companies official perspective in any of the community spaces, and a representative will get back to you in that space.
+
+# The MAINTAINERS file in Chef
+
+# Maintainers
+
+This file lists how the Chef project is maintained. When making changes to the system, this
+file tells you who needs to review your patch - you need a simple majority of maintainers
+for the relevant subsystems to provide a :+1: on your pull request. Additionally, you need
+to not receive a veto from a Lieutenant or the Project Lead.
+
+[Check out HOW_CHEF_IS_MAINTAINED](link to come) for details on the process, how to become
+a maintainer, lieutenant, or the project lead.
+
+# Project Lead
+
+[Adam Jacob](http://github.com/adamhjk)
+
+# Components
+
+## Chef Core
+
+Handles the core parts of the Chef DSL, base resource and provider
+infrastructure, and the Chef applications. Includes anything not covered by
+another component.
+
+### Lieutenant
+
+### Maintainers
+
+## Dev Tools
+
+Chef Zero, Knife, Chef Apply and Chef Shell.
+
+### Lieutenant
+
+### Maintainers
+
+## Test Tools
+
+ChefSpec, Berkshelf (the chef bits), Test Kitchen (the Chef bits)
+
+### Lieutenant
+
+### Maintainers
+
+## Platform Specific Components
+
+The specific components of Chef related to a given platform - including (but not limited to) resources, providers, and the core DSL.
+
+## Enterprise Linux
+
+### Lieutenant
+
+### Maintainers
+
+## Ubuntu
+
+### Lieutenant
+
+### Maintainers
+
+## Windows
+
+### Lieutenant
+
+### Maintainers
+
+## Solaris
+
+### Lieutenant
+
+### Maintainers
+
+## AIX
+
+### Lieutenant
+
+### Maintainers
+
+## Mac OS X
+
+### Lieutenant
+
+### Maintainers
+
+