Hi Guys,
I am a bit fed-up to have to receive Neels non-productive mails every single day and given my tight work schedule let's have him win, declare Gerrit a failure and return to patchwork.
The twist is that I am no longer willing to clean behind everyone on the patchwork UI. So somebody else needs to sign-up for the patch merging and gardening in the WebUI.
My proposal would be:
* Sunday morning we change all ACLs (no more pushes, no more merges/submits/reviews) * Luckily we have all patches in our patchwork and can continue from there.
agreed?
holger
Hi.
I don't think hasty decisions would benefit anyone. Personally I favor gerrit over patchwork because it's easier for me to grab particular patch, fix it and than send back for review with gerrit taking care of versioning, jenkins (re)test etc. I also have an impression that gerrit gives better overview of awaiting patches which decrease the chance that some patch would be "lost" in ML.
On Jun 1, 2016, at 12:01 PM, Max msuraev@sysmocom.de wrote:
Hi.
I don't think hasty decisions would benefit anyone. Personally I favor gerrit over patchwork because it's easier for me to grab particular patch, fix it and than send back for review with gerrit taking care of versioning, jenkins (re)test etc. I also have an impression that gerrit gives better overview of awaiting patches which decrease the chance that some patch would be "lost" in ML.
+1
If you're not going to be convinced to transition to evil proprietary closed software, Gerrit is pretty nice for patch submitters and does seem to offer good CI integration and overviews.
There are some serious advantages to GitHub, beyond ease of use and efficiency though.
You can see where we transitioned (Early 2010) from just mailing list patches to using GitHub.
https://www.openhub.net/p/freeradius (See contributors Per Month graph)
-Arran
Arran Cudbard-Bell a.cudbardb@freeradius.org FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
On Wed, Jun 01, 2016 at 02:29:05PM +0200, Holger Freyther wrote:
Hi Guys,
I am a bit fed-up to have to receive Neels non-productive mails every single day and given my tight work schedule let's have him win, declare Gerrit a failure and return to patchwork.
Let's have this on a non-personal level, and let's have consensus. I don't win either way. My goofiness of handling gerrit should not be too relevant. If dropping gerrit means losing your reviews, my choice is to keep gerrit.
Secondly, it's not your personal responsibility to resolve my gerrit problems. There's others around in the internet too. If your schedule is tight, please don't bother with that! I'm posting to openbsc@, not hfreyther@.
It seems we won't get branch reviews smoothed out, but by far most of our work is indeed single patch submission. And we've discussed/resolved pretty much all other problems so far.
I know that Lynxis and others like gerrit. Even if consensus to drop gerrit converges, IMHO sunday would be too soon. Let's have other people's opinions first.
~Neels
Hi Holger,
On Wed, Jun 01, 2016 at 02:29:05PM +0200, Holger Freyther wrote:
I am a bit fed-up to have to receive Neels non-productive mails every single day and given my tight work schedule let's have him win, declare Gerrit a failure and return to patchwork.
Pleaes don't, it will just be more confusing and fragment our developments further.
I actually come to like gerrit quite a bit. However, that's mostly as a reviwer. I will be pushing plenty of changes to gerrit over the next few days, so I will also know the pleasure of branches / patchets.
I understand there are issues, but as Neels has alsso pointed out, let's not be too quick. We can still decide to go back after another 1-2 months or so.
-
Arran Cudbard-Bell -
Harald Welte -
Holger Freyther -
Max -
Neels Hofmeyr