> If Elastic wants to adopt an open core model, that's perfectly fine, but mixing the open source and proprietary bits in the same repo is messy and should rais

> If Elastic wants to adopt an open core model, that's perfectly fine, but mixing the open source and proprietary bits in the same repo is messy and should raise eyebrows. GitLab recently proposed a similar action. See the below link for the trouble they had maintaining two codes bases for one application. I have dealt with git submodules-it is not fun. https://about.gitlab.com/2019/02/21/merging-ce-and-ee-codebases/ https://about.gitlab.com/2019/02/21/merging-ce-and-ee-codeba... This is what GitLab proposed. I thought they handled it very transparently. Other companies should take note. The gitlab-ce and gitlab-ee repositories are replaced with a single gitlab repository, with all open issues and merge requests moved into the single repository. All frontend assets (JavaScript, CSS, images, views) will be open sourced under the MIT license. All proprietary backend code is located in the /ee repository. All documentation is merged together and clearly states which features belong to which feature set. Documentation is already licensed under CC-BY-SA.