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

macchanger 1.6.0 lost copying information #3

Closed
thoger opened this issue Apr 12, 2013 · 6 comments
Closed

macchanger 1.6.0 lost copying information #3

thoger opened this issue Apr 12, 2013 · 6 comments
Assignees

Comments

@thoger
Copy link
Contributor

thoger commented Apr 12, 2013

macchanger update form 1.5.0 to 1.6.0 removes COPYING file that contains licensing information. There's also no license information in the README, so one has to look into all source to find out.

Both GNU and downstream vendor packaging guidelines strongly encourage inclusion of the license text:

http://www.gnu.org/prep/standards/html_node/Releases.html
http://fedoraproject.org/wiki/Packaging:LicensingGuidelines#License_Text

Please consider mentioning license in the README explicitly, in addition to re-adding COPYING, given that current license is GPLv2 or later.

@alobbs
Copy link
Owner

alobbs commented Apr 18, 2013

That was unintentional. macchanger 1.7.0 ought to ship the COPYING file again.

@alobbs
Copy link
Owner

alobbs commented Jan 1, 2014

f4f66e1 fixed it.

@alobbs alobbs closed this as completed Jan 1, 2014
@thoger
Copy link
Contributor Author

thoger commented Jan 1, 2014

The commits adds GPL 3 text to COPYING, while all source files keep saying GPL 2 or later. Is this intentional re-license to be GPL 3+?

@ghost ghost assigned alobbs Jan 1, 2014
@alobbs
Copy link
Owner

alobbs commented Jan 3, 2014

Yes, it is, indeed. GNU MAC Changer should be distributed under the GPLv3+ from now on.

@thoger
Copy link
Contributor Author

thoger commented Jan 7, 2014

Thank you for the clarification!

@dpaleino
Copy link

dpaleino commented Feb 1, 2014

It would be best if this was fixed in the source files too ;)

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

No branches or pull requests

3 participants