Chore: add governance file and refer to the community repo (#3814)

* Chore: update docs

Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>

* Chore: add governance file and refer to the community repo

Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>

GOVERNANCE.md

@@ -0,0 +1,16 @@
+# Governance
+
+[Project maintainers](https://github.com/kubevela/community/blob/main/OWNERS.md#maintainers) are responsible for activities around maintaining and updating KubeVela.
+Final decisions on the project reside with the project maintainers.
+
+Maintainers **MUST** remain active. If they are unresponsive for >6 months,
+they will be automatically removed unless a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) of the other project maintainers agrees to extend the period to be greater than 6 months.
+
+New maintainers can be added to the project by a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) vote of the existing maintainers.
+A potential maintainer may be nominated by an existing maintainer.
+A vote is conducted in private between the current maintainers over the course of a one week voting period.
+At the end of the week, votes are counted and a pull request is made on the repo adding the new maintainer to the [CODEOWNERS](https://github.com/kubevela/kubevela/blob/master/.github/CODEOWNERS) file.
+
+A maintainer may step down by submitting an [issue](https://github.com/kubevela/kubevela/issues/new/choose) stating their intent.
+
+Changes to this governance document require a pull request with approval from a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) of the current maintainers.

OWNERS

@@ -1,12 +0,0 @@
-approvers:
-- kubevela-controller
-- kubevela-devex
-- kubevela-dashboard-approver
-
-reviewers:
-- kubevela-controller
-- oam-spec
-- kubevela-dashboard-reviewer
-
-members:
-- community-collaborators

OWNERS_ALIASES

@@ -1,61 +1 @@
-Reviewers:
-- Ghostbaby
-- StevenLeiZhang
-- chwetion
-- yue9944882
-- zxbyoyoyo
-- reetasingh
-- wangwang
-- evanli18
-- devholic
-- fourierr
-- JooKS-me
-- s4rd1nh4
-
-Approvers:
-- Somefive (Multi-Cluster)
-- chivalryq (Vela CLI)
-- sunny0826 (kubevela.io)
-- hanxie-crypto (VelaUX)
-- FogDong (Workflow)
-- wangyikewxgm (Addon)
-- yangsoon (VelaQL）
-
-Maintainers:
-- wonderflow
-- hongchaodeng
-- captainroy-hy
-- resouer
-- barnettZQG
-- leejanee
-- zzxwill
-- BinaryHB0916
-- dhiguero
-
-Emeritus Members:
-- ryanzhang-oss
-- Fei-Guo
-- szihai
-- xiaoyuaiheshui
-- wenxinnnnn
-- silenceper
-- erdun
-- mosesyou
-- artursouza
-- woshilanren11
-
-bootstrap-contributors:     # thank you for bootstrapping KubeVela at the very early stage!
-- xiaoyuaiheshui
-- Ghostbaby
-- wenxinnnnn
-- silenceper
-- erdun
-- sunny0826
-- mosesyou
-- artursouza
-- wonderflow
-- hongchaodeng
-- ryanzhang-oss
-- woshilanren11
-- hanxie-crypto
-- zzxwill
+The owner file has been migrated to the community repo, please refer to https://github.com/kubevela/community/blob/main/OWNERS.md

README.md

@@ -49,13 +49,25 @@ Official blog is available on [KubeVela blog](https://kubevela.io/blog).
 
 ## Community
 
+We want your contributions and suggestions! 
+One of the easiest ways to contribute is to participate in discussions on the Github Issues/Discussion, chat on IM or the bi-weekly community calls.
+For more information on the community engagement, developer and contributing guidelines and more, head over to the [KubeVela community repo](https://github.com/kubevela/community).
+
+### Contact Us
+
+Reach out with any questions you may have and we'll make sure to answer them as soon as possible!
+
 - Slack:  [CNCF Slack kubevela channel](https://cloud-native.slack.com/archives/C01BLQ3HTJA) (*English*)
-- Gitter: [oam-dev](https://gitter.im/oam-dev/community) (*English*)
 - [DingTalk Group](https://page.dingtalk.com/wow/dingtalk/act/en-home): `23310022` (*Chinese*)
 - Wechat Group (*Chinese*): Broker wechat to add you into the user group.
  
   <img src="https://static.kubevela.net/images/barnett-wechat.jpg" width="200" />
-- Bi-weekly Community Call: 
+
+### Community Call
+
+Every two weeks we host a community call to showcase new features, review upcoming milestones, and engage in a Q&A. All are welcome!
+
+- Bi-weekly Community Call:
   - [Meeting Notes](https://docs.google.com/document/d/1nqdFEyULekyksFHtFvgvFAYE-0AMHKoS3RMnaKsarjs).
   - [Video Records](https://kubevela.io/videos/meetings/en/meetings).
 - Bi-weekly Chinese Community Call:
@@ -72,6 +84,7 @@ Official blog is available on [KubeVela blog](https://kubevela.io/blog).
 For more talks, please checkout [KubeVela Talks](https://kubevela.io/videos/talks/en/standardizing-app).
 
 ## Contributing
+
 Check out [CONTRIBUTING](./CONTRIBUTING.md) to see how to develop with KubeVela.
 
 ## Report Vulnerability
@@ -79,4 +92,5 @@ Check out [CONTRIBUTING](./CONTRIBUTING.md) to see how to develop with KubeVela.
 Security is a first priority thing for us at KubeVela. If you come across a related issue, please send email to security@mail.kubevela.io .
 
 ## Code of Conduct
+
 KubeVela adopts [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).

community.md

@@ -1,7 +1,3 @@
 # Community
 
-All contributors should be welcomed to the community by existing members, helped with PR workflow, and directed to relevant documentation and communication channels.
-
-Please check [community-membership.md](https://github.com/oam-dev/community/blob/main/community-membership.md) to start engaging with the community.
-
-Enjoy coding and collaboration in OSS world!
+Please refer to the [community repo](https://github.com/kubevela/community) for details.