Like many of you, I was disappointed when I learned that Redis®1 was changing to a non-free licensing model. This is a betrayal of the free software community, but perhaps not an entirely surprising one. Forks are likely to start appearing in the coming days, and today, I would like to offer Redict to you as a possible future home for your needs, and present its trade-offs as compared to the other forks you’re likely to be choosing from soon.
  • hollyberries@programming.dev
    3·
    8 months ago

    For resources on licenses, off the top of my head there are:

    Both sites have breakdowns of each license for the layperson. As always, the GNU Licenses page has others.

    In response to your arguments:

    1. While I personally agree with this 100%, it unfortunately doesn’t fall under the OSI definition of open-source. I’m only saying this because I ranted on another ActivityPub service about that last year after several high-profile open-source projects switched over to more restrictive licenses. I was called out by a number of people for even suggesting that closed-source developers should be required to pay up. In the end, the consensus was to use AGPL or a license with such a muddy definition that Legal departments can’t use to work with such as the WTFPL or Good, not Evil license (full text to the Good, not Evil license here).
    2. Also in agreement with this, except in cases where a user’s project becomes their full-time job and financial compensation is required. From there, I find it ethical to charge for personalised support. There unfortunately are developers that work at large businesses that try to hide who they are working for in order to get support without contributing in some way.

    The choice is mainly about how much effort you’re willing to pour into supporting the project alone if others take interest in it, how much you want others to be willing to pour into supporting your project via contributions or financials, and how you would feel if a more successful fork of your project becomes more restrictive after a license change or organisation restructuring (looking at you, Gitea and RedHat).

    My personal choice in license is simple. Most of my software is for me and works on my machines. I also don’t want commercial entities providing my software as a service without contributing code back, so AGPL is an easy choice. I do have a disclaimer on my public facing git forge that none of my AGPL licensed projects support dual licensing because I value code contributions more than money, especially if they come from the enterprise sector.

    • haui@lemmy.giftedmc.com
      1·
      8 months ago

      Thats awesome! Thank you so much for taking the time to write this out. I have a good understanding of your pov now and I like it.

      Would you mind connecting on dm or matrix if one ever wanted to help? I‘m currently working on a couple projects which require me to step up my game quite a lot. I‘d be interested in your opinion.

      Have a good one.