Changes

{{draft}}

{{Graduate | Hi Priority}}

To be effective, the members of the Sugar Labs community must to work together; our code of conduct lays down the "ground rules" for our cooperative efforts.

To be effective, the members of the Sugar Labs community must to work together; our code of conduct lays down the "ground rules" for our cooperative efforts.

That collaboration depends on good relationships between developers (and end-users). We have agreed upon the following Code of Conduct as a guide to our collaboration and cooperation.

That collaboration depends on good relationships between developers (and end-users). We have agreed upon the following Code of Conduct as a guide to our collaboration and cooperation.

This Code of Conduct covers your behavior as a member of the Sugar Labs community, in any forum, mailing list, wiki, web site, IRC channel, code-sprint, public meeting, or private correspondence. The Oversight Board will arbitrate in any dispute over the conduct of a member of the community.

This Code of Conduct covers your behavior as a member of the Sugar Labs community, in any forum, mailing list, wiki, web site, IRC channel, code-sprint, public meeting, or private correspondence. The Oversight Board will arbitrate in any dispute over the conduct of a member of the community.

Sugar Labs and Free Software are about collaboration and working together. Collaboration reduces redundancy of work done in the Free Software world, and improves the quality of the software produced. You should aim to collaborate with other Sugar contributors, as well as with the entire Sugar ecosystem that is interested in the work you do. Your work should be done transparently and patches from Sugar should be given back to the community when they are made, not just when the distribution releases. If you wish to work on new code for existing upstream projects, at least keep those projects informed of your ideas and progress. It may not be possible to get consensus from upstream or even from your colleagues about the correct implementation of an idea, so don't feel obliged to have that agreement before you begin, but at least keep the outside world informed of your work, and publish your work in a way that allows outsiders to test, discuss and contribute to your efforts.

Sugar Labs and Free Software are about collaboration and working together. Collaboration reduces redundancy of work done in the Free Software world, and improves the quality of the software produced. You should aim to collaborate with other Sugar contributors, as well as with the entire Sugar ecosystem that is interested in the work you do. Your work should be done transparently and patches from Sugar should be given back to the community when they are made, not just when the distribution releases. If you wish to work on new code for existing upstream projects, at least keep those projects informed of your ideas and progress. It may not be possible to get consensus from upstream or even from your colleagues about the correct implementation of an idea, so don't feel obliged to have that agreement before you begin, but at least keep the outside world informed of your work, and publish your work in a way that allows outsiders to test, discuss and contribute to your efforts.

== Be Flexible ==

== Be flexible ==

The Sugar Labs community and its members come from various backgrounds and cultures.  It is important to remember that Sugar Labs is a place for educators and developers; parents, teachers, and children; and speakers of many languages to work together.  Try to find the appropriate forum for your topic, level or expertises, or language.  If you come across a post that is in an incorrect forum, please respectfully redirect the poster to the appropriate.  However, a project such as Sugar Labs requires communication between groups and languages.

The Sugar Labs community and its members come from various backgrounds and cultures.  It is important to remember that Sugar Labs is a place for educators and developers; parents, teachers, and children; and speakers of many languages to work together.  Try to find the appropriate forum for your topic, level or expertises, or language.  If you come across a post that is in an incorrect forum, please respectfully redirect the poster to the appropriate.  However, a project such as Sugar Labs requires communication between groups and languages.

== When you disagree, consult others ==

== When you disagree, consult others ==

Disagreements, both political and technical, happen all the time and the Sugar community is no exception. The important goal is not to avoid disagreements or differing views but to resolve them constructively. You should turn to the community and to the community process to seek advice and to resolve disagreements. We have the oversight board which will help to decide the right course for Sugar Labs. There are also several Project Teams and Team Leaders, who may be able to help you figure out which direction will be most acceptable. If you really want to go a different way, then we encourage you to make fork the Sugar code base so that the community can try out your changes and ideas for itself and contribute to the discussion.

The Sugar community is not immune to disagreements—both political and technical. We do not try to avoid disagreements or differing views, but we do try to resolve them constructively. Turn to the community and to community processes to seek advice and to mediate and resolve disagreements. Community resources include an Oversight Board which will help to decide the right course for Sugar Labs, project teams and team leaders who may be able to help you, and an ombudsman who will investigate complaints and, where possible, resolve them by making recommendations to the community. We welcome you to fork the Sugar code base if you are determined to go your own way; enabling the community to test your ideas and possibly merge them back into the mainstream.

== When you are unsure, ask for help ==

== When you are unsure, ask for help ==

This code of conduct applies very much to your behavior in mailing lists and web forums.

This code of conduct applies very much to your behavior in mailing lists and web forums.

#Please watch you language.  The Sugar community is a family-friendly place.

#Please watch your language.  The Sugar community is a family-friendly place.

#Please use a valid email address to which direct responses can be made.

#Please use a valid email address to which direct responses can be made.

#Please avoid flamewars, trolling, personal attacks, and repetitive arguments.

#Please avoid flamewars, trolling, personal attacks, and repetitive arguments.

== Spanish version ==

== Spanish version ==

A Spanish version is available at http://co.sugarlabs.org/go/Código_de_Conducta

A Spanish version is available at<nowiki/>http://pe.sugarlabs.org/ir/Coordinaci%C3%B3n

== Version en Español ==

== Version en Español ==

La version en español de este documento esta disponible en http://co.sugarlabs.org/go/Código_de_Conducta

La version en español de este documento esta disponible en http://pe.sugarlabs.org/ir/Coordinaci%C3%B3n