5 ms·

We've been using gitlab for most VideoLAN projects, and are moving towards it for all of them (including vlc and x264). A lot of things are great, and going in

by jbk 10y ago

We've been using gitlab for most VideoLAN projects, and are moving towards it for all of them (including vlc and x264). A lot of things are great, and going in the right direction, but the issues tracker is really lacking. The lack of custom fields, that you find in all other bugtrackers except github, and the lack of dependent issues are really blocking us to move full to gitlab. And the biggest issue is that they're discussing to do it, but only in the non-open-source version, which we cannot use...

sytse 10y ago
Thanks for using GitLab. We have open sourced features based on your request before https://news.ycombinator.com/item?id=10931690 https://news.ycombinator.com/item?id=10931690 I can't promise anything regarding these features. Especially custom fields are a typical EE feature in our perspective. The dependent issues feature proposal https://gitlab.com/gitlab-org/gitlab-ce/issues/4058#note_24946893 https://gitlab.com/gitlab-org/gitlab-ce/issues/4058#note_249... is still on the CE tracker but I'm not sure what it's future is.
- jbk 10y ago
  Don't take me badly, Gitlab is the best thing around. We've tested many solutions... (too many) It's just that I really want to quit using trac, who is slow and not integrated with the rest of the infrastructure.
  - sytse 10y ago
    No worries, we love you too! Our Product Manager Victor Wu will email you to learn more.
deleted 10y ago
[deleted]
victorwu 10y ago
You are referring to this one right? https://gitlab.com/gitlab-org/gitlab-ee/issues/1906 https://gitlab.com/gitlab-org/gitlab-ee/issues/1906. Yes, it is currently marked as an EE feature. And Sid linked to the dependent issues feature below. Both of these features are not scheduled for development yet. We scope work out month to month, so we can't promise anything regarding those at this time. But we are discussing them as you see in the issues and considering how they would fit into our product as we recognize they are important features for many teams. For relations between issues, we are considering various designs, such as: https://gitlab.com/gitlab-org/gitlab-ee/issues/1941 https://gitlab.com/gitlab-org/gitlab-ee/issues/1941 and https://gitlab.com/gitlab-org/gitlab-ce/issues/29444 https://gitlab.com/gitlab-org/gitlab-ce/issues/29444.
- jbk 10y ago
  How can we help? Can we help coding?
mydigitalself 10y ago
> non-open-source version, which we cannot use... is it a function of cost, or otherwise?
- newsat13 10y ago
  AFAIK, the EE code is also open source. So this is somehow a function of cost. The massively insanely popular VLC project somehow has no money to pay for it's version control? How did it come down to this?
  - sytse 10y ago
    Our EE version is publicly viewable but not open source. I can't speak for the VLC project but previously they indicated that cost was not the problem. They care about the free as in freedom instead of the free as in beer.
lima 10y ago
I recommend Phabricator: https://www.phacility.com/ https://www.phacility.com/ It has a best-in-class code review tool and a bug tracker with custom fields, permissions, templates, dependencies and more. Its code review is built on a patch workflow (like the email-based one that the Linux kernel uses) and works very well, especially for large teams. Merge requests are clunky in comparison. Many large open source projects moved to it, including Blender, Wikimedia, FreeBSD, Haskell, LLVM and more. I'm using it in production, am glad to answer any questions. The development team is dog-fooding it: https://secure.phabricator.com/ https://secure.phabricator.com/ Example review: https://secure.phabricator.com/D17538 https://secure.phabricator.com/D17538 (just picked one at random, there are better examples probably) Example task: https://secure.phabricator.com/T8783 https://secure.phabricator.com/T8783 Wikimedia instance: https://phabricator.wikimedia.org/ https://phabricator.wikimedia.org/ Mockups: https://phabricator.wikimedia.org/pholio/ https://phabricator.wikimedia.org/pholio/ Workboard: https://phabricator.wikimedia.org/project/view/171/ https://phabricator.wikimedia.org/project/view/171/ And much more! The developers (especially epriestley and chad) are very professional and have a lot of experience managing large projects at scale. Large essay about the workflow: https://secure.phabricator.com/phame/post/view/766/write_review_merge_publish_phabricator_review_workflow/ https://secure.phabricator.com/phame/post/view/766/write_rev...

by jbk 10y ago

sytse 10y ago

Thanks for using GitLab. We have open sourced features based on your request before https://news.ycombinator.com/item?id=10931690 https://news.ycombinator.com/item?id=10931690 I can't promise anything regarding these features. Especially custom fields are a typical EE feature in our perspective. The dependent issues feature proposal https://gitlab.com/gitlab-org/gitlab-ce/issues/4058#note_24946893 https://gitlab.com/gitlab-org/gitlab-ce/issues/4058#note_249... is still on the CE tracker but I'm not sure what it's future is.

jbk 10y ago
Don't take me badly, Gitlab is the best thing around. We've tested many solutions... (too many) It's just that I really want to quit using trac, who is slow and not integrated with the rest of the infrastructure.
- sytse 10y ago
  No worries, we love you too! Our Product Manager Victor Wu will email you to learn more.

deleted 10y ago

[deleted]

victorwu 10y ago

You are referring to this one right? https://gitlab.com/gitlab-org/gitlab-ee/issues/1906 https://gitlab.com/gitlab-org/gitlab-ee/issues/1906. Yes, it is currently marked as an EE feature. And Sid linked to the dependent issues feature below. Both of these features are not scheduled for development yet. We scope work out month to month, so we can't promise anything regarding those at this time. But we are discussing them as you see in the issues and considering how they would fit into our product as we recognize they are important features for many teams. For relations between issues, we are considering various designs, such as: https://gitlab.com/gitlab-org/gitlab-ee/issues/1941 https://gitlab.com/gitlab-org/gitlab-ee/issues/1941 and https://gitlab.com/gitlab-org/gitlab-ce/issues/29444 https://gitlab.com/gitlab-org/gitlab-ce/issues/29444.

jbk 10y ago
How can we help? Can we help coding?

mydigitalself 10y ago

> non-open-source version, which we cannot use... is it a function of cost, or otherwise?

newsat13 10y ago
AFAIK, the EE code is also open source. So this is somehow a function of cost. The massively insanely popular VLC project somehow has no money to pay for it's version control? How did it come down to this?
- sytse 10y ago
  Our EE version is publicly viewable but not open source. I can't speak for the VLC project but previously they indicated that cost was not the problem. They care about the free as in freedom instead of the free as in beer.

lima 10y ago

I recommend Phabricator: https://www.phacility.com/ https://www.phacility.com/ It has a best-in-class code review tool and a bug tracker with custom fields, permissions, templates, dependencies and more. Its code review is built on a patch workflow (like the email-based one that the Linux kernel uses) and works very well, especially for large teams. Merge requests are clunky in comparison. Many large open source projects moved to it, including Blender, Wikimedia, FreeBSD, Haskell, LLVM and more. I'm using it in production, am glad to answer any questions. The development team is dog-fooding it: https://secure.phabricator.com/ https://secure.phabricator.com/ Example review: https://secure.phabricator.com/D17538 https://secure.phabricator.com/D17538 (just picked one at random, there are better examples probably) Example task: https://secure.phabricator.com/T8783 https://secure.phabricator.com/T8783 Wikimedia instance: https://phabricator.wikimedia.org/ https://phabricator.wikimedia.org/ Mockups: https://phabricator.wikimedia.org/pholio/ https://phabricator.wikimedia.org/pholio/ Workboard: https://phabricator.wikimedia.org/project/view/171/ https://phabricator.wikimedia.org/project/view/171/ And much more! The developers (especially epriestley and chad) are very professional and have a lot of experience managing large projects at scale. Large essay about the workflow: https://secure.phabricator.com/phame/post/view/766/write_review_merge_publish_phabricator_review_workflow/ https://secure.phabricator.com/phame/post/view/766/write_rev...