-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
Please clarify under which GPL versions phpsysinfo is licensed (currently ambiguous) #156
Comments
PhpSysInfo is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2. |
@namiltd: I interpret the missing "or any later version" in your comment as "only version 2". You then should adapt the according paragraphs in I suggest to do a Additionally explicitly using e.g. the word "only" in the |
What if I decide to change license to "GPLv2 or any later version"? |
Then you'd change the boilerplate in all files as well as README.md accordingly and re-add the phrase "or (at your option) any later version". I don't see a problem there. :-) (You might want to ask other contributors first before relicensing their contributions, but I assume that's not the issue here.) I don't mind which license you choose. It's also no problem if single files (like e.g. 3rd-party plugins) are licensed under a different license or different GPL version(s). It should just be unambiguous under which license the project in general (i.e. for all files without explicit boilerplate or license declaration) is published as well as for every single file which has different license terms. |
Contents has been standardized. Now PhpSysInfo is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2 or (at your option) any later version. This is clearly defined. |
As mentioned in #120 I use some of the phpsysinfo graphics in another project.
But it is currently unclear if the project as a whole …
It would be nice if this could be unambiguously declared in at least README.md. Thanks!
The text was updated successfully, but these errors were encountered: