3 ms·

Recently in my projects I've gone to AGPL with a linking exception for unmodified versions. For me I think it's the right balance between freedom for users and

by logn 11y ago

Recently in my projects I've gone to AGPL with a linking exception for unmodified versions. For me I think it's the right balance between freedom for users and freedom for developers (while they may be making proprietary software based on libre software, they're encouraged by the license terms to help sustain the the main project). (edited)

mark_l_watson 11y ago
That sounds good. If you don't mind, please share how you worded that, or some other reference.
- deleted 11y ago
  [deleted]
- logn 11y ago
  It's basically the GNU Classpath wording, but I had to modify it slightly to achieve my goals [1]. Part of the wording about the objective (the first sentence) was shamelessly borrowed from the Mattermost project [2]. GNU Classpath is more permissive in that its exception applies to modified versions too [3]. [1] https://github.com/MachinePublishers/jBrowserDriver/blob/master/LICENSE https://github.com/MachinePublishers/jBrowserDriver/blob/mas... [2] https://github.com/mattermost/platform/blob/master/LICENSE.txt https://github.com/mattermost/platform/blob/master/LICENSE.t... [3] https://www.gnu.org/software/classpath/license.html https://www.gnu.org/software/classpath/license.html
  - wahnfrieden 11y ago
    Keep in mind the custom wording will make it harder for some companies to use your code, since accepting additional licenses can require lawyer approval. This adds value to choosing one of the common licenses over crafting a similar fork.
    - kijin 11y ago
      LGPL was intended to be a standardization of "GPL with the Classpath exception". Perhaps we need a similar license for "AGPL with the Classpath exception". Maybe call it LAGPL or something.
      - DannyBee 11y ago
        LGPL predates the classpath exception by quite a while, and doesn't serve the same purpose at all. The classpath exception is intended to cause the target software to not have a license change just because it used a certain runtime library (classpath). The LGPL has different aims entirely (around allowing library components for software). Essentially, the classpath exception was written for programming language runtime libraries (and is thus the basis of what later became the gcc runtime library exception). The LGPL was written for random library software, and started out much earlier than the classpath exception (by a decade or two).
deleted 11y ago
[deleted]
deleted 11y ago
[deleted]
deleted 11y ago
[deleted]

by logn 11y ago

mark_l_watson 11y ago

That sounds good. If you don't mind, please share how you worded that, or some other reference.

deleted 11y ago
[deleted]
logn 11y ago
It's basically the GNU Classpath wording, but I had to modify it slightly to achieve my goals [1]. Part of the wording about the objective (the first sentence) was shamelessly borrowed from the Mattermost project [2]. GNU Classpath is more permissive in that its exception applies to modified versions too [3]. [1] https://github.com/MachinePublishers/jBrowserDriver/blob/master/LICENSE https://github.com/MachinePublishers/jBrowserDriver/blob/mas... [2] https://github.com/mattermost/platform/blob/master/LICENSE.txt https://github.com/mattermost/platform/blob/master/LICENSE.t... [3] https://www.gnu.org/software/classpath/license.html https://www.gnu.org/software/classpath/license.html
- wahnfrieden 11y ago
  Keep in mind the custom wording will make it harder for some companies to use your code, since accepting additional licenses can require lawyer approval. This adds value to choosing one of the common licenses over crafting a similar fork.
  - kijin 11y ago
    LGPL was intended to be a standardization of "GPL with the Classpath exception". Perhaps we need a similar license for "AGPL with the Classpath exception". Maybe call it LAGPL or something.
    - DannyBee 11y ago
      LGPL predates the classpath exception by quite a while, and doesn't serve the same purpose at all. The classpath exception is intended to cause the target software to not have a license change just because it used a certain runtime library (classpath). The LGPL has different aims entirely (around allowing library components for software). Essentially, the classpath exception was written for programming language runtime libraries (and is thus the basis of what later became the gcc runtime library exception). The LGPL was written for random library software, and started out much earlier than the classpath exception (by a decade or two).

deleted 11y ago

[deleted]

deleted 11y ago

[deleted]

deleted 11y ago

[deleted]