Document copyright and licensing in code base
Bug #720283 reported by
Clint Byrum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Medium
|
Clint Byrum |
Bug Description
Other than the debian/copyright file, there is no per-file documentation of the copyright assignment and licensing of the code.
I would suggest:
- Adding Copyright headers to all non-trivial non-generated files
- Adding a COPYING file to the root which contains the contents of the AGPL (promised by the copyright file but not actually included)
Related branches
lp:~clint-fewbar/pyjuju/remove-debian-dir
- Gustavo Niemeyer: Needs Fixing
- Kapil Thangavelu (community): Approve
- William Reade (community): Approve
-
Diff: 839 lines (+682/-104)10 files modifiedCOPYING (+661/-0)
README (+21/-0)
debian/changelog (+0/-51)
debian/compat (+0/-1)
debian/control (+0/-17)
debian/copyright (+0/-28)
debian/ensemble.docs (+0/-1)
debian/install (+0/-1)
debian/pycompat (+0/-1)
debian/rules (+0/-4)
Changed in ensemble: | |
milestone: | none → budapest |
Changed in ensemble: | |
milestone: | budapest → dublin |
Changed in ensemble: | |
importance: | Undecided → Medium |
Changed in ensemble: | |
milestone: | dublin → none |
Changed in juju: | |
assignee: | nobody → Clint Byrum (clint-fewbar) |
milestone: | none → florence |
status: | New → Fix Released |
To post a comment you must log in.
When we did this for Landscape we got some advice from Andrew Sinclair
(a member of Canonical's legal department) and he gave us some exact
wording to use. You should probably talk to him to make sure that
whatever gets put in place passes legal muster.