1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Redis license change

    From Micke Nordin@21:1/5 to All on Fri Mar 22 07:30:01 2024
    ------DPT1K8J9H28WV5DP06LE2IMK6S13L9
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    What will Debian do with regard to the Redis announcement that they will go proprietary[0]?

    Fedora seems to be moving fast to get rid of Redis[1] and maybe we should start thinking about this too?

    Some drop in replacements are KeyDB[2] and redict[3]. Both of these have issues as far as debian packaging goes. KeyDB haven't yet synched the 7.x changes from upstream redis, and are still on the 6.3 patch level. Redict is a very new project, and a
    direct result of the license change. The KeyDB project have been a round for a while and is in heavy use by Snapchat, but does not see a heavy invetment in time from them, so development is quite slow.


    0. https://redis.com/blog/redis-adopts-dual-source-available-licensing

    1. https://lists.fedoraproject.org/archives/list/[email protected]/thread/XVFFKU2NYB2Q3BQUYNANSDNE4VCJQ6KF

    2. https://github.com/Snapchat/KeyDB/issues/798

    3. https://codeberg.org/redict/redict

    All the best,
    Micke
    ------DPT1K8J9H28WV5DP06LE2IMK6S13L9
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html><html><body><div dir="auto">What will Debian do with regard to the Redis announcement that they will go proprietary[0]?<br><br>Fedora seems to be moving fast to get rid of Redis[1] and maybe we should start thinking about this too?<br><br>
    Some drop in replacements are KeyDB[2] and redict[3]. Both of these have issues as far as debian packaging goes. KeyDB haven't yet synched the 7.x changes from upstream redis, and are still on the 6.3 patch level. Redict is a very new project, and a
    direct result of the license change. The KeyDB project have been a round for a while and is in heavy use by Snapchat, but does not see a heavy invetment in time from them, so development is quite slow.<br><br><br>0. <a href="https://redis.com/blog/redis-
    adopts-dual-source-available-licensing">https://redis.com/blog/redis-adopts-dual-source-available-licensing</a><br><br>1. <a href="https://lists.fedoraproject.org/archives/list/[email protected]/thread/XVFFKU2NYB2Q3BQUYNANSDNE4VCJQ6KF">https:/
    /lists.fedoraproject.org/archives/list/[email protected]/thread/XVFFKU2NYB2Q3BQUYNANSDNE4VCJQ6KF</a><br><br>2. <a href="https://github.com/Snapchat/KeyDB/issues/798">https://github.com/Snapchat/KeyDB/issues/798</a><br><br>3. <a href="https://
    codeberg.org/redict/redict">https://codeberg.org/redict/redict</a><br><br>All the best,<br>Micke</div></body></html>
    ------DPT1K8J9H28WV5DP06LE2IMK6S13L9--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Smith@21:1/5 to Micke Nordin on Fri Mar 22 13:50:01 2024
    Hi,

    On Fri, Mar 22, 2024 at 07:00:40AM +0100, Micke Nordin wrote:
    What will Debian do with regard to the Redis announcement that
    they will go proprietary[0]?

    There isn't really any choice as it's no longer free software. So at
    best it gets moved into non-free I suppose (it is still source
    available) if anyone has the will. It seems likely that the
    maintainer will not have the will to see it moved to non-free. You'd
    have to ask them.

    As for what if anything replaces it, it is more down to if anyone
    has the will and interest to package things. I expect there'll be
    some alternatives packaged, since it's a popular use case.

    Fedora seems to be moving fast to get rid of Redis[1] and maybe we
    should start thinking about this too?

    It won't require much thinking. 😀

    It's not a matter for debate whether it qualifies for the main
    archive - it doesn't.

    Redict is a very new project, and a direct result of the license
    change. The KeyDB project have been a round for a while and is in
    heavy use by Snapchat, but does not see a heavy invetment in time
    from them, so development is quite slow.

    When it comes to Debian it's more about will anyone put in the work.
    There is no central authority saying, "the project needs to replace
    Redis. Let us select XYZ as its replacement." — as there might be
    in, say, Fedora, where FESCo would make decisions like that. Debian
    doesn't work that way.

    There is no barrier to both KeyDB and Redict being packaged, other
    than there being maintainers to do it.

    You may like to submit a Request For Packaging bug for one or both,
    though again, may not get very far unless someone is already
    interested in doing it.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)