-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License #5
Comments
Yeah I'd like everything in this repository to be CC-4 or something similar. I've personally made all of these traces except for the automerge-perf trace. And I've just added the license tag to the README of the other traces that were missing it. - Except for automerge-perf, which I didn't make so I can't license it. The automerge-perf trace comes from automerge/automerge-perf by @ept. The source text was a paper that is now published, so there's probably some complex copyright around that. Maybe Martin can chime in - are you happy to put your automerge-perf editing trace under a public license of some sort? |
Agree it would be great to license everything CC. I just checked and we did assign the copyright for that article to the IEEE. The relevant part of the copyright assignment reads:
So on the one hand I'm allowed to "authorize others to reproduce the Work", but not "grant third-party requests for re-use". Not sure how to interpret that. We can probably treat the editing trace the same way as a preprint PDF, for which the copyright assignment says:
I think a reasonable interpretation would be that we can license the editing trace CC BY-NC, which would allow the data to be distributed but not sold. As long as we also say "(c) IEEE" somewhere suitable and link to the official publication page, it should be fine. |
Great - I’ll add a comment to that effect. Thanks @ept |
@josephg It seems like this license statement was never added. @ept has now licensed the editing trace under CC BY (see https://github.com/automerge/automerge-perf), so this should now be legally possible. Would you like to add that license statement please? Thanks. |
On further thought I think we can license it CC-BY. No need to make it CC-BY-NC, since I believe the copyright assignment concerns only the final paper, and the editing trace contains a lot more information than the final paper. I've now made this explicit in the automerge-perf repo. |
It is not clear under what license this repo can be used. A number of traces mention CC-4.0, but under other traces there is no mention of a license.
Would it be possible to clarify the license for the entire repo?
The text was updated successfully, but these errors were encountered: