Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dear open-source maintainers, a letter from GitLab

about.gitlab.com

Post reply on HN
Print view View original

1–10 of 325 posts

Re: Dear open-source maintainers, a letter from GitLab

#4

Post by filleokus »

It seems as the linked issue, for the "long list of suggestion", is being spammed or something?

https://gitlab.com/gitlab-org/gitlab-ce/issues/8938

I have never used GitLab myself, but some of the features mentioned in the article (like a true voting system) is something I've really longed for. Might have to reconsider trying out GitLab more.

Re: Dear open-source maintainers, a letter from GitLab

#5

Post by glandium »

Just for this, I'm tempted:

One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased.

The main thing keeping me from actually doing it is the network effect... and this:

Disadvantages

Right now GitLab.com is really slow and frequently down. This is because of fast growth in 2015.

Re: Dear open-source maintainers, a letter from GitLab

#6

Post by levlaz »

glandium wrote: post #5

Just for this, I'm tempted: One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased. The main thing keeping me from actually doing it is the network effect... and this: Disadvantages Right now GitLab.com is really slow and frequently down. This is because of f…

Very true, I think they are working very hard on improving the experience this quarter. Front page of HN probably does not help either. :)

Re: Dear open-source maintainers, a letter from GitLab

#7

Post by enimodas »

glandium wrote: post #5

Just for this, I'm tempted: One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased. The main thing keeping me from actually doing it is the network effect... and this: Disadvantages Right now GitLab.com is really slow and frequently down. This is because of f…

Only in the enterprise edition though.

Re: Dear open-source maintainers, a letter from GitLab

#9

Post by jbk »

With VideoLAN, we're not on github, but I believe we fit the 'large open source project' description. We host VLC, FFmpeg, x264 and quite a few related libraries.

For VLC and all related VideoLAN projects, we're moving to our own instance of GitLab hosted on our infrastructure.

And to be honest, it's quite good, but a few stuffs are ridiculously limited, to the point that some people in the community are resisting the change.

The first part is the groups and subgroups: it seems incredibly difficult to give sub-groups access to repos (like a team for iOS, one for Android, one for libVLC... but all are under the "videolan/" group). It seems there is a way with the EE, but not in the CE; and the current idea for the CE is to have sub-projects, which is not good, because it will make our URLs way more complex than needed.

The second part is the bugtracker/issues tracker. We use trac for VLC, and we want to leave it for something better; but gitlab issues is way too limited, even when using the templates. Especially, it seems to be impossible to add custom searchable fields (like "platforms", "priority" or "modules") which are very very useful to do queries. Also, there is no way to do custom queries and store them ("I want all the bugs for Windows, which are related to the interface modules").

If I remember correctly, this second part was also a complaint in the open letter to github.

Finally, it's not really related, since it's more a feature request, but we'd love to allow external people to fork our repos, but not create completely new ones (or have them validated) because we don't want to host any projects under the sun (there is github and gitlab for that). So far, you either allow both features or none of them.

PS: can we have custom landing pages and custom logo in the CE version? :D :D

Post reply on HN