On 24 November 2015 at 03:22, Barry Warsaw
On Nov 23, 2015, at 10:20 AM, Victor Stinner wrote:
It would allow us (Python) to own our data (reviews), rather than relying on a private provider like Gitlab (I don't know if Gitlab can be used completly freely on our own server).
It can. The community edition is completely open source and the enterprise edition probably doesn't have features we'd miss.
The feature comparison chart is at https://about.gitlab.com/features/#compare Some of the richer review workflow features are only in the Enterprise edition (including the ones that let you make GitLab a bit more like Gerrit, by requiring multiple sign-offs, rebasing merge requests through the web UI, etc), but I agree we could ask GitLab to offer us a Community Edition instance without missing anything critical. That said, one we should get clarified is the "git hooks" feature. Since hook processing is handled by git rather than GitLab, I *think* that feature just refers to the web UI [1] linked from the features page for defining certain hooks without having to write the relevant scripts yourself, but we should get that clarified explicitly (since we're still going to want to run pre-receive hooks like the indentation checking one and the whitespace one, even if we also have those checks automated in pre-merge CI). Cheers, Nick. [1] http://doc.gitlab.com/ee/git_hooks/git_hooks.html -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia