同步操作将从 百度开源/BFE 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
The BFE community adheres to the following principles:
The BFE project has a project lead.
A project lead in BFE is a single person that has a final say in any decision concerning the BFE project.
The term of the project lead is one year, with no term limit restriction.
The project lead is elected by BFE maintainers according to an individual's technical merit to BFE project.
The current project lead is identified in the MAINTAINERS file`.
Classify GitHub issues and perform pull request reviews for other maintainers and the community.
During GitHub issue classification, apply all applicable labels to each new issue. Labels are extremely useful for follow-up of future issues. Which labels to apply is somewhat subjective so just use your best judgment.
Make sure that ongoing PRs are moving forward at the right pace or closing them if they are not moving in a productive direction.
Participate when called upon in the security release process. Note that although this should be a rare occurrence, if a serious vulnerability is found, the process may take up to several full days of work to implement.
In general continue to be willing to spend at least 20% of your time working on BFE (1 day per week).
If a maintainer is no longer interested or cannot perform the maintainer duties listed above, they should volunteer to be moved to emeritus status.
In extreme cases this can also occur by a vote of the maintainers per the voting process. The voting process is a simple majority in which each senior maintainer receives two votes and each normal maintainer receives one vote.
Changes in project lead is initiated by opening a github PR.
Anyone from BFE community can vote on the PR with either +1 or -1.
Only the following votes are binding:
The PR should only be opened no earlier than 6 weeks before the end of the project lead's term. The PR should be kept open for no less than 4 weeks. The PR can only be merged after the end of the last project lead's term, with more +1 than -1 in the binding votes.
When there are conflicting PRs about changes in project lead, the PR with the most binding +1 votes is merged.
The project lead can volunteer to step down.
All substantive updates in Governance require a supermajority maintainers vote.
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 cncf-bfe-maintainers@lists.cncf.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 project lead has the final say to decide an issue.
Decision making process should be transparent to adhere to the principles of BFE project.
All proposals, ideas, and decisions by maintainers or the project lead
should either be part of a github issue or PR, or be sent to cncf-bfe-maintainers@lists.cncf.io
.
The BFE Code of Conduct is aligned with the CNCF Code of Conduct.
Sections of this documents have been borrowed from Fluentd and CoreDNS projects.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。