TLDR: Companies should be required to pay developers for any open source software they use.

He imagines a simple yearly compliance process that gets companies all the rights they need to use Post-Open software. And they’d fund developers who would be encouraged to write software that’s usable by the common person, as opposed to technical experts.

It’s an interesting concept, but I don’t really see any feasible means to get this to kick off.

What are your thoughts on it?

  • BaumGeist@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    7 months ago

    people are always going to be floating ways to save capitalism in the face of communities privileging freedom over greed.

    this completely misses the point of free software, and fails to solve the problems Mr. Perens identifies with Open Source. He claims it fails to serve the “common person” (end users) and then proposes a solution that serves… only devs.

    Open Source has completely failed to serve the common person. For the most part, if they use us at all they do so through a proprietary software company’s systems, like Apple iOS or Google Android, both of which use Open Source for infrastructure but the apps are mostly proprietary… Indeed, Open Source is used today to surveil and even oppress them.

    All these problems are already solved by free software. the rebranding of “open source” was a compromise on the principles of free software to make the movement palatable to profit-seekers. In the end, it predictably failed to improve anything. The solution isn’t to reinvent the wheel, it’s to stop making the wheel square because the square lobby insists they’ll only use it if it’s square. The solution is copyleft, and free software being used more than it’s defanged cousin.

    The common person doesn’t know about Open Source, they don’t know about the freedoms we promote which are increasingly in their interest

    That’s a feature, not a bug. On one hand, if people knew about free software they wouldn’t be as good consumers. On the other hand, internals should be opaque to users; just as devs don’t want to have to know how the logic gates in the CPU are routing their code to write code, end users shouldn’t have to worry about the politics of the communities that developed their code.

  • Lvxferre@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    I think that the RHEL example is out-of-place, since IBM (“Red Hat”) is clearly exploiting a loophole of the GNU Public License. Similar loopholes have been later addressed by e.g. the AGPL and the GPLv3*, so I expect this one to be addressed too.

    So perhaps, if the GPL is “not enough”, the solution might be more GPL.

    *note that the license used by the kernel is GPLv2. Cue to Android (for all intents and purposes non-free software) using the kernel, but not the rest.

      • Lvxferre@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        They’re still providing the code for people who buy the compiled software. And they are not restricting their ability to redistribute that code. So it’s still compliant with the GPL in the letter. However, if you redistribute it, they’ll refuse to service you further versions of the software.

        It’s clearly a loophole because they can argue “ackshyually, we didn’t restrict you, we just don’t want further businesses with you, see ya sucker”.

        • Atemu@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          7 months ago

          Is there a court case about this already? Because that’s clearly not the intention of the GPL.

          • Lvxferre@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            7 months ago

            I don’t think that there is one yet, otherwise it would get famous. Not sure though.

  • ᕙ(⇀‸↼‶)ᕗ@lemm.ee
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    7 months ago

    what an idiot. the eval process is funny stupid and costly. the consequences will be companies both avoiding to use foss and also be less secure for using closed source. and then there is ai. code written with ai is not copyright-able and i bet anyone will prefer ai dumb code over costly foss code. may that dev rott in hell for this egomaniac idea of a free world.

  • onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    7 months ago

    I agree. Either use a business source license like Elastic and others, or fight for the installation of a third party that audits proprietary code for license use and sues if the rules haven’t been followed. It’s why I like the creative commons. They are quite realistic. Most of their licenses say: if you use this commercially, you have to pay. If not, then it’s free.

    People who claim business source licenses are “not opensource” sound like such capitalist shills to me. It’s as if they’re shouting from the rooftops “it’s OK to fuck over opensource developers because principles matter more than reality”.

    CC BY-NC-SA 4.0