Re: [gentoo-proxy-maint] Posting patches on this mailing list instead of using GitHub

[Haelwenn (lanodan) Monnier]

[2020-06-07 10:01:43+0300] Joonas Niilola:
> On 6/7/20 2:45 AM, Ralph Seichter wrote:
> > Still, I wonder why patches are posted here instead of using GitHub,
> > because there is no public review process going on. To me, email-based
> > patches on the Gentoo Proxy Maintainer mailing list are at best mildly
> > annoying, and at worst an attempt at jumping the queue, i.e. to get
> > one's changes processed faster than those made through GitHub. They
> > also, in my perception, have a smell of "ooh, look at me, I am working"
> > about them.
>
> I also wonder that. Especially when I know some of the contributors DO
> use Github. If you've read this list, you know my feelings about this
> subject.
>
> The automated CI check is a huge plus for both parties, and when I think
> about it, the time spent should be rather equal whether you choose
> git-send-email or git push. But the review and the 'fixing' part is
> definitely cleaner with git push.
>
> Now to your last sentence, I don't believe it's a matter of "attention
> seeking", but more some disgust towards Github. But I'd also like hear
> what's this all about. Would Gitlab be better than Github due to principles?
>
> -- juippis

Since I'm the one which does send patches through email on proxy-maint:

- It's not to jump the queue, in fact I get about the same lag in my 
experience between GitHub PRs and using email. But it's much less predictable.

- I'd rather avoid GitHub completely, I do use it from time to time but because 
I have to.

And while sending via GitHub sometimes works I also got at least one PR later 
reverted because it didn't get a proper ACK from the maintainers, if I have to 
also ping them through email, why not just send the patch via email?
Specially as metadata.xml already gives me the emails.

There is also the problem of having to sync your repo to GitHub, 
if I forget to push gentoo's master to my fork I end up having to send all 
the past history manually, and I discovered this one quite later on.
This was a huge pain when I only had the choice between a slow connection or 
a metered one.
Also see https://forgeperf.org/ for how slow GitHub can get as just a web view.

Finally, I don't have this issue but github isn't available to everyone 
depending on where they live, and often a VPN isn't an option there, 
so another option needs to exists.

Best Regards,