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.
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.
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.
How does fork changes work ? do they have to open source it as well.
And is the license same as MariaDB license too ?
It is only a business cant build a competing service using it ?
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.