News for hackers. Stuff that matters.
Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @11:55AM (#36972623)
I am so freaking sick of companies lying and exploiting open source. This is Embrace, Extend, Extinguish at it's finest. By calling closed source software open source they're moving the window and confusing the entire concept of open source.

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.

Re:CodeCov is now Open Source by the_mitsuhiko on Wednesday August 02, 2023 @12:02PM (#36972724)
> I would have rather see CodeCov stay completely closed than see them pollute and damage the open source community like this.

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.

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:07PM (#36972806)
You should really disclose that you work for Sentry/CodeCov in your comments about this.

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.

Re:CodeCov is now Open Source by the_mitsuhiko on Wednesday August 02, 2023 @12:20PM (#36973009)
I was assuming that writing “us” would be clear about my association.

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.

Re:CodeCov is now Open Source by meesles on Wednesday August 02, 2023 @12:46PM (#36973384)
Most good-faith commenters put clear statements about their association to what they're defending. Not doing so immediately makes me suspicious.
Re:CodeCov is now Open Source by azdle on Wednesday August 02, 2023 @12:47PM (#36973397)
Can I suggest calling it "Eventually-Open Source Software"?

> Software that has source code available that automatically becomes open source at some explicitly specified, unchangeable, point in the future.

Re:CodeCov is now Open Source by the_mitsuhiko on Wednesday August 02, 2023 @01:05PM (#36973645)
> Can I suggest calling it "Eventually-Open Source Software"?

FWIW that's what I call it, but that's not exactly a well known enough term.

Re:CodeCov is now Open Source by pseudalopex on Wednesday August 02, 2023 @03:27PM (#36975877)
Eventually open explains itself. And makes anyone not sure what it means aware to find out. It is superior entirely to lying.
Re:CodeCov is now Open Source by pydry on Wednesday August 02, 2023 @12:15PM (#36972922)
>Keep in mind there is a third option- CodeCov could just be honest about what they're doing.

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.

Re:CodeCov is now Open Source by yjftsjthsd-h on Wednesday August 02, 2023 @12:20PM (#36972998)
> Restricting the hosting monopolist's freedom 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.

Re:CodeCov is now Open Source by pydry on Wednesday August 02, 2023 @12:27PM (#36973116)
It's the same thing. Theyre angry because they agree with big tech's gatekeeping of 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".

Re:CodeCov is now Open Source by yjftsjthsd-h on Wednesday August 02, 2023 @12:33PM (#36973207)
No, it literally is not the same thing, and is literally not about big tech at all. It is in fact very simple: Is the thing you're calling Open Source actually Open Source, or is it not? You don't get to change what words mean because you think they should change, or because your business model isn't compatible with their real meaning but you'd really like to use them anyways.
Re:CodeCov is now Open Source by cxr on Wednesday August 02, 2023 @12:49PM (#36973417)
> It's the same thing.

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?

Re:CodeCov is now Open Source by cosmojg on Wednesday August 02, 2023 @12:18PM (#36972972)
> As of today, CodeCov is scheduled for full, OSI compliant Open Source.

Then title the blog post, "CodeCov will eventually be Open Source" instead of being deceptive.

Re:CodeCov is now Open Source by mdaniel on Wednesday August 02, 2023 @12:14PM (#36972905)
> 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).

"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

Re:CodeCov is now Open Source by the_mitsuhiko on Wednesday August 02, 2023 @12:26PM (#36973103)
Everything is always fine until someone comes along and starts selling hosting of Open Source SaaS projects. I cannot talk for Zulip and I truly hope they will succeed with not relicensing or closing part of the software.
Re:CodeCov is now Open Source by mdaniel on Wednesday August 02, 2023 @12:49PM (#36973415)
This strawman argument gets trotted out every time and every instance that I've heard thus far is exactly that. It's the "otherwise the terrorists win" of my profession

Ordinarily I would have gladly used Sentry's community and my good experience with its hosting and customer service as rebuttals but now ...

Re:CodeCov is now Open Source by bentlegen on Wednesday August 02, 2023 @06:41PM (#36978822)
Re:CodeCov is now Open Source by mdaniel on Thursday August 03, 2023 @12:20AM (#36981318)
You are misinformed; they implemented a Sentry-compatible endpoint if the Project enabled it: https://gitlab.com/gitlab-org/gitlab/-/blob/v15.0.0-ee/lib/a...

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

Re:CodeCov is now Open Source by zeeg on Wednesday August 02, 2023 @12:51PM (#36973452)
Do you disagree the Apache licensed version of Sentry doesn’t provide real value?

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.

Re:CodeCov is now Open Source by sontek on Wednesday August 02, 2023 @12:51PM (#36973456)
GitLab is a good example of not actually opensource. They are open corse which is much worse than BSL. There are tons of features they don't allow you to use even if you self-host unless you purchase a license.

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.

Re:CodeCov is now Open Source by mdaniel on Wednesday August 02, 2023 @12:54PM (#36973492)
I would enjoy seeing the specific features of the MIT codebase that they "don't allow" you to use
Re:CodeCov is now Open Source by sontek on Wednesday August 02, 2023 @01:14PM (#36973774)
All the features they exclude from the MIT code base and only include in the The GitLab Enterprise Edition...

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.

Re:CodeCov is now Open Source by mdaniel on Wednesday August 02, 2023 @01:18PM (#36973833)
> All the features they exclude from the MIT code base and only include in the The GitLab Enterprise Edition...

> > 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

Re:CodeCov is now Open Source by sontek on Wednesday August 02, 2023 @01:21PM (#36973881)
What do you mean we aren't on the same page? These are two options when opensourcing things:

- 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.

Re:CodeCov is now Open Source by daniel_riel on Friday August 04, 2023 @01:17AM (#36995756)
I agree with you.

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...

Re:CodeCov is now Open Source by candiddevmike on Wednesday August 02, 2023 @12:23PM (#36973051)
In a commercial context, was this planned or some last ditch effort to get more users/usage?
Re:CodeCov is now Open Source by the_mitsuhiko on Wednesday August 02, 2023 @12:31PM (#36973177)
We generally Open Source our stuff. When we acquired specto for profiling all the stuff was opened up as well either under Open Source straight away for SDKs and supporting infrastructure or time locked under the BSL.
Re:CodeCov is now Open Source by zeeg on Wednesday August 02, 2023 @12:25PM (#36973094)
Planned - this is how we operate at Sentry, it just took us a bit of time to get it ready to release
Re:CodeCov is now Open Source by that_guy_iain on Wednesday August 02, 2023 @12:02PM (#36972731)
It's not closed source. They're source available. Which I would argue is better than both Open and Closed source.

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.

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:06PM (#36972786)
You can argue all you want, but it's not Open Source and even you agree about that.

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.

Re:CodeCov is now Open Source by that_guy_iain on Wednesday August 02, 2023 @12:08PM (#36972828)
> 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.

Re:CodeCov is now Open Source by pydry on Wednesday August 02, 2023 @12:05PM (#36972779)
You're taking an explicitly pro rentier stance here and seeking to shame a business model that actually supports the development of open source.

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.

Re:CodeCov is now Open Source by mort96 on Wednesday August 02, 2023 @12:28PM (#36973123)
Just don't fucking call your software open source when it's not open source. Don't try to leech off the goodwill people have towards open source by falsely claiming that your software is open source.
Re:CodeCov is now Open Source by pydry on Wednesday August 02, 2023 @12:32PM (#36973189)
It's open source hated by big tech that undermines Jeff Bezos's goodwill.

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.

Re:CodeCov is now Open Source by mort96 on Wednesday August 02, 2023 @01:09PM (#36973705)
It's not open source.

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.

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:09PM (#36972838)
Oh please.

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.

Re:CodeCov is now Open Source by pydry on Wednesday August 02, 2023 @12:21PM (#36973034)
Oh please is exactly what I thought when I read your comment.

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.

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:28PM (#36973124)
Read the first line of the BSL license-

> 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.

Re:CodeCov is now Open Source by zeeg on Wednesday August 02, 2023 @12:00PM (#36972699)
What’s abusive about it? 80% of Sentrys source code is licensed under Apache-2.0 (and is how Codecov will be in a few years) which is far more than what everyone’s favorite open core companies have done.

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.

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:04PM (#36972775)
The abusive part is the lie, especially the lie that is literally trying to change the definition of open source. There are sentry employees in this very thread trying to argue that "BSL is open source".

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.

Re:CodeCov is now Open Source by zeeg on Wednesday August 02, 2023 @12:08PM (#36972824)
I created the Sentry project, am the CTO, and represent one of the strongest voices in our company for why this opinion of open source must change or open source will continue to be unsustainable.

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.

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:15PM (#36972932)
There are a lot of companies that support open source (Github has given away far more than you have, other companies sponsor employees to work on software directly, etc etc), you aren't special just because you claim that you're an open source company. It's not the BSL that gives you the ability to donate money, it's the fact that you sell a profitable product. You could sell a proftable product with a closed source license, or you could call your license shared source, and still donate money.

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.

Re:CodeCov is now Open Source by whit537 on Wednesday August 02, 2023 @12:32PM (#36973188)
> your end goal is to exclude commercial reuse from the open source definition

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.]

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @02:00PM (#36974502)
Open Source has always meant without limitations on use. You want to extend the standard to add a limitation on use, which would in turn radically change the definition of open source (to the point where you'd extinguish the current definition). Rather than simply accept that open source doesn't work for your business, at least for your core product, you want to change the definition of open source to something that it isn't.
Re:CodeCov is now Open Source by azdle on Wednesday August 02, 2023 @12:14PM (#36972915)
No one is saying there's anything wrong with releasing your code under the BSL. What's wrong is that you're lying and claiming you're open sourcing your code.
Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:24PM (#36973068)
At this point it's hard not to think that they're purposefully ignoring this. It doesn't matter how many times I say that I don't care about their license, just their messaging, and yet we've got at least three employees from Sentry completely ignoring that and acting as if we don't think they have a right to license their own software.

It's a straw man that lets them ignore the actual issue people have.

Re:CodeCov is now Open Source by ssddanbrown on Thursday August 03, 2023 @04:16AM (#36982852)
They've been like this before with Sentry, when I've raised their sketchy use of open source. I have some example queries/responses in this issue:

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.

Re:CodeCov is now Open Source by whit537 on Wednesday August 02, 2023 @12:16PM (#36972936)
> literally trying to change the definition of open source

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.]

Re:CodeCov is now Open Source by tedivm on Wednesday August 02, 2023 @12:21PM (#36973031)
It's kind of crappy for you and others at Sentry to attempt to unilaterally change the definition of open source, despite the fact that there clearly is opposition to it.
Re:CodeCov is now Open Source by whit537 on Wednesday August 02, 2023 @12:37PM (#36973243)
Why do you say unilaterally? MariaDB wrote the BSL, not us. Sentry is far from the only company with the problem of wanting to open-source its core products without exposing itself to the risk of other companies cannibalizing our business model without contributing to product development. This is an existential threat and the BSL protects us from it so we can keep improving Sentry.
Re:CodeCov is now Open Source by Terretta on Wednesday August 02, 2023 @12:39PM (#36973270)
"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."

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.

Re:CodeCov is now Open Source by Terretta on Wednesday August 02, 2023 @12:37PM (#36973249)
> Therefore, some concept of time-delayed release must be included in the definition of open source.

Or, you know, use the existing definitions for that transitional stage.

Your assertion is neither "therefore" nor "must".

Re:CodeCov is now Open Source by JimDabell on Wednesday August 02, 2023 @01:18PM (#36973840)
Why are you so attached to calling something open source when it is not open source? You know it will piss people off. You know it will generate bad will. You can avoid all of that by simply not calling it open source. Why are you so insistent upon using deceptive labelling? Where is the benefit?
Re:CodeCov is now Open Source by slgeorge on Wednesday August 02, 2023 @04:51PM (#36977223)
> I am so freaking sick of companies lying and exploiting open source. This is Embrace, Extend, Extinguish at it's finest.

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.