Skip to content

GPLv3 license may not be appropriate for a plugin #4

@jcttrll

Description

@jcttrll

Unfortunately, after experimenting with your plugin (which is cool and works great for us!), we noticed it's GPLv3. We would like to use it in a proprietary system, but that obviously isn't possible with this license, which is sad.

At the bottom of the GPLv3 license, there's a little blurb that seems kind of applicable:

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.

Would you be open to the idea of licensing your plugin under LGPL (or MIT or Apache, if you're familiar with those), instead of (or in addition to) GPLv3? That way, more people could use it. We're very much pro-Open-Source at our company and we like to contribute back to projects we use (I have a very small PR open with your plugin right now, actually), but we just can't use something if it's GPLv3.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions