It’s early. Everyone is confused. If I could define it, I would have provided a defintion.
At this stage, it’s about acquiring requirements and looking at prior art. And being humble about the solution space. No? If you don’t think there’s any problem today, then argue that point.
> By definition you cannot have an open source licence which says "cannot be used for bezos yacht".
By definition by what definition? There are already disagreements about what open source is, long before these business models. The problem solving comes first, and then there may or not be a debate whether about whether the solution fits better into an existing definition or a new one.
> Either you accept that […] or you don't open source your code
But why? Is this an intrinsic duality or an anccidental/historical one? Or is it about preventing scope creep of the open source term? The latter is easy to solve - don’t call it open source. Or at least defer the debate.
No, it is not, it is decades in, in a well-understood area. Some VC-backed firms (and the VC’s backing them, who see this as critical beyond the immediate firms) want to trade on the idea and popularity of open source without its substance because open source as has has been known for decades is not a viable foundation for the kind of business model that they would like, but has at the same time secured the kind of mindshare in the market that makes it difficult for proprietary software to achieve the kind of rapid ramp-up that provides the timing and combination of returns they want. So they’ve decided to spend a lot of effort making everyone feel confused at some ginned up new threat to open-source, which is not a threat to open source, not something that open source community hasn’t known about for decades, but just a problem for a bait-and-switch business model in which software gains traction trading on the cachet of open source and then rakes in monopoly rents that avoiding is one of the benefits to users of open source licensing.
They want users to see them like Postgres, but they want to milk users like Oracle. That’s the problem – a marketing problem for proprietary software vendors. The attempt to sell confusion is an attempt to conceal that that is all the problem is.
Dislike of VCs as much as the next guy, but is this a representative picture? Many companies I’ve seen have been genuinely interesting, like SurrealDB, CockroachDB and Hashicorp. Are you saying it’s all a long bait and switch game?
In some cases I wouldn't be surprised, in others sure maybe the founders did believe in open source at some point (there are definitely individuals who claim to have never changed their opinion, but their writings would suggest otherwise), but either they've left (voluntarily or not) or simply they gave away control to others who are only in it to make money.
As always, Chesterton's fence applies: all of the 10 points of the OSD were widely debated at the time (as was its predecessor, the Debian Free Software Guidelines), so it's worth explaining why the issues raised then no longer apply.
Right. It’s a public benefit org based in CA. I very much appreciate what they do, but I don’t think they own or should own the term. In either case, it’s a moot point because it’s just a term definition. The important thing is to find a good model that promotes the same or very similar benefits we get from traditional OSS but in an evolving world.
It’s early. Everyone is confused. If I could define it, I would have provided a defintion.
At this stage, it’s about acquiring requirements and looking at prior art. And being humble about the solution space. No? If you don’t think there’s any problem today, then argue that point.
> By definition you cannot have an open source licence which says "cannot be used for bezos yacht".
By definition by what definition? There are already disagreements about what open source is, long before these business models. The problem solving comes first, and then there may or not be a debate whether about whether the solution fits better into an existing definition or a new one.
> Either you accept that […] or you don't open source your code
But why? Is this an intrinsic duality or an anccidental/historical one? Or is it about preventing scope creep of the open source term? The latter is easy to solve - don’t call it open source. Or at least defer the debate.