Opened 13 years ago
Last modified 4 years ago
#400 accepted enhancement
Media licensing should be human readable
Reported by: | Sacha | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | programming | Keywords: | test, review |
Cc: | Stephen Compall | Parent Tickets: |
Description
When uploading media, the licensing options don't give enough information for most people to make an informed choice.
The current list is:
All rights reserved
CC BY 3.0
CC BY-SA 3.0
CC BY-ND 3.0
CC BY-NC 3.0
CC BY-NC-SA 3.0
CC BY-NC-ND 3.0
CC0 1.0
Public Domain
Propose better options, helptexts, or perhaps a block of text that changes based on your choice.
Change History (27)
comment:1 by , 13 years ago
comment:3 by , 12 years ago
Milestone: | 0.3.0 → 0.3.1 |
---|
comment:4 by , 12 years ago
Owner: | removed |
---|---|
Status: | new → assigned |
comment:5 by , 12 years ago
Component: | component1 → programming |
---|
comment:6 by , 12 years ago
Milestone: | 0.3.1 |
---|
This didn't make it into 0.3.1 as far as I can tell.
If someone wants to work on this for 0.3.2, please assign yourself and set the milestone to 0.3.2.
comment:7 by , 12 years ago
Milestone: | → 0.3.2 |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:9 by , 12 years ago
Owner: | removed |
---|
Taking myself off this, as I don't think I'll be able to work on it anytime soon, and other seem to be working on the related licensing issue.
comment:10 by , 12 years ago
Keywords: | bitesized added |
---|
I'm marking this as bitesized. It shouldn't be difficult to do at all: it's really just adding a few fields to the license list and adding a bit to the templates.
There's some question of whether or not we might change the way this works with a more robust plugin per conversations in #395 but in the meanwhile, this small change would really help us out a lot (and would help figure out how to improve such a plugin also.)
comment:11 by , 12 years ago
Keywords: | bitesized removed |
---|
pythonsnake pointed out that this is *not* bitesized as it might require hacking the wtforms select field to do some magic. removing bitesized tag.
comment:12 by , 12 years ago
Owner: | set to |
---|
comment:13 by , 12 years ago
Milestone: | 0.3.3 → 0.3.4 |
---|
comment:14 by , 12 years ago
Cc: | added |
---|
comment:15 by , 12 years ago
Update: this is done, but I need to update it to work with a recent MediaGoblin version (my hacking instance is a bit out-of-date).
comment:16 by , 11 years ago
Status: | assigned → in_progress |
---|
Hi! I'm moving this ticket from "assigned" to in_progress per our new workflow. Please update the ticket and let us know if you're still working on this. If you are, super great! If not, we'll remove the claim and move it back to "accepted" in a couple of weeks.
Thanks!
comment:17 by , 11 years ago
Owner: | removed |
---|---|
Status: | in_progress → review |
Pushed it here https://github.com/pythonsnake/MediaDwarf/tree/400_license
comment:19 by , 11 years ago
Owner: | set to |
---|---|
Status: | review → in_progress |
I was testing out this code, and it seems to work fine on the submit page, but on the edit_account page, I get the following error:
If you could also rebase it against master in the process, that would be great. Thanks
comment:21 by , 11 years ago
Milestone: | 0.5.0 → 0.6.0 |
---|
comment:22 by , 11 years ago
Milestone: | 0.6.0 → 0.7.0 |
---|
comment:23 by , 11 years ago
Keywords: | test added |
---|
comment:24 by , 10 years ago
Milestone: | 0.7.0 → 0.8.0 |
---|
I'm bumping this to 0.8.0, but if it doesn't really make it in 0.8.0, the milestone should be removed so as to avoid milestone-bump spam.
comment:26 by , 10 years ago
Owner: | removed |
---|---|
Status: | in_progress → accepted |
comment:27 by , 4 years ago
Keywords: | review added |
---|
It would be good after you select a license if there were some sort of textbox beneath it that explained what it meant, or something.