Pretty much what is says in the title. Redis had been using the BSD-3 license for years to encourage developers to write code for them for free and now they've gone and switched to some custom proprietary license in order to secure their theft of the labor of everyone who has contributed to the project over the years. It's the same age old story.

A harsh, but important reminder to never write code for projects with these weak open source licenses. These licenses ONLY exist so that your labor can be stolen, either by them re-licensing at some point in the future or other companies taking it right now. That's the only reason they use BSD/MIT-style licenses.

As an aside it's a shame we're stuck with the GPL given the person who wrote it.

  • combat_brandonism [they/them]
    ·
    9 months ago

    now they've gone and switched to some custom proprietary license in order to secure their theft of the labor of everyone who has contributed to the project over the years

    I mean they were also securing it against the theft of their labor by cloud monopolists just whitelabeling their software. Almost like they should've just AGPL'd it from the get-go. Open source non-copyleft is just bootlicking with extra steps.

    As an aside it's a shame we're stuck with the GPL given the person who wrote it.

    order-of-lenin

  • footfaults
    ·
    edit-2
    1 month ago

    deleted by creator

  • hello_hello [comrade/them]
    ·
    edit-2
    9 months ago

    Were not stuck with the GPL. The GPL is stuck with us not using it.

    person who wrote it.

    Funny, that same person also wrote essays explaining this same exact thing and those essays are hosted on a place called gnu dot org.

    Can't get too angry though, this sort of thing happens all the time. Which is why GNOME is the flagship Linux desktop and not KDE with Qt.