We believe that our most valuable resource is the passionate community members who keep Zhip running. We are always looking for active, enthusiastic members of the Zhip community to become core contributors.
Contributors who have displayed lasting commitment to the evolution and maintenance of Zhip will be invited to become core contributors. For instance, contributors who:
- Love to help out other users with issues on GitHub
- Continue to make Zhip a stable product
- Review pull requests using the "Review Changes" feature in GitHub
- Merge pull requests we review, except for PRs where the author has push access. Merge PRs using the "Squash and Merge" feature in GitHub
- Respond to issues and help others
- Own regressions caused by our own contributions and PR approvals
- Maintain consistent coding standards
- Inform maintainers when critical fixes are merged so a release can be prepared
- Identify other Zhip community members who would be effective core contributors
- Make Zhip the best open source tool and community out there
- Ensure that new contributions live up to current coding standards.
- Adhere to the Zhip Code of Conduct
- Keep test coverage high and ensure up-to-date documentation
We work in a high-trust environment which implies that anyone and everyone is able to merge pull requests from the community. If the PR reviewer feels strongly about seeing a PR to completion, they should assign it to themselves and request necessary changes.
Most Importantly, our community prides itself in our supportive and friendly attitude. Above all else, we are always:
- Polite
- Friendly
- Having fun
- Encouraging the use of emojis 🚀