You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest removing the footer for CC for any page linking to archival material and adding a note about the ownership. Legally speaking, we need to ask permission to reproduce most of these stuff, but if we make the clear distinction on where CC ends and copyrighted stuff starts, then we could benefit from fair use rules (although with large verbatim reproduction we are going to fail test 3).
The bottom line is as long as the curators and maintainers of this archive are very clear about the intent and scope, then it is okay until someone complains.
I can own this effort if we are in agreement.
The text was updated successfully, but these errors were encountered:
So far, I've put credits, intent, and copyright notice in the README file the folder containing archival files.
The CC footer is very generic, only applied to the content pages auto-generated for the website, which are almost all CC anyway. I think we need some kind of copyright notice under these pages anyway, but agree that we can be more clear about the non-CC parts.
Anyways, any improvements/updates are appreciated. Just submit a PR as you see fit best and we can discuss about the details there.
I suggest removing the footer for CC for any page linking to archival material and adding a note about the ownership. Legally speaking, we need to ask permission to reproduce most of these stuff, but if we make the clear distinction on where CC ends and copyrighted stuff starts, then we could benefit from fair use rules (although with large verbatim reproduction we are going to fail test 3).
The bottom line is as long as the curators and maintainers of this archive are very clear about the intent and scope, then it is okay until someone complains.
I can own this effort if we are in agreement.
The text was updated successfully, but these errors were encountered: