Conversation

Moving to GitLab will be a huge pain continuously, too. GitLab has a *HUGE* footprint with many moving parts. Most of my time will be taken just doing sysadmin tasks. My tiny little time available for hacking on code will be greatly diminished.
5
3
Replying to
Gerrit is easy to host. It covers code hosting + code review with a nice workflow for people without commit access to submit changes without having their own repositories on it. Recently explained why I like it here: twitter.com/DanielMicay/st Don't see a FreeBSD package though.
Quote Tweet
Replying to @DanielMicay and @CecileTonglet
The Gerrit workflow is that you make your commits and push them to the upstream repository without needing commit access via `git push gerrit HEAD:refs/for/<BRANCH>`. Commits get a Change-Id and pushing again will update your changes. Also nice for tracking backported patches.
1
1
Replying to
I have a feeling it works fine without changing any of the code. I think you would just need to deal with setting up the user/group, directories, init script, etc.
1
Replying to and
It's really good at handling large repositories and I expect you'll have major issues with almost anything else. There's a reason all those huge projects adopted it instead of it remaining an AOSP thing. I don't think GitLab will work well.
1
Replying to
TBH, I don't think anything will work well. Hipsterism development practices assume large amounts of resources and $$$ to throw at a problem. And also assume hosting on Linux.
1