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

Cleaning up description of GNU GPL in the index.html and changing the note in the gplv2 and gplv3 license pages #177

Closed
wants to merge 5 commits into from

Conversation

joshuagay
Copy link

@joshuagay joshuagay commented Jan 9, 2014

I made some minor changes to how the GNU GPL is described in the index.html page as well a change to the note on the GPLv2 and GPLv3 license pages stating that all source code files should state their copyright and licensing terms, which I think could make sense for all other licensing pages as well.

@@ -42,7 +42,7 @@
<h3>I care about sharing improvements.</h3>
</a>
<p>
The GPL (<a href="licenses/gpl-v2">V2</a> or <a href="licenses/gpl-v3">V3</a>) is a copyleft license that requires anyone who distributes your code or a derivative work to make the source available under the same terms. V3 is similar to V2, but further restricts use in hardware that forbids software alterations.
The GNU GPL (<a href="licenses/gpl-v2">v2</a> or <a href="licenses/gpl-v3">v3</a>) is a copyleft license that protects free code from being turned into proprietary software. Version 3 is international and protects better against DRM, lockdown and patents; it's compatible with Apache 2.0.
Copy link
Contributor

@benbalter benbalter Jun 16, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are you trying to solve for here?

a copyleft license that protects free code from being turned into proprietary software

This gives the user less context then they currently get. It's describing the philosophy, not the practical implications for me as a consumer or a publisher.

protects better against DRM

DRM is jargon. The target audience should be a non-technical user.

it's compatible with Apache 2.0.

Why is that vital to include on the home page? What's license compatibility? What's Apache 2.0?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the first sentence is actually clearer in the pull request than the original. The original says it requires you to distribute the code under the same terms but doesn't describe the terms. There's probably a better phrasing than "protects free code from being turned into proprietary software" but at least it says something.

@josinalvo
Copy link

josinalvo commented Apr 28, 2015

I found this explanation still a bit technical. Care to look at #260 ?

@bkeepers
Copy link
Contributor

bkeepers commented Sep 20, 2015

This gives the user less context then they currently get.

I agree with @benbalter here. I'm not sure this helps clarify anything.

@joshuagay I'm going to close this pull requests since it's stale, but I'm happy to reopen it and continue the conversation here if you are interested.

@bkeepers bkeepers closed this Sep 20, 2015
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.

None yet

5 participants