That being said, I think this is the first time I've seen someone at Sentry openly admit that you are trying to change the overall definition of open source and I do thank you for at least admitting it. If your end goal is to exclude commercial reuse from the open source definition then my theory about embrace/extend/extinguish seems to be as accurate as I thought.
This is fairly accurate, though there are a range of possible outcomes we would be satisfied with.
> my theory about embrace/extend/extinguish seems to be as accurate as I thought.
This is confused. Embrace/extend/extinguish means to initially participate in an open standard and then extend the standard in such a way that the non-extended version is sidelined.
What is the standard in this case? The Open Source Definition? What is the extension? A limit on commercial reuse in the OSD itself? A widely endorsed time-based license scheme such as BSL? Let's say this came to pass (use your imagination :P ). What is extinguished thereby? The OSD still stands. The supposed extinguisher is _more_ committed to the standard, not less. Other companies that use even weirder licenses like SSPL and ELv2 and now HFOIL :rolling-eyes: are likely brought back within an easier to reason about system and we can all stop arguing about this a couple times a year. There is net _more_ open source software in the world, in both the strong (current) and weak (time-delayed) sense.
That seems better to me than the current situation, and if in your view that is a change in the essence of open source, then yes, let's change open source. Change or die.
[disclosure: I'm Head of Open Source at Sentry, which owns Codecov.]
It's a straw man that lets them ignore the actual issue people have.
https://github.com/ssddanbrown/Open-Source-Confusion-Cases/i...
The repo readme has other examples of sketchy cases of open source and licensing usage. This aspect (of why not just use a different term) often gets ignored. Sometimes folks say they're using it "to prevent confusion to users since they would have heard about open source" which is always an ironic self-involved viewpoint to see.
1. The only way for businesses to release their core products under OSI-approved licenses is through a time delay such as the BSL.
2. It's good for businesses to release their core products under OSI-approved licenses.
3. Therefore, some concept of time-delayed release must be included in the definition of open source.
I'll concede that this is an evolution or refinement of the definition of open source, but not a change to the essence.
[disclosure: I'm Head of Open Source at Sentry, which owns Codecov.]
BSL doesn't try to redefine open source, it's clear it's transitional. So you're trying to do something MariaDB didn't do and the BSL doesn't do.
Or, you know, use the existing definitions for that transitional stage.
Your assertion is neither "therefore" nor "must".
I disagree with your sentiment here, as I see plenty of negative effects from unfunded open source, from low ethics companies, and from proprietary softwares deterrent to progress.
BSL is allowing us to give $500,000 to other open source projects this year, in addition to allowing any team in the world to use our software. What other open source company is putting their money where their mouth is? Nothing obligates us to make any of these decisions.
We need to evolve our irrational views of idealism and find common ground that allows sustainability if we want open source to thrive.