Because the thread has turned into a "why I like/dislike GitLab over GitHub", I'll say one thing that keeps sending me back to GitHub is the neat-o desktop client. I use a command line for everything else in life; but with Git I'm hopeless.
Dear open-source maintainers, a letter from GitLab
51–60 of 325 posts
Re: Dear open-source maintainers, a letter from GitLab
#52Github OTOH has an extremely usable mobile UI.
Re: Dear open-source maintainers, a letter from GitLab
#53Earlier quoted context omitted.
> 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"). Isn't this use-case covered by Gitlab's issue labels?
If you have to create a label for every platform you support and every existing priority and module, the labels list will become really cluttered, making it hard to find things.
Re: Dear open-source maintainers, a letter from GitLab
#54Their issue tracker seems really busy atm: https://i.imgur.com/Iv46xnx.png
udaiso03: https://archive.is/jZFbR NSFW!
bamwar10: https://archive.is/HeWvt
opmania35: https://archive.is/jNEr2 NSFW!
Re: Dear open-source maintainers, a letter from GitLab
#55Re: Dear open-source maintainers, a letter from GitLab
#56Re: Dear open-source maintainers, a letter from GitLab
#57The only question left is if your servers are powerful enough to run gitlab. Maybe I'll sacrifice a goat for some new server hardware and 256GB of ram.
Re: Dear open-source maintainers, a letter from GitLab
#58Earlier quoted context omitted.
Actually, that will not happen.
What? Listening to the developers?
Re: Dear open-source maintainers, a letter from GitLab
#59Earlier quoted context omitted.
Just yesterday I ended up implementing my own mirroring of GitHub repositories. GitLab supports this in EE (new in 8.3), but not CE. That's not a feature that only large enterprises use–I run an open source GitHub organization and wanted to use GitLab as CI. It works! But I needed to reimplement an EE feature to do it. To be clear, I don't think there is anything sinister about keeping features behind a paid firewall…
> I run an open source GitHub organization and wanted to use GitLab as CI. It works! But I needed to reimplement an EE feature to do it. Is there a reason why you didn't use GitLab.com, which runs EE and thus has Repository Mirroring? > I'm just saying that the EE features are not all "mostly interesting to companies with 100+ employees." Several of them are things I needed as a single open-source developer. Fair eno…
1. My hosting is way more reliable than yours :-)
2. I need to host the CI runners myself anyway, because you don't have the right config
3. I already have a private GitLab install, so it's no extra trouble
4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly
5. I prefer to have a commercial relationship with important tools. You seem like nice people, let's see what happens when you get acquired. As long as you can't be bothered to sell to 2-person teams, I'll just run CE and have my commercial relationship with AWS instead.
Re: Dear open-source maintainers, a letter from GitLab
#60Because the thread has turned into a "why I like/dislike GitLab over GitHub", I'll say one thing that keeps sending me back to GitHub is the neat-o desktop client. I use a command line for everything else in life; but with Git I'm hopeless.