> Merging EE functions into CE has always been at the discretion of the core team
If someone independently implements all of the EE functions without looking at or using the EE code, will the core team reject the patch due to the fact that it would give a reason for customers to stop paying for EE? Is there any scenario where the core team would accept such a patch?
We advise people to submit one function at a time, this speeds up the process and makes it easier to incorporate feedback. If there is a high quality merge request for an EE feature we'll probably merge it. We hope that instead of duplicating work that has been done most people will focus their efforts on the 180 features marked accepting merge requests http://feedback.gitlab.com/forums/176466-general/status/7964... By the way, some people in the core team https://about.gitlab.com/core-team/ do not work for GitLab the company.
Why do you think that? The non GitLab employees in the core team want to see a great and successful open source product and that is what is happening. The code they contribute stays open source. Ask them how they feel about it, I would be surprised if they would feel the company unfairly appropriates their work. Do you think Open Core can work if done right or do you think it always is a bad thing?
If someone independently implements all of the EE functions without looking at or using the EE code, will the core team reject the patch due to the fact that it would give a reason for customers to stop paying for EE? Is there any scenario where the core team would accept such a patch?