https://gitlab.com/gitlab-org/gitlab-ce/issues?state=opened&author_username=deckar01 https://gitlab.com/gitlab-org/gitlab-ce/issues?state=opened&... As more of

https://gitlab.com/gitlab-org/gitlab-ce/issues?state=opened&author_username=deckar01 https://gitlab.com/gitlab-org/gitlab-ce/issues?state=opened&... As more of the feature development goes into EE, there is less of a need to back port the latest changes. There are tons of workflow processes I would love to more tightly integrate with GitLab, but not all of them would make sense outside of my organization. Some of them can be hacked together with bots, but some of them require extending the core functionality and would probably require a fork. > forking GitLab instead of contributing upstream I think this is the problematic mindset. Meaningful contributions to upstream will follow useful forks. > they all fell behind with upstream and couldn’t keep up to date anymore. Code churn doesn't just slow down forks, it slows down core development.