“Most proprietary relicensing businesses work as follows: a single codebase is produced by a for-profit company, which retains 100% control over all copyright in the software (either via an ©AA or a CLA). That codebase is offered as a gratis product to the marketplace, and the company invests substantial resources in marketing the software to users looking for FOSS solutions. The marketing department then engages in captious and unprincipled copyleft enforcement actions in an effort to “convert” those FOSS users into paying customers for proprietary licensing for the same codebase. (Occasionally, the company also offers additional proprietary add-ons, improvements, or security updates that are not available under the FOSS license — when used this way, the model is often specifically called “Open Core”.)”

  • @wraptile
    link
    34 years ago

    What a drab read.

    I really don’t like sfconservancy style - who even reads these bloated walls of text?

    I think the biggest issue with libre culture is that it’s one of the most punk modern cultures out there but has the complete opposite representation of giant, dry walls of text with no passion, inspiration or yet, even actual content!

    • @LofenyyOPM
      link
      14 years ago

      Haha I typically don’t like their stuff, but I saw this article on Mastodon and it resonated with me, so I posted it. I will admit that it’s definitely a dry read, but I also think it’s important. It’s good news.

  • @LofenyyOPM
    link
    34 years ago

    I never knew how proprietary relicensing worked before reading this. This definitely justifies my decision to only use GTK+ in the software that I write instead of QT, which follows this business model. When you think of something as popular as QT potentially doing something like this, it makes you realize that there could be a large number of businesses who do this shady practice without us knowing.

    Not to knock QT, I’m not saying that they’re trying to get people to submit into buying proprietary licenses, I’m just saying that the GPL, or any free software license, should apply freely to anyone. Once something is free software, it should remain free software.

    I’m very curious about what license they’re drafting and what it’s going to look like in the future!

    • @wraptile
      link
      34 years ago

      I’m not sure this applies to QT though. It used to apply to some libraries like PyQt which had dual lincese: it’s floss for floss projects but for paid ones you need to pay but there were completely free alternatives like Pyside.
      The whole KDE project is based on QT so I’d argue it’s pretty safe, right?

      • @LofenyyOPM
        link
        34 years ago

        Honestly, it probably is safe, but I’d rather personally not take the risk. I know QT does do multi licensing like this. I like what this article says. Copyleft licenses should apply to everyone equally, no exceptions. Especially now that free software is desirable to developers more often than not.