Hacks Hackers Charter

Stephen Abbott edited this page Jul 16, 2015 · 4 revisions

We want a productive, happy and agile community that can welcome new ideas, improve every process every year, and foster collaboration between groups with very different needs, interests and skills. We gain strength from diversity, and actively seek participation from those who enhance it.

This code of conduct exists to ensure that diverse groups collaborate to mutual advantage and enjoyment. We expect it to be honored by everyone who is a part of the Hacks/Hackers community

RULE ONE: Be Considerate

Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should consider them when making decisions.

RULE TWO: Be Respectful

Disagreement is no excuse for poor manners. We work together to resolve conflict, assume good intentions and do our best to act in an empathic fashion. We don't allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.

RULE THREE: Take responsibility for our words and our actions

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

RULE FOUR: Be collaborative

Collaboration between teams that each have their own goal and vision is essential; for the whole to be more than the sum of its parts, each part must make an effort to understand the whole. Collaboration reduces redundancy and improves the quality of our work. Internally and externally, we celebrate good collaboration. We prefer to work transparently and involve interested parties as early as possible.

RULE FIVE: Value decisiveness, clarity and consensus

Disagreements, social and technical, are normal, but we do not allow them to persist and fester leaving others uncertain of the agreed direction. We expect participants in the project to resolve disagreements constructively. When they cannot, we escalate the matter to structures with designated leaders to arbitrate and provide clarity and direction.

RULE SIX: Ask for help when unsure

Nobody is expected to be perfect in this community. Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful.

RULE SEVEN: Step down considerately

When somebody leaves or disengages from the community, we ask that they do so in a way that minimises disruption to the project. They should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.

*These guidelines are modeled after the Ubuntu Code of Conduct, and likewise licensed under Creative Commons Attribution-Share Alike 3.0.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.