Merge lp:~dholbach/launchpad/coc-1.1 into lp:launchpad/db-devel

Proposed by Curtis Hovey
Status: Merged
Approved by: Curtis Hovey
Approved revision: not available
Merged at revision: not available
Proposed branch: lp:~dholbach/launchpad/coc-1.1
Merge into: lp:launchpad/db-devel
Diff against target: 383 lines (+180/-94)
8 files modified
lib/canonical/launchpad/doc/canonical_url_examples.txt (+2/-2)
lib/canonical/launchpad/pagetests/basics/notfound-traversals.txt (+2/-2)
lib/lp/registry/codesofconduct/1.1.txt (+82/-0)
lib/lp/registry/model/codeofconduct.py (+1/-1)
lib/lp/registry/stories/gpg-coc/02-signcoc.txt (+4/-4)
lib/lp/registry/stories/gpg-coc/99-coc-presentation.txt (+3/-3)
lib/lp/registry/stories/gpg-coc/reformatted_11_coc.asc (+84/-81)
utilities/migrater/file-ownership.txt (+2/-1)
To merge this branch: bzr merge lp:~dholbach/launchpad/coc-1.1
Reviewer Review Type Date Requested Status
Curtis Hovey (community) code Approve
Review via email: mp+15505@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Curtis Hovey (sinzui) wrote :

I am resubmitting this proposal because it must be merged into db-devel, not devel

Revision history for this message
Curtis Hovey (sinzui) wrote :

Hi Daniel.

This branch looks good to land after a couple of changes.

We want to revert line 147 of the diff because it is testing the old CoC, not the current one. We also need to replace the signed CoC that we are testing with the 1.1 version signed by Sample Person--this is hard. I had learn how we did it the first time, and you should not need to struggle with this. You can apply the patch at http://pastebin.ubuntu.com/332568/ to fix the test and the test data.

After you have applied and pushed the changes. I will approve it to land. PQM reopens 4 days. I can land this branch at that time. Your work will be visible on staging.launchpad.net next week, and will be released on 2009-12-17

review: Needs Fixing (code)
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks a lot for the review and the fix to it. Those two were clearly "thinko"s. :-)

Great work!

Revision history for this message
Daniel Holbach (dholbach) wrote :

Hum... on a second look: should we instead of changing lib/lp/registry/stories/gpg-coc/reformatted_101_coc.asc not add lib/lp/registry/stories/gpg-coc/reformatted_11_coc.asc or something?

Revision history for this message
Curtis Hovey (sinzui) wrote :

I see the merge did not work as I expected. In my branch I renamed 101 to 11. Your branch only has the modifications. The test will fail because it is looking for reformatted_11_coc.asc. You can fix this using
    bzr mv lib/lp/registry/stories/gpg-coc/reformatted_101_coc.asc lib/lp/registry/stories/gpg-coc/reformatted_11_coc.asc

Revision history for this message
Daniel Holbach (dholbach) wrote :

I hope it's all good now.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Thanks Daniel.

I will land this when PQM opens at the end of the week.

review: Approve (code)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'lib/canonical/launchpad/doc/canonical_url_examples.txt'
2--- lib/canonical/launchpad/doc/canonical_url_examples.txt 2009-09-10 10:27:20 +0000
3+++ lib/canonical/launchpad/doc/canonical_url_examples.txt 2009-12-02 15:33:16 +0000
4@@ -94,8 +94,8 @@
5
6 An ICodeOfConduct
7
8- >>> canonical_url(cocset['1.0'])
9- u'http://launchpad.dev/codeofconduct/1.0'
10+ >>> canonical_url(cocset['1.1'])
11+ u'http://launchpad.dev/codeofconduct/1.1'
12
13
14 == Distributions, distroseriess and so on ==
15
16=== modified file 'lib/canonical/launchpad/pagetests/basics/notfound-traversals.txt'
17--- lib/canonical/launchpad/pagetests/basics/notfound-traversals.txt 2009-11-20 15:02:39 +0000
18+++ lib/canonical/launchpad/pagetests/basics/notfound-traversals.txt 2009-12-02 15:33:16 +0000
19@@ -96,8 +96,8 @@
20
21
22 >>> check("/codeofconduct")
23->>> check("/codeofconduct/1.0")
24->>> check("/codeofconduct/1.0/+download")
25+>>> check("/codeofconduct/1.1")
26+>>> check("/codeofconduct/1.1/+download")
27
28 >>> check("/projectgroups", auth=True)
29 >>> check("/projectgroups/+all", auth=True)
30
31=== added file 'lib/lp/registry/codesofconduct/1.1.txt'
32--- lib/lp/registry/codesofconduct/1.1.txt 1970-01-01 00:00:00 +0000
33+++ lib/lp/registry/codesofconduct/1.1.txt 2009-12-02 15:33:16 +0000
34@@ -0,0 +1,82 @@
35+= Ubuntu Code of Conduct v1.1 =
36+
37+This Code of Conduct covers our behaviour as members of the Ubuntu
38+Community, in any forum, mailing list, wiki, web site, IRC channel,
39+install-fest, public meeting or private correspondence. Ubuntu
40+governance bodies are ultimately accountable to the Ubuntu Community
41+Council and will arbitrate in any dispute over the conduct of a member
42+of the community.
43+
44+ '''Be considerate.''' Our work will be used by other people, and
45+ we in turn will depend on the work of others. Any decision we take
46+ will affect users and colleagues, and we should take those
47+ consequences into account when making decisions. Ubuntu has
48+ millions of users and thousands of contributors. Even if it's not
49+ obvious at the time, our contributions to Ubuntu will impact the
50+ work of others. For example, changes to code, infrastructure,
51+ policy, documentation, and translations during a release may
52+ negatively impact others' work.
53+
54+ '''Be respectful.''' The Ubuntu community and its members treat
55+ one another with respect. Everyone can make a valuable
56+ contribution to Ubuntu. We may not always agree, but disagreement
57+ is no excuse for poor behaviour and poor manners. We might all
58+ experience some frustration now and then, but we cannot allow that
59+ frustration to turn into a personal attack. It's important to
60+ remember that a community where people feel uncomfortable or
61+ threatened is not a productive one. We expect members of the
62+ Ubuntu community to be respectful when dealing with other
63+ contributors as well as with people outside the Ubuntu project and
64+ with users of Ubuntu.
65+
66+ '''Be collaborative.''' Collaboration is central to Ubuntu and to
67+ the larger free software community. This collaboration involves
68+ individuals working with others in teams within Ubuntu, teams
69+ working with each other within Ubuntu, and individuals and teams
70+ within Ubuntu working with other projects outside. This
71+ collaboration reduces redundancy, and improves the quality of our
72+ work. Internally and externally, we should always be open to
73+ collaboration. Wherever possible, we should work closely with
74+ upstream projects and others in the free software community to
75+ coordinate our technical, advocacy, documentation, and other work.
76+ Our work should be done transparently and we should involve as
77+ many interested parties as early as possible. If we decide to
78+ take a different approach than others, we will let them know early,
79+ document our work and inform others regularly of our progress.
80+
81+ '''When we disagree, we consult others.''' Disagreements, both
82+ social and technical, happen all the time and the Ubuntu
83+ community is no exception. It is important that we resolve
84+ disagreements and differing views constructively and with the help
85+ of the community and community processes. We have the Technical
86+ Board, the Community Council, and a series of other governance
87+ bodies which help to decide the right course for Ubuntu. There are
88+ also several Project Teams and Team Leaders, who may be able to
89+ help us figure out the best direction for Ubuntu. When our goals
90+ differ dramatically, we encourage the creation of alternative sets of
91+ packages, or derivative distributions, using the Ubuntu Package
92+ Management framework, so that the community can test new ideas and
93+ contribute to the discussion.
94+
95+ '''When we are unsure, we ask for help.''' Nobody knows
96+ everything, and nobody is expected to be perfect in the Ubuntu
97+ community. Asking questions avoids many problems down the road,
98+ and so questions are encouraged. Those who are asked questions should
99+ be responsive and helpful. However, when asking a question, care must
100+ be taken to do so in an appropriate forum.
101+
102+ '''Step down considerately.''' Members of every project come and
103+ go and Ubuntu is no different. When somebody leaves or disengages
104+ from the project, in whole or in part, we ask that they do so in a
105+ way that minimises disruption to the project. This means they
106+ should tell people they are leaving and take the proper steps to
107+ ensure that others can pick up where they left off.
108+
109+We pride ourselves on building a productive, happy and agile community
110+that can welcome new ideas in a complex field, and foster collaboration
111+between groups with very different needs, interests and goals. We hold
112+our leaders to an even higher standard, in the Leadership Code of
113+Conduct, and arrange the governance of the community to ensure that
114+issues can be raised with leaders who are engaged, interested and
115+competent to help resolve them.
116+
117
118=== modified file 'lib/lp/registry/model/codeofconduct.py'
119--- lib/lp/registry/model/codeofconduct.py 2009-07-17 18:46:25 +0000
120+++ lib/lp/registry/model/codeofconduct.py 2009-12-02 15:33:16 +0000
121@@ -47,7 +47,7 @@
122
123 path = 'lib/lp/registry/codesofconduct/'
124 prefix = 'Ubuntu Code of Conduct - '
125- currentrelease = '1.0.1'
126+ currentrelease = '1.1'
127 # Set the datereleased to the date that 1.0 CoC was released,
128 # preserving everyone's Ubuntu Code of Conduct signatory status.
129 # https://launchpad.net/products/launchpad/+bug/48995
130
131=== modified file 'lib/lp/registry/stories/gpg-coc/02-signcoc.txt'
132--- lib/lp/registry/stories/gpg-coc/02-signcoc.txt 2009-09-18 15:24:30 +0000
133+++ lib/lp/registry/stories/gpg-coc/02-signcoc.txt 2009-12-02 15:33:16 +0000
134@@ -34,7 +34,7 @@
135 Sample Person tries unsuccessfully to register a truncated code of conduct.
136
137 >>> truncated_coc = read_file('truncated_coc.asc')
138- >>> browser.open('http://launchpad.dev/codeofconduct/1.0.1/+sign')
139+ >>> browser.open('http://launchpad.dev/codeofconduct/1.1/+sign')
140 >>> browser.getControl('Signed Code').value = truncated_coc
141 >>> browser.getControl('Continue').click()
142 >>> print_errors(browser.contents)
143@@ -59,11 +59,11 @@
144 >>> browser.open('http://launchpad.dev/codeofconduct/1.0/+sign')
145 >>> browser.getLink('the current version').click()
146 >>> print browser.url
147- http://launchpad.dev/codeofconduct/1.0.1
148+ http://launchpad.dev/codeofconduct/1.1
149
150 >>> browser.getLink('Sign it').click()
151 >>> print browser.url
152- http://launchpad.dev/codeofconduct/1.0.1/+sign
153+ http://launchpad.dev/codeofconduct/1.1/+sign
154
155
156 Code of Conduct registration
157@@ -73,7 +73,7 @@
158 has leading spaces removed. This succeeds because the words the same and
159 appear in the same order.
160
161- >>> reformatted_coc = read_file('reformatted_101_coc.asc')
162+ >>> reformatted_coc = read_file('reformatted_11_coc.asc')
163 >>> browser.getControl('Signed Code').value = reformatted_coc
164 >>> browser.getControl('Continue').click()
165 >>> print browser.url
166
167=== modified file 'lib/lp/registry/stories/gpg-coc/99-coc-presentation.txt'
168--- lib/lp/registry/stories/gpg-coc/99-coc-presentation.txt 2009-08-18 17:25:41 +0000
169+++ lib/lp/registry/stories/gpg-coc/99-coc-presentation.txt 2009-12-02 15:33:16 +0000
170@@ -36,11 +36,11 @@
171 >>> browser.open('http://localhost:9000/codeofconduct')
172 >>> browser.getLink('current version').click()
173
174- >>> 'Ubuntu Code of Conduct - 1.0.1' in browser.contents
175+ >>> 'Ubuntu Code of Conduct - 1.1' in browser.contents
176 True
177
178 >>> browser.getLink('Sign it').url
179- 'http://localhost:9000/codeofconduct/1.0.1/+sign'
180+ 'http://localhost:9000/codeofconduct/1.1/+sign'
181
182 >>> browser.getLink('Download this version').url
183- 'http://localhost:9000/codeofconduct/1.0.1/+download'
184+ 'http://localhost:9000/codeofconduct/1.1/+download'
185
186=== renamed file 'lib/lp/registry/stories/gpg-coc/reformatted_101_coc.asc' => 'lib/lp/registry/stories/gpg-coc/reformatted_11_coc.asc'
187--- lib/lp/registry/stories/gpg-coc/reformatted_101_coc.asc 2006-05-25 21:18:24 +0000
188+++ lib/lp/registry/stories/gpg-coc/reformatted_11_coc.asc 2009-12-02 15:33:16 +0000
189@@ -1,89 +1,92 @@
190 -----BEGIN PGP SIGNED MESSAGE-----
191 Hash: SHA1
192
193-= Ubuntu Code of Conduct =
194+= Ubuntu Code of Conduct v1.1 =
195
196-This Code of Conduct covers your behaviour as a member of the Ubuntu
197+This Code of Conduct covers our behaviour as members of the Ubuntu
198 Community, in any forum, mailing list, wiki, web site, IRC channel,
199-install-fest, public meeting or private correspondence. The Ubuntu
200-Community Council will arbitrate in any dispute over the conduct of a
201-member of the community.
202-
203-'''Be considerate.''' Your work will be used by other people,
204-and you in turn will depend on the work of others. Any decision
205-you take will affect users and colleagues, and we expect you to
206-take those consequences into account when making decisions. For
207-example, when we are in a feature freeze, please don't upload
208-dramatically new versions of critical system software, as other
209-people will be testing the frozen system and will not be
210-expecting big changes.
211-
212-'''Be respectful.''' The Ubuntu community and its members treat
213-one another with respect. Everyone can make a valuable
214-contribution to Ubuntu. We may not always agree, but
215-disagreement is no excuse for poor behaviour and poor
216-manners. We might all experience some frustration now and then,
217-but we cannot allow that frustration to turn into a personal
218-attack. It's important to remember that a community where people
219-feel uncomfortable or threatened is not a productive one. We
220-expect members of the Ubuntu community to be respectful when
221-dealing with other contributors as well as with people outside
222-the Ubuntu project and with users of Ubuntu.
223-
224-'''Be collaborative.''' Ubuntu and Free Software are about
225-collaboration and working together. Collaboration reduces
226-redundancy of work done in the Free Software world, and improves
227-the quality of the software produced. You should aim to
228-collaborate with other Ubuntu maintainers, as well as with the
229-upstream community that is interested in the work you do. Your
230-work should be done transparently and patches from Ubuntu should
231-be given back to the community when they are made, not just when
232-the distribution releases. If you wish to work on new code for
233-existing upstream projects, at least keep those projects
234-informed of your ideas and progress. It may not be possible to
235-get consensus from upstream or even from your colleagues about
236-the correct implementation of an idea, so don't feel obliged to
237-have that agreement before you begin, but at least keep the
238-outside world informed of your work, and publish your work in a
239-way that allows outsiders to test, discuss and contribute to
240-your efforts.
241-
242-'''When you disagree,''' consult others. Disagreements, both
243-political and technical, happen all the time and the Ubuntu
244-community is no exception. The important goal is not to avoid
245-disagreements or differing views but to resolve them
246-constructively. You should turn to the community and to the
247-community process to seek advice and to resolve
248-disagreements. We have the Technical Board and the Community
249-Council, both of which will help to decide the right course for
250-Ubuntu. There are also several Project Teams and Team Leaders,
251-who may be able to help you figure out which direction will be
252-most acceptable. If you really want to go a different way, then
253-we encourage you to make a derivative distribution or
254-alternative set of packages available using the Ubuntu Package
255-Management framework, so that the community can try out your
256-changes and ideas for itself and contribute to the discussion.
257-
258-'''When you are unsure,''' ask for help. Nobody knows
259-everything, and nobody is expected to be perfect in the Ubuntu
260-community (except of course the SABDFL). Asking questions avoids
261-many problems down the road, and so questions are
262-encouraged. Those who are asked should be responsive and
263-helpful. However, when asking a question, care must be taken to
264-do so in an appropriate forum. Off-topic questions, such as
265-requests for help on a development mailing list, detract from
266-productive discussion.
267-
268-'''Step down considerately.''' Developers on every project come
269-and go and Ubuntu is no different. When you leave or disengage
270-from the project, in whole or in part, we ask that you do so in
271-a way that minimises disruption to the project. This means you
272-should tell people you are leaving and take the proper steps to
273-ensure that others can pick up where you leave off.
274+install-fest, public meeting or private correspondence. Ubuntu
275+governance bodies are ultimately accountable to the Ubuntu Community
276+Council and will arbitrate in any dispute over the conduct of a member
277+of the community.
278+
279+ '''Be considerate.''' Our work will be used by other people, and
280+ we in turn will depend on the work of others. Any decision we take
281+ will affect users and colleagues, and we should take those
282+ consequences into account when making decisions. Ubuntu has
283+ millions of users and thousands of contributors. Even if it's not
284+ obvious at the time, our contributions to Ubuntu will impact the
285+ work of others. For example, changes to code, infrastructure,
286+ policy, documentation, and translations during a release may
287+ negatively impact others' work.
288+
289+ '''Be respectful.''' The Ubuntu community and its members treat
290+ one another with respect. Everyone can make a valuable
291+ contribution to Ubuntu. We may not always agree, but disagreement
292+ is no excuse for poor behaviour and poor manners. We might all
293+ experience some frustration now and then, but we cannot allow that
294+ frustration to turn into a personal attack. It's important to
295+ remember that a community where people feel uncomfortable or
296+ threatened is not a productive one. We expect members of the
297+ Ubuntu community to be respectful when dealing with other
298+ contributors as well as with people outside the Ubuntu project and
299+ with users of Ubuntu.
300+
301+ '''Be collaborative.''' Collaboration is central to Ubuntu and to
302+ the larger free software community. This collaboration involves
303+ individuals working with others in teams within Ubuntu, teams
304+ working with each other within Ubuntu, and individuals and teams
305+ within Ubuntu working with other projects outside. This
306+ collaboration reduces redundancy, and improves the quality of our
307+ work. Internally and externally, we should always be open to
308+ collaboration. Wherever possible, we should work closely with
309+ upstream projects and others in the free software community to
310+ coordinate our technical, advocacy, documentation, and other work.
311+ Our work should be done transparently and we should involve as
312+ many interested parties as early as possible. If we decide to
313+ take a different approach than others, we will let them know early,
314+ document our work and inform others regularly of our progress.
315+
316+ '''When we disagree, we consult others.''' Disagreements, both
317+ social and technical, happen all the time and the Ubuntu
318+ community is no exception. It is important that we resolve
319+ disagreements and differing views constructively and with the help
320+ of the community and community processes. We have the Technical
321+ Board, the Community Council, and a series of other governance
322+ bodies which help to decide the right course for Ubuntu. There are
323+ also several Project Teams and Team Leaders, who may be able to
324+ help us figure out the best direction for Ubuntu. When our goals
325+ differ dramatically, we encourage the creation of alternative sets of
326+ packages, or derivative distributions, using the Ubuntu Package
327+ Management framework, so that the community can test new ideas and
328+ contribute to the discussion.
329+
330+ '''When we are unsure, we ask for help.''' Nobody knows
331+ everything, and nobody is expected to be perfect in the Ubuntu
332+ community. Asking questions avoids many problems down the road,
333+ and so questions are encouraged. Those who are asked questions should
334+ be responsive and helpful. However, when asking a question, care must
335+ be taken to do so in an appropriate forum.
336+
337+ '''Step down considerately.''' Members of every project come and
338+ go and Ubuntu is no different. When somebody leaves or disengages
339+ from the project, in whole or in part, we ask that they do so in a
340+ way that minimises disruption to the project. This means they
341+ should tell people they are leaving and take the proper steps to
342+ ensure that others can pick up where they left off.
343+
344+We pride ourselves on building a productive, happy and agile community
345+that can welcome new ideas in a complex field, and foster collaboration
346+between groups with very different needs, interests and goals. We hold
347+our leaders to an even higher standard, in the Leadership Code of
348+Conduct, and arrange the governance of the community to ensure that
349+issues can be raised with leaders who are engaged, interested and
350+competent to help resolve them.
351+
352 -----BEGIN PGP SIGNATURE-----
353-Version: GnuPG v1.4.1 (GNU/Linux)
354+Version: GnuPG v1.4.9 (GNU/Linux)
355
356-iD8DBQFEaldO2yWXVgK6XvYRAocHAKCFr7NSD6jwe5PmUW9I0vM5lWzC2QCgktT7
357-1V1PJfbYB/TVw20v/EjJhNw=
358-=i+mH
359+iEYEARECAAYFAksVcI0ACgkQ2yWXVgK6XvbgDACgqN25IVdVInlqyQ1GWTh32/QT
360+wDAAn2VGsn4WxJvnCf6738f2aWPqZ4aK
361+=3I88
362 -----END PGP SIGNATURE-----
363
364=== modified file 'utilities/migrater/file-ownership.txt'
365--- utilities/migrater/file-ownership.txt 2009-09-17 17:29:33 +0000
366+++ utilities/migrater/file-ownership.txt 2009-12-02 15:33:16 +0000
367@@ -1771,6 +1771,7 @@
368 ./emailtemplates/upload-rejection.txt
369 ./emailtemplates/bug-notification-verbose.txt
370 reg ./codesofconduct
371+reg ./codesofconduct/1.1.txt
372 reg ./codesofconduct/1.0.1.txt
373 reg ./codesofconduct/1.0.txt
374 reg ./codesofconduct/README
375@@ -2875,7 +2876,7 @@
376 reg ./pagetests/gpg-coc/97-cocnotfound.txt
377 reg ./pagetests/gpg-coc/98-cocacknowledge.txt
378 reg ./pagetests/gpg-coc/99-coc-presentation.txt
379-reg ./pagetests/gpg-coc/reformatted_101_coc.asc
380+reg ./pagetests/gpg-coc/reformatted_11_coc.asc
381 reg ./pagetests/gpg-coc/truncated_coc.asc
382 bug ./pagetests/guided-filebug
383 bug ./pagetests/guided-filebug/xx-advanced-filebug-tags.txt

Subscribers

People subscribed via source and target branches

to status/vote changes: