• haui@lemmy.giftedmc.com
    link
    fedilink
    arrow-up
    50
    arrow-down
    3
    ·
    9 months ago

    There should be a mandate for companies and profiteers of a library or application to donate x amount of revenue upstream.

    For example 1% of your revenue should always go upstream, the next one sends 1% upstream, etc. You can do more of course but imo you should have to do 1%.

    I know this is a lot of money in googles example but honestly, its better than just using agpl and keeping them out in the first place. Make them pay their fair share.

    • hushable@lemmy.world
      link
      fedilink
      arrow-up
      30
      ·
      9 months ago

      My previous employer used to donate to the sole maintainer of a php library we used extensively (I’m not a php developer, so I don’t remember the name). It wasn’t much, but it was something and it is unfortunate that it is not the norm

        • CosmicTurtle@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          9 months ago

          It sort of is by license. Not directly but if you’re using one of the more restrictive licenses like GPL 3, it often doesn’t pass legal review due to many of the copy left provisions.

          Most companies simply find a similar library that has a more permissive license. A handful will contact the dev and buy a license.

          As much as the MIT license has made code more accessible, its permissiveness is the main reason I don’t use it for my own software, unless I really don’t care for it.

          • haui@lemmy.giftedmc.com
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            9 months ago

            Thanks for mentioning this. It was really helpful.

            Can you see why I want a more bespoke license which still allows for distribution, change and all that but also asks for you to donate part of your revenue (if you make any, that is) to foss projects?

            Because that would streamline the process and would probably find a lot of adopters which would lead to it getting accepted. Probably even more than agpl because you can still make stuff closed source (if we leave the „need to use same license“ out) but you need to pay anyway.

            I‘m getting a lot of hate for this btw. People are really unhappy with this idea because for some reason „free“ for them means free beer it seems.

            Edit: someone mentioned percentage of employees wages who work on foss projects be factored in which I think is great

            • CosmicTurtle@lemmy.world
              link
              fedilink
              English
              arrow-up
              3
              ·
              9 months ago

              I don’t think we need more licenses. OSS license proliferation is bad as it is. IMO, people should do their best to stick with the major licenses: GPL, AGPL, MIT, or Creative Commons if it doesn’t fit the above.

              The problem with a tax that you’ve proposed is that it would be nearly impossible to enforce. How would you know which companies are pulling your library?

              What I’ve been doing is adding the Commons Clause to my license and that I think helps. I don’t write wildly popular software so I don’t really see people donating or asking to purchase a license.

              I personally like the Mozilla model where they donate to various open source projects from a common fund. I’d like to see more stuff like that.

              • haui@lemmy.giftedmc.com
                link
                fedilink
                arrow-up
                1
                arrow-down
                1
                ·
                9 months ago

                Yeah, the mozilla model seems quite interesting.

                After tons of troll messages I‘m now at the point where I will just make everything agpl so nobody can use my stuff if its not the same license and be done with it. I will also make every software I fork agpl if possible which will be a fest.

    • umbrella@lemmy.ml
      link
      fedilink
      arrow-up
      21
      arrow-down
      1
      ·
      9 months ago

      we should bake something like that in whenever we feel like doing GPLv5 or something.

      “free for people, paid for corpos” or something

      • onlinepersona
        link
        fedilink
        English
        arrow-up
        13
        arrow-down
        3
        ·
        9 months ago

        It’s basically what Redis, ElasticSearch, and others have started doing, but people living in fairytale land are throwing a fit because “iT’s NoT frEe!!11!1”

        CC BY-NC-SA 4.0

      • dev_null@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        9 months ago

        Because when projects do it everyone runs away, forks are made, and everyone hates the developers because it’s “not open source anymore”.

    • WalnutLum@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      9 months ago

      I agree with this wholeheartedly,

      but if you feel about this methodology strongly you’re going to get hit with nay-sayers that use the same argument anti-VAT people use, as it’s ostensibly the same mechanism: that the developers farthest downstream would have to take the full amount of the percents piled up in their pricing scheme.

      • haui@lemmy.giftedmc.com
        link
        fedilink
        arrow-up
        9
        ·
        9 months ago

        Thanks but thats not what I meant. I was talking about a combined 1%. Like, if you used my work, you would need to donate at least (!) 1% of your total revenue to open source projects, ideally evenly distributed. That means the library further upstream would get a tiny amount but not nothing and if everyone did this, the library would have a million or more revenue streams (because libraries are widely used).

        • Auli@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          9 months ago

          So would their salaries for people working on OSS contribute to that 1%?

          • haui@lemmy.giftedmc.com
            link
            fedilink
            arrow-up
            2
            ·
            9 months ago

            That could be the case. Thanks for asking and providing valuable new ideas. I think the amount of foss said employees get should factor in, yes.

        • TrumpetX
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 months ago

          This wouldn’t work for a few reasons, but the most glaring is that it would incentive re inventing the wheel.

          • haui@lemmy.giftedmc.com
            link
            fedilink
            arrow-up
            2
            arrow-down
            2
            ·
            9 months ago

            Which is exactly my idea. The AGPL is A LOT worse in this regard since it prevents them from going closed source in the first place iirc. I think many small businesses would gladly use the software and pay 1% of their revenue.

            This kind of argument imo is circular because if I build your house for free, you will not build it yourself, plain and simple. If I provide a service, I ought to get paid for it, plain and simple. And if you make money off of my work, you are part of the problem if you dont donate anyway. So making it mandatory imo is absolutely no issue.

            • TrumpetX
              link
              fedilink
              English
              arrow-up
              2
              ·
              9 months ago

              Reinventing the wheel is exactly why we should use open source libraries.

              Expanding on other unintended outcome here: Different projects have different values. This takes no account for something like Spring vs Apache Commons IO. Or Rails vs nokogiri.

              Libraries will be incentivized into breaking apart to maximize revenue.

              This isn’t really unlike the unintended consequences of health insurance and how it leads to overpriced services with lots of indecipherable codes for service.

              It’s about how the system rewards (pays) for the service. I’m all for supporting open source, but the proposals in this thread are disturbingly anti open source.

              • haui@lemmy.giftedmc.com
                link
                fedilink
                arrow-up
                1
                ·
                9 months ago

                I have no idea what you are referring to. Feel free to provide a source.

                The consequences of our actions are for the most part completely oblivious until we try it, apart from starting wars and such. But even then its hard to say. So I respect your opinion but I disagree completely. Library maintainers have no reason to maintain libraries because they dont get paid or anything for it, which changes drastically once enough projects use my idea of a license.

                The health insurance you are referring to most likely is the american scam version where private companies can suck you dry as they want. Universal healthcare (what happens in some european countries) is what makes going to the doctor dirt cheap or completely cost free. The most disgusting pharma invenstions (like 1000x’ing a cancer medication that used to be dirt cheap iirc) are all american inventions.

                Thats the kicker. The system doesnt. They free load. Again, I respect your opinion. My idea is very much open source. It just enforces fairness. Thats all.