Bug #20782
openTerms of Service, Mission, Privacy Policy review and update
0%
Description
These three footer links haven't been updated in many years. We have a compilation of their current content and some initial comments here:
https://docs.google.com/document/d/1mg5q4_DvJ2ej-RTbBSWSoPcJBucFUwqm-GchR9ShL70/edit
We need to incorporate the current feedback and any new thoughts, then probably contact legal counsel in some way to lock this all down before finalizing.
I'm also going to make this a related task of #16335 because of the parallels with all of our work regarding licensing, Creative Commons, etc.
Related issues
Updated by Colin McDonald over 1 year ago
- Related to Feature #16335: Revisiting options and functions of Creative Commons license widget added
Updated by Colin McDonald about 1 month ago
Just updating here what we've been talking about in recent monthly and weekly team meeting to pick these revisions back up and implement them.
Thanks to Zach for making a run through the old comments and adding some great revisions. I've resolved a lot of them in the Google Doc so it is cleaner and easier to read now. I'd encourage anyone who hasn't looked at this in a while to read again and add any fresh thoughts. Here are a couple of things we're still working on:
- What do we say in the "License to CUNY" section b? We have a few suggestions, but this text seems to be boilerplate for a lot of ToSes CUNY-wide. Luke makes the point that we could specify what is a CUNY license generally (if anything) vs. what rights we must retain in order to display the Commons itself. "Each of these licensed alterations are required for the Commons to function (not a license for CUNY to freely adapt, etc)."
- "3. Reporting Violations or Concerns." there is a missing list after "Your notification of infringement must include:" that seems to have gotten inadvertently cut during the initial ToS revisions. We found one old version and pasted it back in. Legal can use it as a baseline for their review. It's a lot of common-sense items in legalese, like including the copyrighted work in question, the allegedly infringing work on the Commons, and contact info.
- How does Creative Commons and #16335 fit into the main ToS?
Once we have this all in a good place, we'll discuss getting this over to CUNY legal and the last steps before pushing it all live. Once we do that, we should probably let the Open Lab know, since their ToS are based on ours and they might want to make similar revisions (they have the same missing takedown language):