Need to support Ubuntu CoC 1.1
Bug #479870 reported by
William Grant
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Daniel Holbach |
Bug Description
Version 1.1 of the Ubuntu Code of Conduct was blessed on 2009-10-20. Launchpad should probably grow support for it pretty quickly.
See http://
Related branches
lp://qastaging/~dholbach/launchpad/coc-1.1
- Curtis Hovey (community): Approve (code)
-
Diff: 383 lines (+180/-94)8 files modifiedlib/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)
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is not an issue that the launchpad team is working on, but in the course of the discussion, I concluded that the basic requirements can be done with little work. registry/ codesofconduct model.codeofcon duct.CodeOfCond uctConf
1) Add the new 1.1.txt to lib/lp/
2) Update lp.registry.
a) set currentrelease to 1.1
b) set datereleased to the current new date.
Since Person. is_ubuntu_ coc_signer looks for the CoC that is signed after the datereleased, all users no longer be listed as signers of the current CoC. Users can sign the new one. Note that by not changing the datereleased, the old CoC is considered to be compatible with the new CoC, that is what was done for the 1.0 and 1.0.1 CoCs