182
Thoughts on Post-Open Source? (www.theregister.com)

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?

all 50 comments
sorted by: hot top controversial new old
[-] KpntAutismus@lemmy.world 83 points 10 months ago

in a fair world, all of these companies who abuse the GPL license woild get sued and have to face actual consequences. but the legal system favors the rich, and the FOSS dev is left to starve. killed by their own passion.

[-] actual_patience@programming.dev 9 points 10 months ago

Let's not be nihilist here. It's better to come up with solutions than to give up.

[-] KpntAutismus@lemmy.world 8 points 10 months ago

sure, i love change for the better. the EU parliament is proof that change like this is possible, one just needs funding for lobbbyists like rossmann has done it.

[-] onlinepersona@programming.dev 5 points 10 months ago

I honestly thing we need that third party instance that audits proprietary code for the licenses it uses to see if there's a breach. Then they could sue all the companies that don't abide by the license. Most likely GAFAM would lobby against such a thing because they know they use a lot of opensource stuff that could force them to opensource their stuff, but honestly, fuck them. They've made a killing on the backs of free work.

[-] Lmaydev@programming.dev 45 points 10 months ago

I mean just license it as such right? You can't say it's completely free for anyone to use then complain you aren't getting paid.

[-] actual_patience@programming.dev 1 points 10 months ago

Well the question is, how would such a license look like? Or would it be a contract and not a license?

I guess I should ask a lawyer these questions, but I wanted to see what others here thought about the idea.

[-] Lmaydev@programming.dev 2 points 10 months ago

You can buy a license to use software. That's how a lot of software works.

[-] filister@lemmy.world 33 points 10 months ago

All the people predicting doom and gloom for open source, but the reality is that without open source we wouldn't be in the position where we currently are in terms of technology.

To be honest, I also think the patent system should be revamped as it is extremely flawed at the moment and prone to abuse by patent trolls, and it is stifling innovation.

[-] library_napper@monyet.cc 25 points 10 months ago* (last edited 10 months ago)

Fuck no. A small business that is struggling to survive should be able to use WordPress for their website and Linux for their laptops without paying

[-] actual_patience@programming.dev 8 points 10 months ago

The fee could be really small but scale depending on factors like business size. Or there could be no fee outright for businesses smaller than a certain size.

[-] baseless_discourse@mander.xyz 8 points 10 months ago

That still sounds like a lot of confusion for small companies. especially given most FOSS is provided as-is without any legal consultant avaliable.

[-] jaeme@lemmy.ml 5 points 10 months ago

It's also against the very idea of software freedoms in the first place. This is just reinventing proprietary licenses.

[-] bizdelnick@lemmy.ml 23 points 10 months ago

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

You need to read the article yourself before writing TLDR. Spoiler: it is not about payments, it is about source code availability.

[-] actual_patience@programming.dev 5 points 10 months ago

If you had also read the article BTW you would have realized that spoilers: it's not about source code availability.

You saw the first few paragraphs about the Red Hat drama and didn't read further.

Reading the whole thing you'd realize it's a list of reasons why open source software hasn't become popular with the wider public, and his proposed solution to this.

I just included the idea he is proposing, others can read the article to see his reasoning.

[-] BaumGeist@lemmy.ml 19 points 10 months ago* (last edited 10 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 18 points 10 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.

[-] library_napper@monyet.cc 4 points 10 months ago

What loophole? I think they're just blatantly violating it

[-] lvxferre@lemmy.ml 5 points 10 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".

[-] randomaside@lemmy.dbzer0.com 3 points 10 months ago

Enshittification continues

[-] Atemu@lemmy.ml 2 points 10 months ago

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

[-] lvxferre@lemmy.ml 4 points 10 months ago* (last edited 10 months ago)

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

[-] TootSweet@lemmy.world 2 points 10 months ago* (last edited 10 months ago)

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

Love this.

[-] TootSweet@lemmy.world 16 points 10 months ago

So, Open Source was already kindof the capitalistic fork of the Free Software movement. And it feels like Parens' vision of Post-Open Source is about how to marry it more to "the market." If it's not clear from what I've said already, I'm not a fan of that specific aspect of it.

It is a problem that big companies reguarly violate the terms of the GPL. I hope good things come out of SFC v. Visio that give the GPL's requirements of distributing source code with compiled code more teeth, but we'll have to see. I do think the courts agreeing to interpret the GPL (at least in some cases) as a contract rather than as a license is a good thing. It was a gutsy move on the SFC's legal department's part, but the case shows more promise now that they'd made it than it did previously. Perhaps a GPLv4 that better deals with being interpreted as a contract is in order.

Though, I worry that what Parens has in mind for new licenses doesn't address what I'd want to see from the Open Source movement and will ultimately move (Post-)Open Source in the wrong direction.

Specifically what I want from FOSS licenses is to be able to (and to have assurance that others have the option to) write and distribute software with assurances that no one's going to use it to restrict users' rights down the line. The GPL has historically been imperfect at that. The AGPL is better. But the GPL has always been explicit about requiring companies to distribute source code with binaries. What we need is that but with teeth in the form of some combination of court precedent and more effective legalese.

If current licenses have the problem that big companies just ignore the terms set out in the license, I wouldn't imagine making a new sort of license with different terms like "big companies have to pay to get the benefit of using Pots-Open Source software" is really going to work.

All that said, I'm glad to hear discussion about the future of FOSS. I'm worried about where FOSS is now and where it's going and am glad to see more strategic thinking.

[-] actual_patience@programming.dev 2 points 10 months ago

If current licenses have the problem that big companies just ignore the terms set out in the license, I wouldn't imagine making a new sort of license with different terms like "big companies have to pay to get the benefit of using Pots-Open Source software" is really going to work.

It's more that they avoid the spirit of the licensing, not the terms (except Red Hat of course).

I suppose you can split this into two separate arguments:

  • Swap from licenses to more enforceable contracts

  • Have companies pay open source devs

[-] Auzy@beehaw.org 14 points 10 months ago

Doesn't make sense at all.

I keep seeing Redhat used an example, but they contribute a HUGE amount a source code and projects.. Pipewire, systemd, rpm, DBUS and even the main XML addon for VSCode, etc.

I don't think people realise how much poop linux would be swimming in if they went bankrupt..

Redhat are literally one of the big reasons why Linux is so seamless these days, and they're solving a lot of the big problems. And from my understanding, they still contribute the code seperately anyway.

That being said, I agree money needs to go towards developers. However, a lot of them end up hired at major companies. And I don't think this is the way to approach it

[-] baatliwala@lemmy.world 9 points 10 months ago

Don't kid yourselves, regardless of all your ideals open source only works because it's free from a monetary perspective.

Companies work on patches to Linux or other software because it primarily benefits themselves, and they only use Linux because it's free. Companies create hardware on Linux because it's free. They can manufacturer cheap devices and people will buy them because they were low cost primarily because of the use of FOSS software.

Nearly all of FOSS is funded by corporations whether you like it or not, for the reasons you want to hear or not. The only thing that drives people is money.

[-] halm@leminal.space 21 points 10 months ago

The only thing that drives people is money.

Hundreds of thousand of unpaid open source contributors would have a word about that. In fact, millions of voluntary workers in other fields, too.

You're right that companies contribute to open source as well, and that their motivations are probably self serving. Your conclusion doesn't hold water, though.

[-] C126@sh.itjust.works 7 points 10 months ago

Right? This guy has never heard of passion

[-] halm@leminal.space 9 points 10 months ago

Also: generosity, altruism, compassion, kindness, curiosity, exploration, principle, idealism, etc, etc.

IMHO, money is something that exists in the world and that I need to live. It's a necessary evil, not a universal human driving force. And believe me, I'm neither rich or even financially afloat.

[-] actual_patience@programming.dev 2 points 10 months ago

they only use Linux because it's free. Companies create hardware on Linux because it's free

Companies use open source software because it's the cheapest option. It's all about margins.

Nearly all of FOSS is funded by corporations whether you like it or not

Yes, and FOSS can get a lot more funding if they charged companies even a little bit.

So as long as it's cheaper to pay a fee to continue to use an open-source software than it is to hire a group of developers to produce and maintain the same thing, the idea is viable.

load more comments (1 replies)
[-] n2burns@lemmy.ca 7 points 10 months ago

Great, let's inject more capitalism!

[-] Vendetta9076@sh.itjust.works 4 points 10 months ago

Seems like you need to inject more reading comprehension.

[-] grue@lemmy.world 6 points 10 months ago

Well, well, well, if it isn't the consequences of his own actions (inviting corporations to exploit Free Software by trying to re-brand it).

[-] Zerush@lemmy.ml 4 points 10 months ago* (last edited 10 months ago)

These are my thoughts regarding FOSS for a long time. The sense of facilitating the development and freedom of the project has been distorted years ago, when large corporations put their hands on this project, controlling it. Just look at the amount of "OpenSource" soft and services controlled by Google, M$, Amazon, FB ..... Yes, they are free to distribute and modifiable by devs, but mostly full of APIs from these corporations, not controllable by the user, subtracting their sovereignty and only modifiable with effort by people capable of understanding the scripts and redirects they contain. For a normal user it is increasingly irrelevant whether the project is FOSS or proprietary, while these products and the internet in general are in the hands of these companies.

A simple question is enough, which one do you prefer to use? FOSS projects from large corporations, or Freeware from small independent startups, if you don't have the knowledge to review the script anyway, almost impossible in millions of lines, with external references from large apps and services? It becomes decisions of mere trust, perhaps with the help of external services, such as WebKoll, Blacklight, Unfurl and similar, where in the end the license that the product has is irrelevant, with respect to security and privacy, often in question or not, in some like others. In the end only the intentions and ethics of the developer matter.

Yes, of course, the concept of OSS, FOSS and FLOSS requires a profound review and update, so that it does not become a destroyer of what it aims to protect and promote, a free internet.

[-] onlinepersona@programming.dev 4 points 10 months ago* (last edited 10 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

[-] jaeme@lemmy.ml 2 points 10 months ago* (last edited 10 months ago)

business source license

This is nonsense, Business source is not a free license. It is useless to try to invent new and clever licenses if they don't even follow the basic standards for Free software. The solution to helping hackers/devs in their work is not to suddenly reinvent proprietary licenses.

You might be discouraged to know that CC BY-NC-SA 4.0 is a non-free/proprietary license since it restricts commercial use.

There is no crude "fucking over." Creating software is a difficult task, and creating software that respects the user's freedom means giving up the temptation to use your abilities for harm and personal benefit.

[-] AstridWipenaugh@lemmy.world 3 points 10 months ago

This is exciting! He's come up with an economic principle where entities engage in an equitable exchange of goods for money where the consumer of the good pays for the value they receive. This could really change everything! I wonder what they'll call it?

[-] autotldr@lemmings.world 2 points 10 months ago

This is the best summary I could come up with:


RHEL stands for Red Hat Enterprise Linux, which in June, under IBM's ownership, stopped making its source code available as required under the GPL.

Pointing to popular applications from Apple, Google, and Microsoft, Perens says: "A lot of the software is oriented toward the customer being the product – they're certainly surveilled a great deal, and in some cases are actually abused.

The reason that doesn't often happen today, says Perens, is that open source developers tend to write code for themselves and those who are similarly adept with technology.

Perens acknowledges that a lot of stumbling blocks need to be overcome, like finding an acceptable entity to handle the measurements and distribution of funds.

Asked whether the adoption of non-Open Source licenses, by the likes of HashiCorp, Elastic, Neo4j, and MongoDB, represent a viable way forward, Perens says new thinking is needed.

Perens doesn't think the AGPL or various non-Open Source licenses focus on the right issue in the context of cloud companies.


The original article contains 1,837 words, the summary contains 164 words. Saved 91%. I'm a bot and I'm open source!

[-] deFrisselle@lemmy.sdf.org 2 points 10 months ago

So, basically the opposite of BSD3 license

[-] actual_patience@programming.dev 2 points 10 months ago

Yeah pretty much

[-] yournamehere@lemm.ee 1 points 10 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.

this post was submitted on 31 Dec 2023
182 points (100.0% liked)

Open Source

31292 readers
577 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS