Hi, As a user, I agree that Gerrit isn't user friendly nor easy to use. The interface is ugly and understanding how it works when you never used it is a bit a pain. I used Gitlab multiple times and I prefer it. It's more user friendly, easier to use and it offers an easy way to navigate through repositories.
Using gitlab.com could be a good idea as we don't need to maintain the gitlab ourself but having our own gitlab looks better has we have a full hand on it (it's just a pain to maintain from what I heard). Sincerely, Kendos-Kenlen Le mer. 21 déc. 2016 à 13:54, Irvin Choi <[email protected]> a écrit : > I would like to follow up what Somasis has said in the last email. I > currently do have a GitLab server, mirroring Exherbo's git servers > intending to create a mirror for faster git access for Exherbo users. I > submitted a patch about adding this to Eherbo website few months ago (might > be less or more) but was not approved. If anyone is interested, I am > willing to provide server for gitlab for Exherbo community. I've made this > proposal to philantrop, but he has denied my proposal stating that gerrit > will be used instead. Although it is not my intention to bring this up as a > way to dismiss philantrop's wishes, I am generally curious about what > others (including developers), think about replacing Gerrit with gitlab. I > own a VPS with NGINX server, so that is not much a problem for me. > > Thanks! > Simdol > > On Wed, Dec 21, 2016 at 9:00 PM, <[email protected]> > wrote: > > Send Exherbo-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.exherbo.org/mailman/listinfo/exherbo-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Exherbo-dev digest..." > > > Today's Topics: > > 1. Re: To Gerrit or not to Gerrit ... (Kylie McClain) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Dec 2016 21:43:47 -0500 > From: Kylie McClain <[email protected]> > To: [email protected] > Cc: [email protected] > Subject: Re: [Exherbo-dev] To Gerrit or not to Gerrit ... > Message-ID: > < > caoji9tdypvppiamdlhudg6hfnsjex53ainnhzwwlqvdhcl5...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Sun, Dec 18, 2016 at 2:03 PM, <[email protected]> wrote: > > Hi, > > > > Wulf: I am not trying to step on your work, let me know if you think it > > should be done otherwise > > > > We are currently in the situation that the main place for our code > reviews > > is gone which is unfortunate. I would like to put in some work to change > > that, preferably in a way where multiple "sys-admin" Exherbo developers > can > > help each other maintain it. > > > > Since Gerrit is not the easiest piece of software to setup/maintain and > > since I personally do not prefer the Gerrit workflow (making it as hard > as > > possible to work on a branch of commits and creating a tendency for devs > to > > create large commits to make it easier for the review process) I would > like > > to ask if you think: > > > > - We need Gerrit back > > > > or > > > > - We need a place to help review code > > GitLab.com might be an option. > > Pros: > - We put maintenance of code review infrastructure on another group > - Open-source (MIT/expat license), so we can self-host if we want to > - Has a lot of integration plugins already implemented; Jenkins, Irker... > - Has two-way mirroring like Gerrit > - Allows for three different merge request workflows (merge commits > vs. rebasing); this is useful for how Paludis' repo is maintained > since merge commits are common on it, but our repos use rebasing > - Has options for only letting merge requests be merged if they pass tests > - Repositories, issues, etc. can be exported if we ever want to self-host > - Has many login options: GitHub, Google, Twitter, BitBucket > > Cons: > - We put maintenance of code review infrastructure on another group, > so if they go down for a bit, we lose code review functionality > - CLI clients are a little lacking (however > https://github.com/numa08/git-gitlab looks promising imo) > - You could argue that the public instance (GitLab.com) is a little > slow in terms of response speed at times. > > That said, self-hosting is an option. I was at first thinking we could > do that, but then maintaining it on my VPS came to be a bit of a > hassle (mostly due to them recommending nginx, and I want to use > lighttpd...). Plus, GitLab.com is already here, it requires less set > up or maintenance on our part, and so far they've been pretty good > with uptime. They upgrade to the newest GitLab release on the 22nd of > every month, they announce maintainence periods, and overall I think > it's better than something like GitHub for the fact that it's > open-source and we aren't as locked in to one vendor as we would be if > we used them. > > Thoughts? In the mean time I created a group on GitLab.com at > https://gitlab.com/exherbo so we can test it a little if desired; just > ask me to add you to the group if you want to. > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Exherbo-dev mailing list > [email protected] > http://lists.exherbo.org/mailman/listinfo/exherbo-dev > > > ------------------------------ > > End of Exherbo-dev Digest, Vol 103, Issue 4 > ******************************************* > > > _______________________________________________ > Exherbo-dev mailing list > [email protected] > http://lists.exherbo.org/mailman/listinfo/exherbo-dev >
_______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
