3 ms·
Using Gitlab at our company and I love it. I could never agree with the "small teams don't need/want time tracking" argument, so I'm very happy to see they rele
by markdog12 10y ago
Using Gitlab at our company and I love it. I could never agree with the "small teams don't need/want time tracking" argument, so I'm very happy to see they released it for CE.
- sytse 10y agoI'm glad to hear that. BTW The conversation about if this should be in CE happend in https://about.gitlab.com/2016/12/08/announcing-gitlab-enterprise-edition-premium/#comment-3045813029 https://about.gitlab.com/2016/12/08/announcing-gitlab-enterp... and https://gitlab.com/gitlab-org/gitlab-ce/issues/25517 https://gitlab.com/gitlab-org/gitlab-ce/issues/25517
- KuhlMensch 10y agoI am a bit unsure what Gitlab consider a small team. But I find myself getting a little exasperated when they choose to keep features from CE because "small teams don't need it". Last week I found this was the reason they did not include global contributer statistics in CE. This would be a trivial change, and an important one for my team of ~14 engineers with in-house tools and a microservice architecture who would like to see the pulse of development.
- sytse 10y agoThere are no features that are never needed by a small team. To make our business model work we do need to make some features exclusive to EE. The definition we use is: is this feature more relevant for organizations that have more than 100 potential users? We thought this was the case for timetracking but we were wrong and reversed the decision.