Do they even see themselves how utterly ridiculous they are?
Do they even see themselves how utterly ridiculous they are?
Posted Nov 4, 2024 17:14 UTC (Mon) by excors (subscriber, #95769)In reply to: Do they even see themselves how utterly ridiculous they are? by kleptog
Parent article: OSI board AMA at All Things Open
> The intent of all this language is relatively straightforward: if you are a user of an application (perhaps hosted on the net somewhere), you have the right to extract your data from that application to use with your own modified version of the code. Control of data is not to be used to lock users into a de-facto proprietary system.
From that article plus the Register one and some mailing list posts, it sounds like Bruce Perens didn't mind that specific licence's requirements, but he did mind the general idea of Open Source licences imposing requirements on data, largely because it makes the licences much trickier to comply with ("It's a good goal but it means you now need to have a lawyer to understand the license and to respond to your users"), and Open Source ought to be made simpler instead. He thought data restrictions should be completely out of scope for Open Source, and the OSI should reject CAL on that basis.
The OSI didn't have an existing policy on that, so it sounds like his arguments about field-of-use restrictions were stretching to find a technical justification within the OSD to reject it. And then he got increasingly frustrated when people didn't agree with him about the proposed policy or about that interpretation of the OSD, until he ended up quitting the OSI and accusing the board of conspiracy.
Incidentally, since at least 2020 he's been talking about what is now Post-Open (https://postopen.org/), apparently with the intent of supplanting Open Source by having a large number of software projects under a single new zero-cost licence for individuals and small businesses, and a second licence for larger businesses which requires royalties of 1% of the business's entire revenue paid to the Post-Open organisation. That organisation will subtract operating costs then divide the rest amongst individual developers (or their employers) in proportion to how widely each project is used and the number of lines of code each developer has written in the projects' Git repositories.
The goal is to make it simple for companies to comply - they don't have to spend any effort working out exactly which projects they use and how to follow all their different licences or pay for multiple support contracts etc, they just make a single payment to one organisation and that covers all their software - while also making them fund maintenance of the projects they rely on. Which doesn't sound like a bad goal in general, but his specific approach seems, uh, questionable. And I guess it's unsurprising he fell out with the OSI when his ideas are so radically different to Open Source.