- 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, contributions to
Facade will impact the work of others. For example, changes to code,
infrastructure, policy, documentation and translations during a release
may negatively impact others' work.
- Be respectful. The
community and its members treat one another with respect. Everyone can
make a valuable contribution to Facade. 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 community to be respectful when
dealing with other contributors as well as with people outside the
project and with players of Facade.
- Be collaborative. Collaboration
is central to Facade and to the larger free software community. We
encourage individuals and teams to work together whether inside or
outside the Facade 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.
- When we disagree, we consult others. Disagreements,
both social and technical, happen all the time and the Facade 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 also several teams and team leaders, who
may be able to help us figure out the best direction for Facade. When
our goals differ dramatically, we encourage the creation of alternative
sets of ideas, or derivative ideas, so that the community can contribute
new ideas and provide feedback.
- When we are unsure, we ask for help. Nobody
knows everything, and nobody is expected to be perfect in the
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.
- Step down considerately. Members
of every project come and go and Facade 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 minimizes 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.
Please follow these guidelines in addition to the general code of conduct:
- Please use a valid email address to which direct responses can be made.
avoid flamewars, trolling, personal attacks, and repetitive arguments.
On technical matters, the technical team can make a final decision.
The Facade 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 Ubuntu Project.