make licensing info clear during group creation
as discussed during the CAC -- we should make the CC license explicit during group creation
Updated by Boone Gorges almost 7 years ago
- Status changed from Assigned to Reporter Feedback
- Target version set to 1.11
Matt, can you please provide a bit more detail on the policy? I assume we will want to keep the text shown during group creation minimal, but also provide links to our own stated policy as well as an explanation of whatever CC license we use. Is section 2c of https://commons.gc.cuny.edu/about/tos/ the canonical text? If so, a couple questions/thoughts:
- The text says "You may offer your Content on a more restrictive basis..." and explains how you can opt out of CC licensing, but CC-BY-SA-NC is quite restrictive as far as CC licenses go.
- If this policy applies to group members, the language should probably be updated to reflect the fact that there's no obvious opt-out tool for content posted in groups. (Even for group admins, there's no policy, but in any case it seems to me that it doesn't really hold water for the group admin to decide on a license for group members. This might be worth talking to Joe about.)
Also, if there are any suggestions from Matt or anyone else about where this language goes and what it looks like, feel free to provide it. I can do something myself and post it here for feedback, but it might save a bit of work if I got it right the first time.
Updated by Matt Gold almost 7 years ago
- Assignee changed from Boone Gorges to Megan Wacha
Thanks, Boone. I've added Megan to this ticket (as well as Luke and Lisa). Yes, the TOS is the canonical text as far as we have one. I think that "more restrictive," in this case, refers to plain old copyrighted text, though you are right that the differences between that and the NC-BY-SA cc license are not necessarily huge.
It seems to me that this issue needs further conversation before it is ready for technical implementation. We have to decide, first and foremost, what we want to tell users about what they can do and what can happen to their content. We may need to say, in the TOS, that Group Admins have the power to set copyright policy for the groups they administer and that members agree to that policy by joining them. So we may indeed need a conversation with Joe, but we also need conversation within our group regarding this issue.
Megan, is there any possibility that you'd be willing to take the lead on these conversations, working in concert with Luke and Lisa?
Updated by Megan Wacha almost 7 years ago
Hi, All. I agree this issue needs further conversation, and I'm happy to take the lead on this w/ L&L. For me, it's not about being more or less restrictive, but promoting transparency and user choice. There may be instances in which a user does not want the information to be shared or migrated to other platforms (i.e. contributions to private groups) or isn't legally permitted to assign a CC license (i.e. shared files). There are a lot of fun discussions ahead!
I'm new to redmine - would folks prefer to have these conversations here or set a meeting for the new year?
Updated by Raymond Hoh almost 5 years ago
I've updated #9938 to add licensing to the group creation and settings pages:
The comments above from Matt and Maura still need to be addressed.
If we cannot come to some agreement, I can always disable the group license functionality until the necessary licensing questions have been answered.
Updated by Raymond Hoh over 4 years ago
In last month's meeting, we discussed bringing back the Creative Commons license in groups, but only for public groups.
Please review the previous screenshots from comment 11 and let's discuss what needs to happen in order to include this in 1.15.
Updated by Boone Gorges almost 4 years ago
- Assignee changed from Megan Wacha to Raymond Hoh
- Target version changed from 1.16 to 1.17.0
Looks like we missed having the necessary conversations to get this done for 1.16. Reassigning to Ray in hopes that he can bring us up to speed on next steps for the Spring release.