Community Guidelines

All community members must abide by rules of common sense, civility and good neighborliness. Frank discussion is welcomed and encouraged with the goal of arriving at the best technical solution possible. Community participants must adhere to these simple rules:

• Respect and acknowledge all contributions, suggestions and comments from the community.
• Listen and be open to all opinions, which are subject to open discussion.
• Help each other.
• Assume people mean well.

Community Consensus, Lazy Consensus and Slient Consent

Community consensus about a Project issue means that the issue has been submitted to and discussed by Contributors, and that ALL discussing member agree about the issue.

Lazy consensus means that Contributors may proceed with work when they have reason to believe that other Contributors in the community will agree with the direction of their work, and do not need to stop or initiate unnecessary discussion about the work. Contributors should publish their work (that is, merge proposals to master branch) in a timely manner to allow others to possibly raise issues about the work. When the Contributor is not sure there will be consensus, they should raise a proposal to the community via appropriate public communication channels(currently Github issues is possible way to achieve this)

Silent Consent means that those who do not offer a reasoned alternative in course of the discussion implicitly agree with the proposal.

Meritocracy

Responsibilities in the project (including decision making) are given to those who exhibit both the technical skill and dedication to project via their ongoing valuable contributions. Decision making happens inside the community, with more weight given to those who are more familiar with the code.