Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h1>Be very careful!</h1> <p><p> You'd have to ensure that there are two separate licence click-throughs, one for the GPL v3 code, one for the non-proprietary code. You'd also need to be extremely conscientious in ensuring that users understand their rights with respect to the GPL v3 code, and in demonstrating that you have met your obligations w.r.t making that code available.</p> <p>IANAL. I've not double-checked the wording of GPL v3 to be sure there isn't another gotcha.</p> <p>In case of doubt, consider consulting with the <a href="http://www.softwarefreedom.org/" rel="nofollow noreferrer">SFLC</a> (Software Freedom Law Center).</p> <hr> <h3>Nuances</h3> <p>There's an extensive set of comments below - read it. This note is in part a response to the comments.</p> <p>The GPL is not directly an EULA (end-user licence agreement). It is more of a licence to software developers. However, it does confer on the recipients of software certain rights, and the GPL imposes obligations on you as a software developer. In particular, it requires you as the developer to make clear which rights were granted to you and which rights were granted to those to whom you supply the GPL software.</p> <p>You do not have to display the text of the GPL. You might just say "Package X is distributed under the terms of the GNU General Public License version 3. You can find the terms of this license at <a href="http://www.fsf.org/licensing/licenses/gpl.html" rel="nofollow noreferrer">http://www.fsf.org/licensing/licenses/gpl.html</a>. You have certain rights because of this license. You may obtain the source code for Package X from us by downloading it from [<em>...a suitable URL...</em>]. We provide limited support for Package X when it is used with Package Y. <em>...blah...blah...blah...</em>".</p> <p>One advantage of displaying the GPL itself is that you do not have to provide any interpretation of it - and interpreting legal documents is difficult, especially for non-lawyers (such as me!). You might want to make it clear that the users have the rights and do not have to agree to anything; that is sensible (and I believe accurate).</p> <p>Note that it is legitimate to charge for support of Package X (the hypothetical GPL v3 software) - provided you actually provide support. That is permitted. You are not obliged to provide support to people who obtain Package X from elsewhere, either; you may limit that support to your own customers. But you can't stop your customers from obtaining the source, or from relaying the source for Package X to friends, colleagues, or customers of their own.</p> <p>I'm still not a lawyer - if you need legal advice, be prepared to pay to speak with a lawyer who is experienced with software licencing and the GPL.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload