The CubeFS community adheres to the following principles:
- Open: CubeFS is open source.
- Welcoming and respectful: See Code of Conduct.
- Transparent and accessible: Changes to the CubeFS organization, CubeFS code repositories, and CNCF related activities (e.g. level, involvement, etc) are done in public.
- Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles.
The CubeFS project has a Steering Committee.
- The term of the Steering Committee position is one year, and individuals can serve multiple terms in this role.
- Steering Committee Member is responsible for the top-level design of projects, formulation of roadmaps, and community management
- The composition of the Steering Committee members consists of core maintainers from independent developers or vendors.
- To ensure fairness, efforts will be made to maintain a balanced representation among the personnel from different vendors.
- No single vendor can exceed 50% of the total number of personnel.
- The term of the Steering Committee is one year,adjust up to 50% for stability.
Every one carries water...
Making a community work requires input/effort from everyone. Maintainers should actively participate in Pull Request reviews. Maintainers are expected to respond to assigned Pull Requests in a reasonable time frame, either providing insights, or assign the Pull Requests to other maintainers. Every Maintainer is listed in the top-level MAINTAINERS file.
Committer is an active contributor in the community who continuously makes contributions to the community by contributing codes, documentation, participating in community discussions, or answering community questions, etc.
Typically, they need to have a good understanding of the project to help more community users quickly join the project. Committer will be responsible for reviewing relevant issues or PRs, and your opinions are also extremely important to the community.
Every Committer is listed in the top-level MAINTAINERS file.
If you are interested in becoming a committer, please email maintainers@cubefs.groups.io or opening a pull request,
and list your contributions.The steering committee will review the proposal by majority votes,
and you will receive an invitation letter from the community after the review is passed.
On the successful merge of a significant pull request or upon making significant contributions, any current maintainer can reach to the author behind the pull request and ask them if they are willing to become a CubeFS maintainer. Maintainers have the authority to nominate new maintainers by either sending an email to maintainers@cubefs.groups.io or opening a pull request. Typically, new maintainers are selected from among the committers.The steering committee will review the proposal by majority votes, and you will receive an invitation letter from the community after the review is passed.
If a Maintainer feels she/he can not fulfill the "Expectations from Maintainers", they are free to step down. The steering committee will adjust the list of maintainers based on the following factors
- The activity level and contribution level of the maintainer in the past six months.
- Balance of personnel across modules
- Module changes, such as additions or deprecations
- Balance of personnel among vendors.
In such a case:
A PR is required to move the person in question from the maintainer entry to the retirement entry of the respective OWNERS file. The person in question must be mentioned in the body of the PR. This acts as a final contact attempt so that they can provide their feedback.
Only for core maintainers who are losing their status: remove them from the core-maintainers team; go to https://maintainers.cncf.io/ and open a PR to remove them under CubeFS; remove them from the cubefs.groups.io/g/maintainers mailing list.
Changes in steering committee members are initiated by opening a github PR.
Anyone from CubeFS maintainers can vote on the PR with either +1 or -1.
Only the following votes are binding:
- Any maintainer that has been listed in the top-level MAINTAINERS file before the PR is opened.
- Any maintainer from an organization may cast the vote for that organization. However, no organization should have more binding votes than 1/2 of the total number of maintainers defined in 1).
The PR should only be opened no earlier than 4 weeks before the end of the term. The PR should be kept open for no less than 2 weeks. The PR can only be merged after the end of the last term, with more +1 than -1 in the binding votes.
When there are conflicting PRs about changes in Steering Committee, the PR with the most binding +1 votes is merged.
The Steering Committee member can volunteer to step down.
- Changes in project governance (GOVERNANCE.md) could be initiated by opening a github PR.
- The PR should only be opened no earlier than 4 weeks before the end of the Steering Committee's term.
- The PR should be kept open for no less than 1 weeks. The PR can only be merged follow the same
- Voting process as in
Changes in Steering Committee.
- Vendors share communication channels of the community, such as social media and messaging platforms.
- All vendors involved in the project are encouraged to actively participate in the topic selection process for public events.
- Vendors can apply to participate in open-source conferences and events. The invitation should be cc'ed to
maintainers@cubefs.groups.io. - The Steering Committee will review the application, and if it is approved, the Steering Committee can provide guidance on this matter.
Decisions are build on consensus between maintainers.
Proposals and ideas can either be submitted for agreement via a github issue or PR,
or by sending an email to maintainers@cubefs.groups.io.
In general, we prefer that technical issues and maintainer membership are amicably worked out between the persons involved. If a dispute cannot be decided independently, get a third-party maintainer (e.g. a mutual contact with some background on the issue, but not involved in the conflict) to intercede. If a dispute still cannot be decided, the Steering Committee can make the decision by majority votes.
Decision making process should be transparent to adhere to the principles of CubeFS project.
All proposals, ideas, and decisions by maintainers or the Steering Committee should either be part of a github issue or PR, or be sent to maintainers@cubefs.groups.io.
The cubefs GitHub project maintainers team reflects the list of Maintainers.
The CubeFS organization is open to receive new sub-projects under its umbrella. To accept a project into the CubeFS organization, it has to meet the following criteria:
- Must be licensed under the terms of the Apache License v2.0
- Must be related to one or more scopes of the CubeFS ecosystem:
- CubeFS project artifacts (website, deployments, CI, etc)
- External plugins
- Other storage related topics
- Must be supported by a Maintainer not associated or affiliated with the author(s) of the sub-projects
The submission process starts as a Pull Request or Issue on the cubefs/cubefs repository with the required information mentioned above. Once a project is accepted, it's considered a sub-project under the umbrella of CubeFS.
The CubeFS is open to receive new plugins as part of the CubeFS repo. The submission process is the same as a Pull Request submission. Unlike small Pull Requests though, a new plugin submission should only be approved by a maintainer not associated or affiliated with the author(s) of the plugin.
CubeFS might be involved in CNCF (or other CNCF projects) related
marketing, events, or activities. Any maintainer could help driving the CubeFS involvement, as long as
she/he sends email to maintainers@cubefs.groups.io (or create a GitHub Pull Request) to call for participation
from other maintainers. The Call for Participation should be kept open for no less than a week if time
permits, or a reasonable time frame to allow maintainers to have a chance to volunteer.
The CubeFS Code of Conduct is aligned with the CNCF Code of Conduct.
The liaison officer is responsible for daily communication with CNCF, including information updates, demand communication, community activity meetings, etc.
Sections of this documents have been borrowed from CoreDNS, Fluentd and Envoy projects.