This is a hard decision to make. It would be considered on the basis of a couple of things. If it is derivate of already existing code, we would suggest not to do that. If it is an original work, then we would consider those.

Having said that, we want to reduce such kind of conflicts happening in the community. So we would try to limit an entire module under EE License rather a part of it.

> So we would try to limit an entire module under EE License rather a part of it.

As someone not familiar with this license, can you expand a little more into what it offers?

Also another option for this is for you guys to maintain your own branch which would be used for the free hosted solutions so any enterprise feature PR's can be contained to the self-hosted option.

Handling separate closed fork is one of the solution. Historically, it is an overhead for the team managing the project. You can read about the experience shared by Metabase [0].

[0] https://www.metabase.com/blog/Opening-Metabase-Enterprise/in...

I think by EE license, they mean "Enterprise Edition" (aka commercial license, not sure if the code itself would be considered open, closed or "shared").

That correct. The code can't considered open but rather source available.

nice to hear you guys open sourcing this product! Also be interested how you resolve this issue.