7.1.2
by Mark Shuttleworth
Small cleanup of language with no changes in meaning |
1 |
= Ubuntu Code of Conduct v1.1 = |
1
by Matthew East
Create branch, add current version of CoC |
2 |
|
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
3 |
This Code of Conduct covers our behaviour as members of the Ubuntu |
1
by Matthew East
Create branch, add current version of CoC |
4 |
Community, in any forum, mailing list, wiki, web site, IRC channel, |
7.1.2
by Mark Shuttleworth
Small cleanup of language with no changes in meaning |
5 |
install-fest, public meeting or private correspondence. Ubuntu |
6 |
governance bodies are ultimately accountable to the Ubuntu Community |
|
7 |
Council and will arbitrate in any dispute over the conduct of a member |
|
8 |
of the community. |
|
1
by Matthew East
Create branch, add current version of CoC |
9 |
|
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
10 |
'''Be considerate.''' Our work will be used by other people, and |
11 |
we in turn will depend on the work of others. Any decision we take |
|
12 |
will affect users and colleagues, and we should take those |
|
13 |
consequences into account when making decisions. Ubuntu has |
|
14 |
millions of users and thousands of contributors. Even if it's not |
|
15 |
obvious at the time, our contributions to Ubuntu will impact the |
|
16 |
work of others. For example, changes to code, infrastructure, |
|
7.1.1
by Mark Shuttleworth
Add closing paragraph |
17 |
policy, documentation, and translations during a release may |
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
18 |
negatively impact others' work. |
1
by Matthew East
Create branch, add current version of CoC |
19 |
|
20 |
'''Be respectful.''' The Ubuntu community and its members treat |
|
21 |
one another with respect. Everyone can make a valuable |
|
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
22 |
contribution to Ubuntu. We may not always agree, but disagreement |
23 |
is no excuse for poor behaviour and poor manners. We might all |
|
24 |
experience some frustration now and then, but we cannot allow that |
|
25 |
frustration to turn into a personal attack. It's important to |
|
26 |
remember that a community where people feel uncomfortable or |
|
27 |
threatened is not a productive one. We expect members of the |
|
28 |
Ubuntu community to be respectful when dealing with other |
|
29 |
contributors as well as with people outside the Ubuntu project and |
|
30 |
with users of Ubuntu. |
|
31 |
||
32 |
'''Be collaborative.''' Collaboration is central to Ubuntu and to |
|
33 |
the larger free software community. This collaboration involves |
|
34 |
individuals working with others in teams within Ubuntu, teams |
|
35 |
working with each other within Ubuntu, and individuals and teams |
|
36 |
within Ubuntu working with other projects outside. This |
|
37 |
collaboration reduces redundancy, and improves the quality of our |
|
38 |
work. Internally and externally, we should always be open to |
|
39 |
collaboration. Wherever possible, we should work closely with |
|
7.1.1
by Mark Shuttleworth
Add closing paragraph |
40 |
upstream projects and others in the free software community to |
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
41 |
coordinate our technical, advocacy, documentation, and other work. |
42 |
Our work should be done transparently and we should involve as |
|
43 |
many interested parties as early as possible. If we decide to |
|
5.1.1
by Emma Jane
Minor language changes to improve clarity and reduce redundant statements. |
44 |
take a different approach than others, we will let them know early, |
45 |
document our work and inform others regularly of our progress. |
|
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
46 |
|
7.1.2
by Mark Shuttleworth
Small cleanup of language with no changes in meaning |
47 |
'''When we disagree, we consult others.''' Disagreements, both |
48 |
social and technical, happen all the time and the Ubuntu |
|
7.1.1
by Mark Shuttleworth
Add closing paragraph |
49 |
community is no exception. It is important that we resolve |
5.1.1
by Emma Jane
Minor language changes to improve clarity and reduce redundant statements. |
50 |
disagreements and differing views constructively and with the help |
7.1.1
by Mark Shuttleworth
Add closing paragraph |
51 |
of the community and community processes. We have the Technical |
52 |
Board, the Community Council, and a series of other governance |
|
53 |
bodies which help to decide the right course for Ubuntu. There are |
|
54 |
also several Project Teams and Team Leaders, who may be able to |
|
55 |
help us figure out the best direction for Ubuntu. When our goals |
|
56 |
differ dramatically, we encourage the creation of alternative sets of |
|
57 |
packages, or derivative distributions, using the Ubuntu Package |
|
58 |
Management framework, so that the community can test new ideas and |
|
59 |
contribute to the discussion. |
|
60 |
||
7.1.2
by Mark Shuttleworth
Small cleanup of language with no changes in meaning |
61 |
'''When we are unsure, we ask for help.''' Nobody knows |
1
by Matthew East
Create branch, add current version of CoC |
62 |
everything, and nobody is expected to be perfect in the Ubuntu |
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
63 |
community. Asking questions avoids many problems down the road, |
7.1.1
by Mark Shuttleworth
Add closing paragraph |
64 |
and so questions are encouraged. Those who are asked questions should |
65 |
be responsive and helpful. However, when asking a question, care must |
|
66 |
be taken to do so in an appropriate forum. |
|
1
by Matthew East
Create branch, add current version of CoC |
67 |
|
5
by mako at atdot
worked with dholbach to write an extensive revision of the code |
68 |
'''Step down considerately.''' Members of every project come and |
69 |
go and Ubuntu is no different. When somebody leaves or disengages |
|
70 |
from the project, in whole or in part, we ask that they do so in a |
|
71 |
way that minimises disruption to the project. This means they |
|
72 |
should tell people they are leaving and take the proper steps to |
|
5.1.1
by Emma Jane
Minor language changes to improve clarity and reduce redundant statements. |
73 |
ensure that others can pick up where they left off. |
7.1.1
by Mark Shuttleworth
Add closing paragraph |
74 |
|
75 |
We pride ourselves on building a productive, happy and agile community |
|
76 |
that can welcome new ideas in a complex field, and foster collaboration |
|
77 |
between groups with very different needs, interests and goals. We hold |
|
78 |
our leaders to an even higher standard, in the Leadership Code of |
|
79 |
Conduct, and arrange the governance of the community to ensure that |
|
7.1.2
by Mark Shuttleworth
Small cleanup of language with no changes in meaning |
80 |
issues can be raised with leaders who are engaged, interested and |
81 |
competent to help resolve them. |
|
82 |