Merge lp:~akgraner/ubuntu-codeofconduct/proposedv2coc into lp:ubuntu-codeofconduct
- proposedv2coc
- Merge into trunk
Status: | Merged |
---|---|
Merged at revision: | 15 |
Proposed branch: | lp:~akgraner/ubuntu-codeofconduct/proposedv2coc |
Merge into: | lp:ubuntu-codeofconduct |
Diff against target: |
206 lines (+202/-0) 1 file modified
MergedCodeOfConduct.txt (+202/-0) |
To merge this branch: | bzr merge lp:~akgraner/ubuntu-codeofconduct/proposedv2coc |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Community Council | Pending | ||
Review via email: mp+97139@code.launchpad.net |
Commit message
Description of the change
Combined the CoC and LCoC into one document for version control, editing and final approval.
Daniel Holbach (dholbach) wrote : | # |
Amber Graner (akgraner) wrote : | # |
So you need the
On Tue, Mar 13, 2012 at 7:22 AM, Daniel Holbach
<email address hidden> wrote:
> I just pushed lp:~dholbach/ubuntu-codeofconduct/proposedv2coc which adds a missing revision to MergedCodeOfCon
>
> For (maybe) better readability:
> - wdiff between CodeOfConduct.txt and MergedCodeOfCon
> - wdiff between LeadershipCodeO
> --
> https:/
> You are the owner of lp:~akgraner/ubuntu-codeofconduct/proposedv2coc.
So you need the
[-v1.1-] {+v2.0+} =
{+
in the one I did and so the diff will show up?
and the other one in the LCoC has the suggestions for defining various
phrasing. That's pretty cool!
Thanks Daniel!
~Amber
--
Amber Graner//akgraner//
http://
http://
Just me Amber.
There are lots of Linux users who don't care how the kernel works, but
only want to use it. That is a tribute to how good Linux is.
Linus Torvalds
Charles Profitt (cprofitt) wrote : | # |
Read Daniel's version. It looks good to me on quick review. Nice work Amber and Daniel.
Daniel Holbach (dholbach) wrote : | # |
Amber: you just need to run (in your local branch):
bzr pull lp:~dholbach/ubuntu-codeofconduct/proposedv2coc
bzr push
bzr lp-open
and click on the "(+) Propose for merging" or "Resubmit" link to get the updated version with the bits which Matt added in an older revision of the CoC. The pastebin links are basically just a different representation of the proposed changes.
Daniel Holbach (dholbach) wrote : | # |
A few small, but not too important, things I found:
- "Ubuntu is an African concept of 'humanity towards others'." could probably be paraphrased to
"Ubuntu is an ancient African word meaning 'humanity to others'."
- in the suggested changes to the LCoC bits we talk about "community members" again, can we call
them participants like in the new CoC version?
- I'm not quite sure what "work within the Ubuntu system to effect change" means.
- I'm not a huge fan of "their team" as opposed to "the team".
Charles Profitt (cprofitt) wrote : | # |
I like the suggestions put forth by Daniel.
Preview Diff
1 | === added file 'MergedCodeOfConduct.txt' |
2 | --- MergedCodeOfConduct.txt 1970-01-01 00:00:00 +0000 |
3 | +++ MergedCodeOfConduct.txt 2012-03-13 04:22:17 +0000 |
4 | @@ -0,0 +1,202 @@ |
5 | += Ubuntu Code of Conduct v2.0 = |
6 | + |
7 | +== Community == |
8 | + |
9 | +Ubuntu is an African concept of 'humanity towards others'. |
10 | + |
11 | +This Code of Conduct covers our behaviour as members of the Ubuntu |
12 | +Community, in any forum, mailing list, wiki, web site, IRC channel, |
13 | +install-fest, public meeting or private correspondence. Ubuntu governance |
14 | +bodies are ultimately accountable to the Ubuntu Community Council and as |
15 | +such the Ubuntu Community Council will arbitrate in any dispute over the |
16 | +conduct of a member of the community. |
17 | + |
18 | + '''Be considerate.''' Our work will be used by other people, |
19 | + and we in turn will depend on the work of others. Any |
20 | + decision we take will affect users and colleagues, and we |
21 | + should take those consequences into account when making |
22 | + decisions. Ubuntu has millions of users and thousands of |
23 | + contributors. Even if it's not obvious at the time, our |
24 | + contributions to Ubuntu will impact the work of others. For |
25 | + example, changes to code, infrastructure, policy, |
26 | + documentation, and translations during a release may |
27 | + negatively impact others' work. |
28 | + |
29 | + '''Be respectful.''' The Ubuntu community and its members |
30 | + treat one another with respect. Everyone can make a |
31 | + valuable contribution to Ubuntu. We may not always agree, |
32 | + but disagreement is no excuse for poor behaviour and poor |
33 | + manners. We might all experience some frustration now and |
34 | + then, but we cannot allow that frustration to turn into a |
35 | + personal attack. It's important to remember that a |
36 | + community where people feel uncomfortable or threatened is |
37 | + not a productive one. We expect members of the Ubuntu |
38 | + community to be respectful when dealing with other |
39 | + contributors as well as with people outside the Ubuntu |
40 | + project and with users of Ubuntu. '''Be collaborative. |
41 | + |
42 | + ''' Collaboration is central to Ubuntu and to the larger |
43 | + free software community. This collaboration involves |
44 | + individuals working with others in teams within Ubuntu, |
45 | + teams working with each other within Ubuntu, and |
46 | + individuals and teams within Ubuntu working with other |
47 | + projects outside. This collaboration reduces redundancy, |
48 | + and improves the quality of our work. Internally and |
49 | + externally, we should always be open to |
50 | + collaboration. Wherever possible, we should work closely |
51 | + with upstream projects and others in the free software |
52 | + community to coordinate our technical, advocacy, |
53 | + documentation, and other work. Our work should be done |
54 | + transparently and we should involve as many interested |
55 | + parties as early as possible. If we decide to take a |
56 | + different approach than others, we will let them know |
57 | + early, document our work and inform others regularly of our |
58 | + progress. |
59 | + |
60 | + '''When we disagree, we consult others.''' Disagreements, |
61 | + both social and technical, happen all the time and the |
62 | + Ubuntu community is no exception. It is important that we |
63 | + resolve disagreements and differing views constructively |
64 | + and with the help of the community and community processes. |
65 | + We have the Technical Board, the Community Council, and a |
66 | + series of other governance bodies which help to decide the |
67 | + right course for Ubuntu. There are also several Project |
68 | + Teams and Team Leaders, who may be able to help us figure |
69 | + out the best direction for Ubuntu. When our goals differ |
70 | + dramatically, we encourage the creation of alternative sets |
71 | + of packages, or derivative distributions, using the Ubuntu |
72 | + Package Management framework, so that the community can |
73 | + test new ideas and contribute to the discussion. |
74 | + |
75 | + '''When we are unsure, we ask for help.''' Nobody knows |
76 | + everything, and nobody is expected to be perfect in the |
77 | + Ubuntu community. Asking questions avoids many problems |
78 | + down the road, and so questions are encouraged. Those who |
79 | + are asked questions should be responsive and helpful. |
80 | + However, when asking a question, care must be taken to do |
81 | + so in an appropriate forum. |
82 | + |
83 | + '''Step down considerately.''' Members of every project |
84 | + come and go and Ubuntu is no different. When somebody |
85 | + leaves or disengages from the project, in whole or in part, |
86 | + we ask that they do so in a way that minimises disruption |
87 | + to the project. This means they should tell people they are |
88 | + leaving and take the proper steps to ensure that others can |
89 | + pick up where they left off. |
90 | + |
91 | +== Community Leadership == |
92 | + |
93 | +We pride ourselves on building a productive, happy and agile community that |
94 | +can welcome new ideas in a complex field, and foster collaboration between |
95 | +groups with very different needs, interests and goals. We also recognize |
96 | +the vast experience and expertise each member of our community brings to |
97 | +the teams they choose to participate and collaborate with and as such each |
98 | +member of our community has the potential to stand in a leadership |
99 | +position. Whether the leadership is one that is of appointment, election, |
100 | +or example we hold our leaders to an even higher standard, and as such each |
101 | +person signing the Code of Conduct needs to be familiar with those |
102 | +standards so that when in position of leadership can arrange the governance |
103 | +of the community to ensure that issues can be raised with leaders who are |
104 | +engaged, interested and competent to help resolve them. |
105 | + |
106 | + |
107 | +Ubuntu Leadership The Ubuntu Code of Conduct describes the standard for all |
108 | +conduct in the Ubuntu community. Leaders however, are held to a higher |
109 | +standard. This addition to the Code of Conduct provides a set of guidelines |
110 | +which explains to all members the high standards of conduct that leaders in |
111 | +the Ubuntu community are expected to uphold. |
112 | + |
113 | + |
114 | +There are many, many people who hold leadership positions in Ubuntu - from |
115 | +the leaders of translation teams for specific languages, to those who hold |
116 | +positions on our Technical Board and Community Council. Our community |
117 | +depends on the drive and inspiration of many people who start LoCo teams or |
118 | +project teams focused on a particular end goal. We expect everyone who |
119 | +takes on a leadership role to meet this higher standard of conduct. |
120 | + |
121 | + '''Leadership By Example''' We expect leadership by |
122 | + example. In Ubuntu, leadership is not an award, right, or |
123 | + title; it is a privilege. A leader will only retain his or |
124 | + her position as long as he or she acts as a leader. This |
125 | + means that they act with civility, respect, and trust in |
126 | + the ways described in the Code of Conduct. It also means |
127 | + that their contributions are sustained, significant, and |
128 | + reliable for the period that they lead. Leaders in Ubuntu |
129 | + are not autocrats. Leaders in Ubuntu can not and will not |
130 | + stay leaders only because they got there first. Their role |
131 | + stems from shared recognition and respect from their team. |
132 | + |
133 | + '''Respecting Ubuntu Processes and Principles''' The Code |
134 | + of Conduct not only applies to community members, it |
135 | + applies to our leadership even more. Leaders are expected |
136 | + to show more patience, respect, and civility than other |
137 | + members of the Ubuntu community. As leaders, they represent |
138 | + their team and, ultimately, the whole Ubuntu |
139 | + project. Leaders are expected to reflect the values that |
140 | + Ubuntu stands for and the behaviors that Ubuntu holds as |
141 | + paramount. Additionally, they are to act in accordance |
142 | + with Ubuntu governance principles and structures and work |
143 | + within the Ubuntu system to effect change. |
144 | + |
145 | + '''Delegation''' A virtuoso is judged by their actions; a |
146 | + leader is judged by the actions of their team. A leader in |
147 | + Ubuntu knows when to ask for help and when to step |
148 | + back. Good leaders know when not to make a decision but to |
149 | + delegate it to their team. Of course, leadership does not |
150 | + mean that leaders delegate unpleasant work to others; |
151 | + instead, leaders strike a balance between their own hard |
152 | + work -- as they lead by example -- with that of delegation |
153 | + to others. A leader's foremost goal is ensuring that their |
154 | + team and its members succeed. |
155 | + |
156 | + '''Credit''' A good leader does not seek the limelight, but |
157 | + instead aims to congratulate their team for the work they |
158 | + do. While leaders are frequently more visible than their |
159 | + team, leaders in Ubuntu should use that visibility to |
160 | + highlight the great work of their team members and others. |
161 | + |
162 | + '''Conflicts of Interest''' A leader notices when they are |
163 | + conflicted and delegates decisions to others on their team |
164 | + or to other teams or governing councils. When in doubt, |
165 | + leaders publicly ask for a second opinion. Leaders also |
166 | + realize that perceived conflicts of interest are as |
167 | + important as real conflicts of interest and are cognizant |
168 | + of perceptions; they understand that their actions are as |
169 | + tainted by perceived conflicts as by real ones. '''Keeping |
170 | + the Personal Personal''' No team should be an extension of |
171 | + its leader's personality. A leader’s personal feelings and |
172 | + desires will diverge from the interest of their teams. When |
173 | + acting in their capacity as leaders, leaders should not |
174 | + ignore their own beliefs, feelings, and principles but must |
175 | + hold the interests of their team and the Ubuntu community |
176 | + above their own convictions. Leaders make difficult choices |
177 | + but are careful to act in the best interests of their |
178 | + communities. They work with established processes in the |
179 | + community and delegate decisions to others who can. |
180 | + |
181 | + '''Stepping Down''' The Ubuntu Code of Conduct discusses |
182 | + the importance of gracefully stepping down from a |
183 | + position. This is particularly important for leaders who |
184 | + are responsible for decisions or specific processes - for |
185 | + example, if your participation is needed to reach quorum in |
186 | + a team council. If someone in a leadership role does not |
187 | + have time to fulfill their role temporarily, they should |
188 | + warn their team in advance. If an absence becomes extended, |
189 | + they should step down from their leadership position until |
190 | + they have more time to follow through. Similarly, leaders |
191 | + should step down gracefully -- as described in the Code of |
192 | + Conduct. When someone takes on a leadership position in |
193 | + Ubuntu, they are making a commitment to step down |
194 | + gracefully and to ensure that others on the team can easily |
195 | + continue. |
196 | + |
197 | + Note that this is less important in cases where the |
198 | + leadership role does not "block" decisions while the person |
199 | + is absent. For example, if you are one of a team of 50 list |
200 | + moderators, then an extended absence does not mean you |
201 | + should necessarily step down, because decisions will not be |
202 | + blocked by you not being there. Conversely, if your |
203 | + leadership seat is essential for decisions, then extended |
204 | + absences should be very carefully managed, and you should |
205 | + consider stepping down or at least nominating a stand-in |
206 | + while you will be away. |
I just pushed lp:~dholbach/ubuntu-codeofconduct/proposedv2coc which adds a missing revision to MergedCodeOfCon duct.txt
For (maybe) better readability: duct.txt: http:// paste.ubuntu. com/881697 fConduct. txt and MergedCodeOfCon duct.txt: http:// paste.ubuntu. com/881698/
- wdiff between CodeOfConduct.txt and MergedCodeOfCon
- wdiff between LeadershipCodeO