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
Open Source Licence for Tamarin Manual #33
Comments
Update: the editor who flagged it has now formally requested proof of the open source status, so if it is the case that it's open source, I'd be really grateful for the licence being updated. If it's not, I'll re-write as much of the article as possible. |
Hi Martin,
Thanks for your efforts with this! The manual is under open source
license, particularly BSD-3, visible at https://github.com/tamarin-prover
Also, there is this file which may help:
https://github.com/tamarin-prover/manual/blob/master/LICENCE.highlight.js
Not sure if and what our reasoning was for picking this particular
license and making it hard to find, so I need to hear from the others
first before addressing this.
Cheers,
Ralf
…On 12/30/2017 1:07 PM, Martin Dehnel-Wild wrote:
Update: the editor who flagged it has now formally requested proof of
the open source status, so if it is the case that it's open source,
I'd be really grateful for the licence being updated. If it's not,
I'll re-write as much of the article as possible.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACFoi99tdpo1KAPKDellAEuBCN1EzGgnks5tFiefgaJpZM4RPaCV>.
|
Was the BSD-3 licence a specific choice, or was it inferred by GitHub (correctly or otherwise) due to the inclusion of a BSD-Licensed bit of software in the repo, |
Actually it might be incorrectly inferred, good point! Take a look at
the PDF of the manual, particularly page 2 of:
https://tamarin-prover.github.io/manual/tex/tamarin-manual.pdf
It says:
This written work is licensed under a Creative Commons
Attribution-NonCommercial-ShareAlike 4.0 International License. You
may reproduce and edit this work with attribution for all
non-commercial purposes.
which is in line with what I remembered (i.e., a CC license). This
should be the correct answer, but I am happy to hear from anyone else.
Cheers,
Ralf
…On 12/30/2017 5:53 PM, Martin Dehnel-Wild wrote:
Was the BSD-3 licence a specific choice, or was it inferred by GitHub
(correctly or otherwise) due to the inclusion of a BSD-Licensed bit of
software in the repo, |highlight.js| <https://highlightjs.org/>?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACFoiy_-X2MrktW_zekKMUwuibWDlJ3_ks5tFmqQgaJpZM4RPaCV>.
|
Perfect. Wikipedia may complain as this licence is strictly not compatible with theirs (I think you have to be CC BY-SA rather than CC BY-NC-SA) but this should be enough to get them off my back for now! Could this licence be added to the repo as a separate |
NC is a weird licence for the manual, was that intentional? I'd have
thought commercial use was encouraged...
K
On Sat, 30 Dec 2017, at 5:14 PM, Martin Dehnel-Wild wrote:
Perfect. Wikipedia may complain as this licence is strictly not
compatible with theirs (I think you have to be CC BY-SA rather than CC
BY-NC-SA) but this should be enough to get them off my back for now!
Could this licence be added to the repo as a separate LICENCE file,
and included clearly in the HTML version? Thank you!> — You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub[1], or mute the
thread[2].>
|
CC BY-NC-SA:
I don't think this means people can't use the material if they're a commercial entity, just that they can't modify it and then use the result commercially? @katrielalex: I think the NC wording seems to imply that use by a commercial entity is fine, as long as said entity doesn't try to re-sell the material itself. |
Ok, I'm pleased to note that a wikipedia administrator has removed the 'mark for deletion (copyright violation)' flag, and downgraded it to a 'copypaste warning', i.e. it has been noted that some of the content on this page has been copied and pasted from another source, and that this content may not be compatible with wikipedia's licenses.
This gives us a decent stay of execution on this front. I will spend a bit of free time (when I have it) re-phrasing / writing sections so that it's no longer so close to the manual. I would still really appreciate the licence being written into the HTML version and the source repo formally! (Admittedly less of a hurry now -- I'll submit it as a PR when I get time) Thank you :-) |
Tamarin itself is under a GPL license, which also permits commercial use. Only the manual is limited to non-commercial use to prevent e.g. somebody printing it and selling it as a book. However, in my understanding, a company employee can still read the manual and use Tamarin as part of his work (but I am not a lawyer). |
PR adding licence to HTML version now accepted. |
TL;DR: Could someone pretty please add a formal licence to the manual? :-)(Preferably/hopefully/ideally something like GPLv3 as per the rest of Tamarin).
The Wikipedia page for Tamarin has sadly (erroneously) been marked for deletion due to alleged "copyright violation"; they are correct in pointing out that the wiki article text quotes a couple of paragraphs of the manual verbatim, as I thought it was well written and useful content.
It is my belief that the manual was written and released under an open source licence (same as Tamarin itself, hence the repo being publicly available here on GitHub), and that this use of the text is not a copyright violation. If I can prove that the content is open source, this issue goes away.
To resolve this and any future issues, would it be possible to include a formal
LICENCE
file (preferably licensing it as something like GPLv3, although obviously whatever you think most suitable!) within this public repo, so that I can demonstrate its open source status to the Wikipedia administrators? I really don't want my lovely article to be deleted!Thanks, and hope you've all had a lovely Christmas / holiday period.
Martin
P.S. I assume the
LICENCE.highlight.js
is a licence forhighlight.js
or other such software used to create the manual, and not the the text of the manual as a whole!The text was updated successfully, but these errors were encountered: