CUNY Academic Commons

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.

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?

Bumping to our next major release, pending conversation about policy and language.

I've disabled BuddyPress group integration from the license plugin for 1.14.

Bumping the ticket to 1.15 due to Matt's previous comment. Feel free to readjust if needed.

Bumping this to 1.16 since the group creation flow is already set in the main #10987 ticket for 1.15.

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.

Maybe we can tie this in with the related work in #16335.