## Table of Contents - [Code of Conduct](#code-of-conduct) - [Community roles](#community-roles) - [How to become a contributor](#how-to-become-a-contributor) - [How to become a maintainer](#how-to-become-a-maintainer) - [How to become a council member](#how-to-become-a-council-member) - [Council members](#council-members) - [Maintainers](#maintainers) - [Contributors](#contributors) ## Code of Conduct Please see [CODE OF CONDUCT](CODE_OF_CONDUCT.md) ## Community roles Besides being the users of Zadig, which is a great way of contributing to the community by itself (and thank you!), there are 3 active community roles: - Contributor - Maintainer - Council member Note that the latter role is built on top of the former -- i.e. A council member is also a maintainer and a contributor, a maintainer is a contributor as well. Please see the following table for their primary responsibilities: | Role | Primary responsibilities | |----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Contributor | No particular responsibilities, all healthy contributions are welcome. | | Maintainer | Technical: review PRs, participate and review designs, responding to issues. Recognized as a solid and respectful contributor.
Community: guide the community, role model a high standard of behavior.
Strategy: more seasoned maintainers might be consulted by the project council for roadmaps and strategies. | | Council Member | Technical:
Decision maker for key designs.
Help people succeed, guide technical directions.
Create and maintain effective development processes.
Community:
Recognize community contributions and promote excellent contributors to advance their roles (e.g. From contributor to maintainer, or from maintainer to be in the council).
Guide the value of the community -- set the tone. Ultimately responsible for a healthy community.
Strategy:
Set strategy, develop roadmap | | | | ## How to become a contributor? Anyone can be recognized as a Zadig contributor, as long as they manage to have one PR accepted, answered questions in the community forum, or simply reported an issue. ## How to become a maintainer? Must be a contributor first, and nominated by an existing maintainer or a council member. The council will make a decision for the nomination. Normally both the technical and community contribution will be taken into consideration. For example, these are strong signals if the candidate has been a productive contributor, played a key role in driving a few designs, demonstrated both technical skills and enthusiasm towards the project, and been a great citizen for the community. ## How to become a council member? The candidate has to be a maintainer first and be nominated by 2 council members. The council will make a decision for the nomination. The candidate has to have demonstrated strategic impact on the project over a relatively long horizon (or in a consistent way), for example, - Initiated a series of key designs and successfully drove them to be landed - Having a positive impact over the community such as constantly guiding new members, or consistently answering questions - Successfully driving the project to be much more impactful and modeling deep understanding in the product and the industry ## Council members [A list of current council] ## Maintainers [a list of current maintainers] ## Contributors - [nighca](https://github.com/nighca) - [xen0n](https://github.com/xen0n)