I tried a couple license finders and I even looked into the OSI database but I could not find a license that works pretty much like agpl but requiring payment (combined 1% of revenue per month, spread evenly over all FOSS software, if applicable) if one of these is true:

  • the downstream user makes revenue (as in “is a company” or gets donations)
  • the downstream distributor is connected to a commercial user (e.g. to exclude google from making a non profit to circumvent this license)

I ask this because of the backdoor in xz and the obviously rotten situation in billion dollar companies not kicking their fair share back to the people providing this stuff.

So, if something similar exists, feel free to let me know.

Thanks for reading and have a good one.

  • twei@discuss.tchncs.de
    0·
    7 months ago

    You can technically charge for FOSS, but that sort-of collides with the freedom to redistribute the software. You may have heard about that when the whole RHEL/Rocky Linux dispute happened.

    Equal shares can also be kind-of unfair if your backend is using sqlx for the entire database communication and then you also use some small image-conversion library to convert the favicon from .png to .ico.

    My last point may be a bit confusing, let’s try to make it a bit easier to understand: In this case, you are a company, that is directly using a piece of code that is licensed under the license you’ve been thinking about, and you’re also using a piece of proprietary software, e.g. some ERP-Software. The proprietary software is using a FOSS library that permits it to be used in a proprietary binary, let’s say because it’s BSD-Licensed. How do you know that the ERP-Software is using that library, and how would you determine how much you’d have to donate to them. You kind-of have to donate to them, because your ERP-Software wouldn’t run without that library

    • Barbarian@sh.itjust.works
      0·
      7 months ago

      The best use case for purchasing FOSS software is contractor work, specific modules for existing platforms and/or FOSS projects. I’ve done that myself in the past. The client pays for the custom software, it’s written, and then they gets to do absolutely whatever they want with it. If the client wants to publish it, they’re well within their rights. Most of the time it’s too entangled with their internal company workflow to be useful to anyone else though.