Using gerrit or github for review?

[Alexey Brodkin]

Hi Simon,

> -----Original Message-----
> From: U-Boot <u-boot-bounces at lists.denx.de> On Behalf Of Simon Glass
> Sent: Monday, July 13, 2020 9:26 PM
> To: U-Boot Mailing List <u-boot at lists.denx.de>
> Cc: Tom Rini <trini at konsulko.com>; Bin Meng <bmeng.cn at gmail.com>; Masahiro Yamada
> <yamada.masahiro at socionext.com>; Heinrich Schuchardt <xypron.glpk at gmx.de>; Marek Vasut
> <marek.vasut at gmail.com>; Vignesh R <vigneshr at ti.com>; Michal Simek <michal.simek at xilinx.com>; Igor
> Opaniuk <igor.opaniuk at gmail.com>; Heiko Schocher <hs at denx.de>; Fabio Estevam <festevam at gmail.com>;
> Jagan Teki <jagan at amarulasolutions.com>
> Subject: Using gerrit or github for review?
> 
> At present U-Boot uses the mailing list for patch review. What do
> people think about trying out geritt or github for this? I'd be
> willing to do a trial with the -dm mailing list.
> 
> My idea is that patman would email out the patches and also upload
> them to one of these systems. With geritt, emails are sent every time
> there is a review, but for github I'm not sure.

From my experience Gerrit's code-review interface is much less
human-friendly as compared to GitHub. Also GitHub has "Issues" which
are nicely integrated with "Pull-requests".

One good example you may look at is Zephyr RTOS, see
https://github.com/zephyrproject-rtos/zephyr/. They do use GitHub features
quite extensively.

But given U-Boot git repos are already hosted in GitLab instance why not
consider it instead of either GitHub or Gerrit? Review and issues are already
there as well as some other fancy features. Or I'm missing the main point of
the question?

-Alexey