LHC@home: Test4Theory

This code of conduct covers our behavior as members of the Test4Theory (T4T) Community, in any forum, mailing list, wiki, website, Internet relay chat (IRC) channel, install-fest, public meeting or private correspondence. T4T governance bodies are ultimately accountable to the T4T Community Council and will arbitrate in any dispute over the conduct of a member of the community.
 

1. 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 take those consequences into account when making decisions. Even if it's not obvious at the time, our contributions to T4T will impact the work of others. For example, changes to code, infrastructure, policy, documentation and translations during a release may negatively impact others' work.
2. Be respectful. The T4T community and its members treat one another with respect. Everyone can make a valuable contribution to the project. We may not always agree, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the T4T community to be respectful when dealing with other contributors as well as with people outside the T4T project and with users of T4T.
3. Be collaborative. Collaboration is central to T4T and to the larger free software community. We encourage individuals and teams to work together whether inside or outside the T4T Project. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream projects and others in the free software community to coordinate our efforts in all areas whether they be technical, advocacy or documentation. Our work should be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress.
4. When we disagree, we consult others. Disagreements, both social and technical, happen all the time and the T4T community is no exception. It is important that we resolve disagreements and differing views constructively and with the help of the community and community processes. There are several project team leaders, who may be able to help us figure out the best direction for T4T.
5. When we are unsure, we ask for help. Nobody knows everything, and nobody is expected to be perfect in the T4T community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum.
6. Step down considerately. Members of every project come and go and T4T is no different. When somebody leaves or disengages from the project, in whole or in part, we ask that they do so in a way that minimises disruption to the project. This means they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.

 The T4T code of conduct is licensed under the Creative Commons Attribution-Share Alike 3.0 license. You may re-use it for your own project, and modify it as you wish, just please allow others to use your modifications and give credit to the T4T Project!  This code of conduct applies to your behaviour in all the T4T project forums, mailing lists, IRC, etc. Please follow these guidelines in addition to the general code of conduct:

1. Please use a valid email address to which direct responses can be made.
2. Please avoid flamewars, trolling, personal attacks, and repetitive arguments.

 This code of conduct is based in the Ubuntu Code of Conduct.