Community
CloudWeGo is an open source project that anyone in the community can use, improve, and enjoy. We'd love for you to join us! Here's how to get involved.
Develop and Contribute
First off, thank you for your interest in CloudWeGo. We are a very open and active community, where dedicated contributors of all levels are welcome to join to share their passion for open source, learn and upskill themselves. You may participate in the community through GitHub, or simply by interacting with other members in CloudWeGo Slack channel:
If you want to become a Contributor, please read the Contribution Guidelines and the Community Membership Privileges and Guidelines.
Where to Start?
If you’re looking for a place to start for your first contribution, here’s a few things to note. The CloudWeGo project is subdivided into subprojects:
- Kitex (Kitex & Kitex ecosystem & kitex-contrib)
- Hertz (Hertz & Hertz ecosystem & hertz-contrib)
- Volo (Volo & Volo ecosystem & volo-rs & Motore & Pilota)
- Netpoll (Netpoll & Netpoll ecosystem)
- Monoio (Monoio & Monoio ecosystem)
- Serdes (Thriftgo & Frugal & Fastpb & Sonic & thrift-gen-validator)
- Shmipc (shmipc-spec & shmipc-go)
- Website & Docs (cloudwego.github.io)
The community is structured with various roles to streamline day to day operations, and to recognize the efforts of longstanding contributors. Responsibilities for the various community roles fall under these subprojects (repos) as defined by the CloudWeGo team.
| Role | Responsibilities | Requirements | Defined by |
|---|---|---|---|
| Member | Active contributor in the community. | Sponsorship by two approvers or maintainers, and multiple code contributions to the project. | GitHub org member. |
| Committer | Active code contributions and/or issue replies in the subproject. | Sponsorship by two approvers or maintainers and multiple code contributions to the project. | GitHub subproject committer team. |
| Reviewer | Review contributions from other members, and give feedback and guidance. | Continuous history of review and authorship in a subproject. | GitHub subproject reviewer team. |
| Approver | Approve contributions received by the project. | Highly experienced, active reviewer and contributor to a subproject. | GitHub subproject approver team. |
| Maintainer | Set the direction and priorities for a subproject. | Demonstrated sense of responsibility and excellent technical judgement for the subproject. | GitHub subproject maintainer team. |