Welcome to the CloudWeGo community. This is the starting point for becoming a contributor, improving the code and docs, giving presentations and all the goodness of helping out on the project. We are a friendly, collaborative group and look forward to working together.
Other Documents
- How to Contribute - guidelines and advice on becoming a contributor
- Community membership - describes the various responsibilities of contributor roles in the CloudWeGo community
CloudWeGo is Golang-centric middleware that can be used to quickly build enterprise-class cloud native architectures. It contains many components, including the RPC framework Kitex, the basic network library Netpoll, thrfitgo, and netpoll-http2. By combining the community's excellent open source products, developers can quickly build a complete set of micro-service systems.
Visit cloudwego.io for more information about CloudWeGo
CloudWeGo is an open source project with an active development community. The project was started at ByteDance.
We want your contributions, ideas and suggestions! One of the easiest ways to get involved is to participate in discussions and chat on IM (including Wechat, Lark & Slack).
Reach out with any questions you may have and we'll make sure to answer them as soon as possible and as a community member feel free to jump in and answer questions.
Currently, our community meeting is availiable for contributors only. You may contact any maintainer to join the meeting if you are already a contributor.
Previous community meeting notes can be find here for your interest and reference.
The CloudWeGo blog has regular posts on releases and technical articles. If you would like to author a post, reach out to us with a suggestion or directly raise a PR here.
One of the easiest ways to contribute is to participate in discussions at community engagements.
If you're looking for something to work on, read the contribution guidelines and then you start by looking for GitHub issues, marked with "Good First Issue" or the "Help Wanted" labels:
And, we can always use more testing, have more and improved docs, or just write a blog post on what you have discovered while using CloudWeGo.
This project has adopted the Contributor Covenant Code of Conduct