That seems highly irrational. As of today, CodeCov is scheduled for full, OSI compliant Open Source. In a few years people can fully fork and do what they want with it under the Apache 2 license. How is this not an improvement over closed source CodeCov?
Sure, Apache 2 straight away would be nicer but in practice that’s really impossible to accommodate in a commercial context. The only alternative I know is where you keep the interesting pieces closed (eg: open core).
For most people the BSL restrictions won’t matter and if you find interesting code in Sentry or CodeCov you want under Apache ahead of time, you can always mail us.
Being "scheduled for open source in three years" is not the same as being open source today.
Keep in mind there is a third option- CodeCov could just be honest about what they're doing. They could just say "shared source" or "source available" and take the exact same actions they're taking, just without misleading people.
From where I’m standing there is a massive difference between “source available” and BSL with Apache 2. The latter does not require goodwill from us in the future.
> Software that has source code available that automatically becomes open source at some explicitly specified, unchangeable, point in the future.
FWIW that's what I call it, but that's not exactly a well known enough term.
They are. In no way was I confused about what they are doing when I read this.
It's practically speaking open source for everybody with a poison pill for companies like AWS that have successfully charged rents on open source without giving anything back (like elastic search).
Restricting the hosting monopolist's freedom in order to fund the development of open source appears to make some people extremely angry.
That's not why anyone is angry. They're angry because it's labeled "Open Source" in the title, and then turns out to be not actually Open Source.
You may think it's purely an apolitical question of definition but it's about as apolitical as saying "Crimea is part of Russia".
Let's see how committed you are to that stance: just have them change it to the proposed wording. Should be no problem, since it's the same thing, right?
Then title the blog post, "CodeCov will eventually be Open Source" instead of being deceptive.
"impossible", huh? Wow, that must make Zulip the company really mad to hear they're going to close up shop tomorrow morning, and those GitLab folks are never going to go public </snark>
I mention GitLab as a nod to your open core comment because the MIT product they ship provides real value, as does their very real hosted offering
Ordinarily I would have gladly used Sentry's community and my good experience with its hosting and customer service as rebuttals but now ...
I feel perhaps you meant to link to https://gitlab.com/gitlab-org/gitlab/-/issues/329596 which describes their intention to accept Sentry formatted JSON payloads and store them in their own database. Searching for "no need" in that issue will highlight the number of times they were drawing a distinction between the effort required to run GitLab and the effort to run the 15 containers of Sentry self-hosted
What about all the supporting tech that we have released as MIT, BSD, or Apache?
All of that is funded by our ability to stop companies like your beloved GitLab from being the ones who commercialize the other parts. Our goal is not to argue about proper nouns, but to maintain the spirit of open source, and to do that we need to move the conversation forward.
BSL lets you use all features and self-host as long as you aren't a reseller. It is the best model I've seen.
https://about.gitlab.com/pricing/#compare-options
There is a box for "Open Source - MIT License". You'll notice most of the features are not covered under it.
> > I would enjoy seeing the specific features of the MIT codebase that they "don't allow" you to use
I feel we are not on the same page. But, good luck with your BSL future
- GitLab went with Open Core and kept most of their features closed source and not available to the community
- Companies that choose BSL provide all their features to the community both from a source available standpoint AND a usage standpoint.
In my opinion BSL is a MUCH better place to be in than the open core model.
If the choice is Open-Core vs Non OSI Approved License(tm) Open-Source, I definitely support the latter.
The OSI needs to be honest and push "OSI Approved Licenses(tm)"... Instead they're like the Simpson's Old Man Yells at Cloud meme, trying to pretend their special interest group has a trademark on "open-source"
https://knowyourmeme.com/memes/old-man-yells-at-cloud
Even though they admit that trademark was denied
https://opensource.org/pressreleases/certified-open-source.p...
It provides the flexibility of open source with the benefit of being supported and maintained by an actual company that has actual resources. There are percentage wise very few open source projects that have full time resources on them. There are so many tools/projects that if you report a bug to them that bug isn't getting fixed and if you create a PR to fix it it's nto getting merged because the maintainer has moved on with their lives and maintain it as a minor tiny hobby with 1-2 hours a month (if that) and there are tons where they've been taken over for vital maintainance only by a hardcore few that maintain lots of tools since the original maintainer has moved on. This annoys me about open source. It feels super unprofessional and normally we only get something that is maintained properly when it's closed source.
Whether "source available" is better or not is an argument I don't really care about- it's just a red herring. The issue I have is companies claiming Source Available is the same thing as Open Source. I find that to be completely unethical.
That is a fair point. It annoys me too.
Youre on the side of embrace, extend, extinguish.
These licenses exist because rentiers like Amazon and Microsoft are using their hosting market dominance to charge rents on open source and undermining the business model of companies like Elastic Search that actually create it.
It provides a revenue stream to actually pay developers to create more useful open source.
That's where the political imperative to gatekeep the term comes from.
Many people find it easier (or think it's easier) to generate a revenue stream from selling closed source software than from selling open source software, so they decide to make their software closed source.
We need to gatekeep terms for them to retain their meaning. We can't just accept it when tech companies try to change the meaning of "open source" to mean "we published the source code so you can read it". The term source-available exists, and it means something different from open source. If these people announced that they're making their software source-available, everyone would be happy, but they're not.
I am not saying they're required to be open source. I'm not saying they shouldn't be shared source. I'm simply saying they shouldn't lie about being open source. If CodeCov had the exact same license with the exact same restrictions, but didn't lie in their messaging, I wouldn't be commenting about it.
This is open source. It's entirely within the spirit of the movement.
The political imperative to twist the definition comes from tech monopolists, angry at a new wave of licenses that inhibit their ability to profit unhindered. You're getting outraged on their behalf.
> The Business Source License (this document, or the "License") is not an Open Source license. However, the Licensed Work will eventually be made available under an Open Source License, as stated in this License.
The only way you can argue that it's open source is if you're purposefully trying to deceive people.
Is it abusive to stop companies like AWS or GitLab from taking your work and selling it? Is it abusive to try to let as many people as possible use your software?
I’ll tell you what’s abusive - people thinking they have the rights to other peoples work unconditionally, or that they can profiteer off it without contributing back.
If CodeCov said "We are releasing our software under a shared source model" they would still be accomplishing all of the stuff you're saying (preventing AWS and Gitlab from using their product), but they wouldn't be lying about it. That's the major difference here.
The fact that this lie has damage beyond just their company is what's important. If we continue to shift the definition of "open" to include more and more cases of "closed" then the entire concept of open source loses it's meaning. Microsoft tried this in the 90s/2000s, and it's really disappointing to see companies that claim to be promoting open source attempting this today.
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.
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 don't see how this is 'Embrace, Extend, Extinguish'? This license guarantees that the code becomes Free Software at a maximum of 4 years - and in this case they've specified a shorter time period.
I'll give you that there are lots of games played in open source, so I understand that feeling of cynicism. But, this actually seems like an attempt to add some nuance to the commercial<-->free divide.
The reality is that many 'commercial' OSS companies have to take the open core route because understandably investors expect a return on their money. There are exceptions to this, but they are pretty rare. In fact, there are probably a whole set of SaaS companies that could be open source, but don't do so out of the fear of someone taking their code and 'free riding' them.
Finding a way to prefer the entity that sponsors/incubates the code base, while also genuinely allowing a community of contribution around it (not free riding) would be very beneficial in lots of situations. Maybe a better critique would be that this has some similarities to the Trolltech QT approach - but that's a different argument.
I would have rather see CodeCov stay completely closed than see them pollute and damage the open source community like this. Frankly, this abusive nonsense means I will stop using CodeCov and stop recommending them to anyone- which is what I did when Sentry went closed source as well.