Giter VIP home page Giter VIP logo

Comments (9)

desandro avatar desandro commented on June 15, 2024 5

In short, as the owner of Flickity commercial license, you are okay to use both Flickity and this dependency in both your open and closed source projects.

From a high level, my aim is to allow wide usage of Flickity, but provide some rationale for purchasing a commercial license so I can support development. "Commercial" is in reference to people paying for it, not so much the work they use Flickity for. Technically, the commercial license allows you to use Flickity in closed-source projects. As you own a commercial license, you can include Flickity both in closed and open source projects.

As for the GPL license of this react-flickity-component package: the maintainers have decided to adopt GPL as a way of keeping parity between Flickity. The Flickity commercial license terms do not extend to any dependencies so there is some legal gray area. But from a practical standpoint, I'm okay with this usage, and I feel the maintainers of this package will be okay as well. Thanks for checking.

from react-flickity-component.

andreicek avatar andreicek commented on June 15, 2024 1

from react-flickity-component.

yaodingyd avatar yaodingyd commented on June 15, 2024

Thanks for your concern! Commercial OEM License needs to be "Commercial" first, however this is a open source project. We'll update this project to use GPLv3.

from react-flickity-component.

jack-sf avatar jack-sf commented on June 15, 2024

But then, this library can't be used in a project, which is not GPL, but paid for Flickity commercial support, am I right?

We'd like to use it, but our project is closed source, so we can't use a library with GPL license.

from react-flickity-component.

yaodingyd avatar yaodingyd commented on June 15, 2024

If you get commercial license from the original Flickity project, you are free to use this project in your closed source.

from react-flickity-component.

kierangillen avatar kierangillen commented on June 15, 2024

@yaodingyd @theolampert We really wanted to use this wrapper in our MIT licensed project and we have the commercial Flickity license. However the React Flickity Component explicitly declares GPL3 in the package.json https://github.com/theolampert/react-flickity-component/blob/68feb82d5875e6891a93e5041527a931ed518dd7/package.json#L12 and otherwise only touches on the license in the Readme and in this issue. We are not lawyers but this seems too prone to legal issues without more concrete language in cases using the commercial license. To summarize, we consider our coverage of Flickity to be in accordance with the license but not this package, so we don't feel comfortable using it. Perhaps you could reach out to @desandro, he may have already dealt with similar legal issues and may have some advice on how to properly license it. Thanks for an otherwise perfect package.

from react-flickity-component.

theolampert avatar theolampert commented on June 15, 2024

@kierangillen I'm also not a lawyer and the licensing issue is a bit murky to me. As you said perhaps @desandro could give us a pointer here.

from react-flickity-component.

yaodingyd avatar yaodingyd commented on June 15, 2024

Thanks Dave!So the licensing info for this project is accurate. @kierangillen as long as you have commercial license from Flickity, you can use this project in any projects.

from react-flickity-component.

alloy avatar alloy commented on June 15, 2024

@yaodingyd @desandro I really understand the spirit and sympathise with trying to be pragmatic, but alas that's not something we can do with legalese 😞. As it stands, this package (react-flickity-component) states it is licensed under GPLv3 and then in a few other locations (such as this issue) mentions are made that “it's ok”, but unfortunately that’s most likely too hand-wavey.

While you may never take action against us, it is important to realise that others may still decide to do so–for instance, a nefarious competitor.

Having said that, perhaps your statements are enough, but in reality [if we really want to respect licenses, which we do] we would have to have a lawyer look at this situation and it would probably be hard for them to come to a conclusion, which means their final answer would likely be “don't take any chances”.

FWIW I think you should be able to eg dual license your code under GPLv3 or MIT, just be sure to inform users that they can only use the MIT license if they have a commercial Flickity license. But then again… IANAL 🤷‍♂

from react-flickity-component.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.