172

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

submitted 9 months ago by actual_patience@programming.dev to c/opensource@lemmy.ml

80 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[-] autotldr@lemmings.world 0 points 9 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!