All forms of contributions are accepted, for example:
1. Take a look at issues with tag called Good first issue or Help wanted.
2. Join the discussion on mailing list.
3. Answer questions on issues.
4. Fix bugs reported on issues, and send us pull request.
5. Review the existing pull request.
6. Improve the website.
7. Write document or article.
8. Any form of contribution that is not mentioned above.
If you would like to contribute, please send an email to email@example.com to let us know!
Anyone can be a contributor to an Apache project. Being a contributor simply means that you take an interest in the project and contribute in some way, ranging from asking sensible questions (which documents the project and provides feedback to developers) through to providing new features as patches.
If you become a valuable contributor to the project you may well be invited to become a committer. Committer is a term used at the ASF to signify someone who is committed to a particular project. It brings with it the privilege of write access to the project repository and resources.
More details could be found here.
The Apache APISIX community follows the Apache Community’s process on accepting a new committer. After a contributor participates APISIX's community actively, (P)PMC and Committers will make decisions to invite the contributor join Committers and (P)PMC.
1. Start the discussion and vote in @private. Only current PMC member could nominate
2. If the vote passes, send an offer to become a committer with @private CC’ed
3. New committer signs ICLA and apply Apache ID and email address
4. Update Team page.
1. Develop new features
2. Refactor codes
3. Review PR reliably and in time
4. Consider and accept feature requests
5. Answer questions
6. Update documentation and examples
7. Improve processes and tools
8. Guide new contributors join community.
In APISIX community, if a committer who have earned even more merit, can be invited to be a part of the Podling Project Management Committee (PPMC).
One thing that is sometimes hard to understand when you are new to the open development process used at the ASF, is that we value the community more than the code. A strong and healthy community will be respectful and be a fun and rewarding place. More importantly, a diverse and healthy community can continue to support the code over the longer term, even as individual companies come and go from the field.