Skip to content
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

make license visible in main project page #118

Closed
wants to merge 0 commits into from

Conversation

mi-hol
Copy link
Contributor

@mi-hol mi-hol commented Jun 13, 2023

No description provided.

@mck1117
Copy link
Collaborator

mck1117 commented Jun 13, 2023

why does this require a rewrite of the whole file?

@mi-hol
Copy link
Contributor Author

mi-hol commented Jun 13, 2023

Due to copyright terms in GPL3 doc
"Version 3, 29 June 2007

Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this license
document, but changing it is not allowed."

@nmschulte
Copy link
Contributor

nmschulte commented Jun 13, 2023

Isn't the name LICENSE the typical place to find it?

Also, GNU provides the license in different formats: https://www.gnu.org/licenses/#GPL

I agree though, to add language to LICENSE is not the best way to clarify the added notes.

@mck1117
Copy link
Collaborator

mck1117 commented Jun 13, 2023

supplemental terms are allowed, and do not constitute "changing" the license.

image

http://www.mmmtechlaw.com/wp-content/uploads/2014/03/PLI-Open-Source-2014-Extra-provisions-of-FSF-licenses.pdf

@mi-hol
Copy link
Contributor Author

mi-hol commented Jun 13, 2023

good points, though my main intent was to "make license visible in main project page".
image

Any suggestions on: How can we achieve this goal and achieve your goals in combination?

@mck1117
Copy link
Collaborator

mck1117 commented Jun 22, 2023

good points, though my main intent was to "make license visible in main project page".

can you test what happens if you move the "extra" stuff to the end of the license, instead of the beginning? then does github recognize it?

@mi-hol
Copy link
Contributor Author

mi-hol commented Jun 22, 2023

can you test what happens if you move the "extra" stuff to the end of the license, instead of the beginning? then does github recognize it?

It seems a bit more complex because:

  1. GPL-3 license terms state:

    "If you add terms to a covered work in accord with this section, you must place, in
    the relevant source files, a statement of the additional terms that apply to those
    files, or a notice indicating where to find the applicable terms."

  2. combined with the "no change of license" as quoted above

  3. a bit of reading in GH documentation about the license parser

Therefore it seems RE's approach to add terms directly into LICENSE.md is NOT compliant with GPL-3 terms

What is your conclusion?

@mi-hol
Copy link
Contributor Author

mi-hol commented Jul 7, 2023

@mck1117 may I kindly ask for a reaction/comment?

@mi-hol mi-hol closed this Jul 17, 2023
@mi-hol mi-hol force-pushed the master branch 2 times, most recently from 17d4e23 to e493d9a Compare July 17, 2023 09:59
@nmschulte
Copy link
Contributor

good points, though my main intent was to "make license visible in main project page".

ah, I understand better now.

I see you closed this; what was the resolution?

@mi-hol
Copy link
Contributor Author

mi-hol commented Jul 20, 2023

@nmschulte this is neither a reaction from Matt nor a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants