How Projects Join the Helm Organization
| HIP | Title | Author(s) | Created | Type | Status |
|---|---|---|---|---|---|
| 0003 | How Projects Join the Helm Organization | Matt Butcher matt.butcher@microsoft.com | 2020-09-30 | process | accepted |
Abstract
Helm is an organization with multiple projects. This document describes how new projects may be added to the Helm organization.
Motivation
Formalizing this process removes unspoken assumptions and makes it clear how to add a project to the Helm organization.
Rationale
Clarifying the process and the requirements will make it simpler, more consistent, and more transparent for projects to join the Helm organization.
Legal Requirements
Any project added must meet the CNCF's legal requirements, including licenses (Apache 2) and [CNCF intellectual property commitments][CNCF intellectual property commitments]. CNCF allows projects to choose [DCO or CLA][DCO or CLA].
Governance Requirements
Any project added must (a) agree to be held accountable to Helm governance at the organizational level, and (b) have in place a formal project governance structure that meets the requirements set out by the Helm organization in the [Helm governance documents][Helm governance documents].
Additionally, governance requirements from CNCF must be adhered to. For example, any candidate project must use the [CNCF Code of Conduct][CNCF Code of Conduct].
We currently do not allow any projects to "bring their own" code of conduct or to make any additional changes to the existing CNCF code of conduct.
Security Requirements
Any project added must have security guidelines for how to report and resolve security issues. It is acceptable to merely use the existing [Helm security process][Helm security process] for this. But projects that require special or additional reporting may do so.
Specification
This is the process to submit a project for addition to the Helm organization.
1. Project opens issue
The candidate project must open an issue in the [Helm community repository][Helm community repository] requesting that it join.
This issue should provide:
- A link back to the project
- The GitHub user names of those in a governance role for that project
- A short description (1-3 paragraphs) of why it makes sense to add to Helm
- A short explanation of how the project is to be staffed going forward.
2. Helm Org Review
The Helm organization owners will review the proposal. This process will likely involve some back-and-forth conversation with the owners of the project.
3. Helm Org Voting
As stated in the [Helm governance documents][Helm governance documents], a candidate project must pass a supermajority vote before it is accepted into the Helm organization.
If the Helm org maintainers vote to include the project, the project will be considered a recommended Helm project, and CNCF will be notified of our intentions.
4. CNCF Review
CNCF will apply its reviews, including but not limited to intellectual property reviews. This process will be managed between designated Helm org maintainers and the CNCF, with the project being included as necessary.
If this review fails, projects will be given the opportunity to comply with CNCF's requirements. Failure to comply, though, will remove the project from recommended project status, and the process will discontinue.
5. Transition of Resources
Once both Helm and CNCF have reviewed the project and approved, the project becomes a transitional project. Helm org maintainers will work with the transitional project to move resources, transfer requisite ownership, and make any other necessary changes. Helm org maintainers may choose to grant an incoming project a single position as a Helm org maintainer.
6. Completion
At the completion of the transitional process, the project will be an official Helm project. At the next governance cycle, it will be granted representation as per the [Helm governance documents][Helm governance documents].
Backwards compatibility
This change applies to all future project additions and implies no change to the status of existing projects.
Security implications
Not applicable.
How to teach this
The steps in the Specification will be available in [the Helm governance documents][Helm governance documents].
Reference implementation
Not applicable.
Rejected ideas
None currently.
Open issues
None currently.