Ubuntu-OSE Code of Conduct: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
Your work will be used by other people, and you in turn will depend on the work of others. | Your work will be used by other people, and you in turn will depend on the work of others. | ||
Any decision you make will affect users and colleagues, and we expect you to take those | Any decision you make will affect users and colleagues, and we expect you to take those | ||
consequences into account when making decisions. | consequences into account when making decisions. Consider how your behavior | ||
will affect the | will affect the well being of others around you. | ||
'''Be respectful''' | '''Be respectful''' | ||
| Line 15: | Line 15: | ||
now and then, but we cannot allow that frustration to turn into a personal attack. It’s | 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 | important to remember that a community where people feel uncomfortable or threatened | ||
is not a productive one. We expect members of the | is not a productive one. We expect members of the OSE community to be respectful | ||
when dealing with other contributors as well as with people outside the | when dealing with other contributors as well as with people outside the OSE project, | ||
and with users of | and with users of OSE. | ||
'''Be collaborative''' | '''Be collaborative''' | ||
OSE is about collaboration and working together. Collaboration | |||
reduces redundancy of work done in the | reduces redundancy of work done in the Open Hardware world, and improves the quality | ||
of the | of the hardware produced. You should aim to collaborate with other OSE maintainers, | ||
as well as with the upstream community that is interested in the work you do. Your work | as well as with the upstream community that is interested in the work you do. Your work | ||
should be done transparently and | should be done transparently and updates from OSE should be given back to the | ||
community when they are made, not just when the distribution releases. If you wish to | community when they are made, not just when the distribution releases. If you wish to | ||
work on new | work on new ideas 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 | 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 | from your colleagues about the correct implementation of an idea, so don’t feel obliged to | ||
| Line 36: | Line 36: | ||
'''When you disagree, consult others''' | '''When you disagree, consult others''' | ||
Disagreements, both political and technical, happen all the time, and the | Disagreements, both political and technical, happen all the time, and the OSE | ||
community is no exception. The important goal is not to avoid disagreements or differing | 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 | views but to resolve them constructively. You should turn to the community and to the | ||
community process to seek advice and to resolve disagreements | community process to seek advice and to resolve disagreements. If you really want to go a different | ||
way, then we encourage you to document and publish your work, so that the | |||
way, then we encourage you to | |||
community can try out your changes and ideas for itself and contribute to the discussion. | community can try out your changes and ideas for itself and contribute to the discussion. | ||
'''When you are unsure, ask for help''' | '''When you are unsure, ask for help''' | ||
Nobody knows everything, and nobody is expected to be perfect in the | Nobody knows everything, and nobody is expected to be perfect in the OSE community | ||
(except of course the SABDFL [Self-Appointed Benevolent Dictator for Life]). Asking | (except of course the SABDFL [Self-Appointed Benevolent Dictator for Life]). Asking | ||
questions avoids many problems down the road, and so questions are encouraged. Those | questions avoids many problems down the road, and so questions are encouraged. Those | ||
who are asked should be responsive and helpful. However, when asking a question, care | who are asked should be responsive and helpful. However, when asking a question, care | ||
must be taken to do so in an appropriate forum. Off-topic questions, such as requests for | must be taken to do so in an appropriate forum. Off-topic questions, such as requests for | ||
help on | help on an entirely unrelated project, detract from productive discussion. | ||
'''Step down considerately''' | '''Step down considerately''' | ||
Developers on every project come and go, and | Developers on every project come and go, and OSE is no different. When you leave or | ||
disengage from the project, in whole or in part, we ask that you do so in a way that | disengage from the project, in whole or in part, we ask that you do so in a way that | ||
minimizes disruption to the project. This means you should tell people you are leaving | minimizes disruption to the project. This means you should tell people you are leaving | ||
Revision as of 20:08, 13 July 2012
These are OSE guidelines for basic conduct, based on slight modification of the Ubuntu Code of Conduct:
Be considerate
Your work will be used by other people, and you in turn will depend on the work of others. Any decision you make will affect users and colleagues, and we expect you to take those consequences into account when making decisions. Consider how your behavior will affect the well being of others around you.
Be respectful
The OSE community and its members treat one another with respect. Everyone can make a valuable contribution to OSE. 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 OSE community to be respectful when dealing with other contributors as well as with people outside the OSE project, and with users of OSE.
Be collaborative
OSE is about collaboration and working together. Collaboration reduces redundancy of work done in the Open Hardware world, and improves the quality of the hardware produced. You should aim to collaborate with other OSE maintainers, as well as with the upstream community that is interested in the work you do. Your work should be done transparently and updates from OSE should be given back to the community when they are made, not just when the distribution releases. If you wish to work on new ideas 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.
When you disagree, consult others
Disagreements, both political and technical, happen all the time, and the OSE 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. If you really want to go a different way, then we encourage you to document and publish your work, so that the community can try out your changes and ideas for itself and contribute to the discussion.
When you are unsure, ask for help
Nobody knows everything, and nobody is expected to be perfect in the OSE community (except of course the SABDFL [Self-Appointed Benevolent Dictator for Life]). Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Off-topic questions, such as requests for help on an entirely unrelated project, detract from productive discussion.
Step down considerately
Developers on every project come and go, and OSE is no different. When you leave or disengage from the project, in whole or in part, we ask that you do so in a way that minimizes disruption to the project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you leave off.