Update governance and link to the new community project (openkruise#670)

Signed-off-by: FillZpp <[email protected]>

Author: FillZpp

ADOPTERS.md

@@ -1,132 +1,3 @@
+# Code of Conduct
 
-# Contributor Covenant Code of Conduct
-
-This document defines the code of conduct that applies to the entire Openkruise project hosted and managed by the [Openkruise organization](https://github.com/openkruise).
-
-## Our Pledge
-
-We as members, contributors, and maintainers pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, social-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Personal attacks
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Project maintainers are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Project maintainers have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the project maintainers responsible for enforcement at
-[email protected].
-All complaints will be reviewed and investigated promptly and fairly.
-
-All project maintainers are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Project maintainers will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from project maintainers, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).
-Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
+OpenKruise follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).

CODE_OF_CONDUCT.md

@@ -1,47 +1,22 @@
 # Governance
 
-This document defines governance policies for the entire Openkruise project hosted and managed by the [Openkruise organization](https://github.com/openkruise).
+The governance model adopted in OpenKruise is influenced by many CNCF projects.
 
 ## Principles
 
 - **Open**: Openkruise is an open source community.
-- **Welcoming and respectful**: See [Code of Conduct](CODE_OF_CONDUCT.md).
+- **Welcoming and respectful**: See [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
 - **Transparent and accessible**: Work and collaboration should be done in public.
 - **Merit**: Ideas and contributions are accepted according to their technical merit
   and alignment with project objectives, scope and design principles.
 
-## Project Maintainers
-
-Maintainers are the first and foremost contributors that are committed to the success of Openkruise project.
-They normally take the following responsibilities:
-
-- Classify GitHub issues and perform pull request reviews for other maintainers and the community.
-- During GitHub issue classification, apply all applicable [labels](https://github.com/openkruise/kruise/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.
-
-## Process of becoming a maintainer
+## Code of Conduct
 
-- Talk to one of the existing project [maintainers](MAINTAINERS.md) that you are interested in becoming a
-  maintainer, and he will nominate you as a new maintainer. After nomination, you will need to
-  create a PR to update the list in [MAINTAINERS.md](MAINTAINERS.md).
-- We will expect you to start contributing increasingly complicated PRs, under the guidance
-  of the existing maintainers.
-- We may ask you to do some PRs from our backlog. As you gain experience with the code base and our standards,
-  we will ask you to do code reviews for incoming PRs.
-- Once the existing maintainers have made a consensus that the nominating maintainer has deep understanding
-  about the project and is able to independently take the maintainer responsibilities,
-  the PR will be approved and the new maintainer becomes active.
+The OpenKruise [Code of Conduct](CODE_OF_CONDUCT.md) is aligned with the CNCF Code of Conduct.
 
-## When does a maintainer lose maintainer status
+## Community Membership
 
-- 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 maintainer receives one vote.
+See [community membership](https://github.com/openkruise/community/blob/master/community-membership.md).
 
 ## Decision making process
 
@@ -53,10 +28,6 @@ If a dispute cannot be decided independently, get a third-party maintainer (e.g.
 on the issue, but not involved in the conflict) to intercede and the final decision will be made.
 Decision making process should be transparent to adhere to the principles of Openkruise project.
 
-## Code of Conduct
-
-The Openkruise [Code of Conduct](CODE_OF_CONDUCT.md) is aligned with the CNCF Code of Conduct.
-
 ## Credits
 
 Some contents in this documents have been borrowed from [BFE](https://github.com/bfenetworks/bfe/blob/develop/GOVERNANCE.md) and [CoreDNS](https://github.com/coredns/coredns/blob/master/GOVERNANCE.md) projects.

FAQ.md

@@ -2,10 +2,8 @@
 approvers:
   - Fei-Guo
   - FillZpp
-  - jian-he
+  - furykerry
 reviewers:
   - Fei-Guo
   - FillZpp
-  - jian-he
-  - jetmuffin
-  - evertrain
+  - furykerry

GOVERNANCE.md

@@ -0,0 +1,4 @@
+approvers:
+  - zmberg
+reviewers:
+  - zmberg

MAINTAINERS.md

@@ -0,0 +1,4 @@
+approvers:
+  - zmberg
+reviewers:
+  - zmberg

OWNERS

@@ -0,0 +1,3 @@
+reviewers:
+  - hellolijj
+  - shiyan2016

pkg/control/pubcontrol/OWNERS

@@ -0,0 +1,3 @@
+reviewers:
+  - jetmuffin
+  - evertrain