[the_mitsuhiko]

Armin from Sentry here: obviously biased but the term I like the most to describe BSL as used by Sentry is: eventually Open Source.

The BSL upgrades automatically to Apache 2, so the only thing that it does is establishing a time window where there are some restrictions on the code.

A theoretical version is one where you just only release code with a large delay under the Apache 2 license and keep the rest closed source. That's also still technically open source but I would argue that's not a particular good version.

[samblr]

> Basically (can't reply to your other reply)

That is so good. How are the contributions managed from community ? is there a CLA that they need to agree. Couldn't find that in repo.

[the_mitsuhiko]

> How are the contributions managed from community?

Depends. Many places where the community contributes are just flat out open source licenses. For instance all our SDKs or certain backend services like our symbolicator service.

We don't have a lot of contributions going to the BSL licensed content for this to be much of a concern at the moment.

[zeeg]

They aren't in our case. Open Source doesn't have to mean community built, and Sentry (the product) is built almost exclusively by our company. Our philosophy is something along the lines of: Pull Requests are nice, but we'd rather you just give us open feedback and support the project in other ways.

We do accept PRs, and do have a large contributor community, but its primarily things like SDKs or documentation. The core product is complex enough that making a significant change - even if its one we agree with - is a hurdle.

[samblr]

Thank you both (Zeeg and Armin).

How does fork changes work ? do they have to open source it as well.

And is the license same as MariaDB license too ?

[samblr]

So if understood correctly, sentry entire source code is open source and can be used to monitor my backend/saas etc.

It is only a business cant build a competing service using it ?

[the_mitsuhiko]

Basically.