Opened 15 years ago
Last modified 15 years ago
#2 closed defect (FIXED)
Add appropriate copyright headers to all files / adjust COPYING
| Reported by: | Christopher Allan Webber | Owned by: | Will Kahn-Greene |
|---|---|---|---|
| Priority: | major | Milestone: | 0.0.1 |
| Component: | Keywords: | ||
| Cc: | Parent Tickets: |
Description
Add / adjust copyright headers on all files.
- Python files already have appropriate AGPL header, except need adjustment to provide exception for HTML (maybe also CSS for the sake of clarity?) files. See: http://www.gnu.org/licenses/gpl-faq.html#WMS though we will probably need to make some adjustments to that.
- HTML templates should contain CC0 header. See: http://wiki.creativecommons.org/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F
- Move COPYING to AGPLv3.txt
- Download CC0_1.0.txt:http://creativecommons.org/publicdomain/zero/1.0/legalcode.txt
- Create a new COPYING which describes that python code is under AGPLv3 (AGPLv3.txt) w/ exception for HTML templates, Javascript under AGPLv3 w/ exception for HTML, and HTML templates / images / CSS of base theme all under CC0 (CC0_1.0.txt)
If we end up having CSS files by the time this is written we should also add headers to these, but do this in the style listed at the bottom of this post: https://creativecommons.org/weblog/entry/27094
Change History (6)
comment:1 by , 15 years ago
| Owner: | set to |
|---|
comment:2 by , 15 years ago
willkg: okay. Could you also run it the "exception" stuff by brett smith / reply to the mailing list to make sure that we've got it right when done? [09:26] and appreciated paroneayea: can you toss that additional action item in in the bug? yeah sure
;)
comment:3 by , 15 years ago
Here's an update.
- We're waiting for an email from Brett with his thoughts on the text we're using.
- The documentation (everything under docs/) will be under a CC0 license including code snippets, templates, and static assets.
- When we add branding assets to the repository for both the software and the documentation, we'll license them differently--but we're kicking that can down the road until it's an issue.
I have a lot of this work sitting on my computer. When things get resolved, I'll check it all in.
Note:
See TracTickets
for help on using tickets.
Grabbing this one so I can mess everything real good! Muah ha ha ha ha!