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

[Robert Günzler]

On Sun Jun 7, 2020 at 11:15 PM CEST, Joonas Niilola wrote:
> In the end, we are *all* trying to make Gentoo better, right? I am
> thankful of every contribution, and this mailing list is low traffic at
> the moment. If Github is not an option, please don't let that stop you
> from contributing. You can of course send git-format patches directly to
> proxy-maint@g.o, too.

This 100%! To me that also includes not making the maintainers life
harder though...

> But I'm still interested about the discussion _why_ Github doesn't work
> for everyone. We can maybe find some new ideas or new ways, when we are
> aware of all the problems.

I honestly think it doesn't matter so much _why_ people prefer something else
over GH. How much are you considering to switch to yet another
solution after all... 
And I bet even that wouldn't make everybody happy :P

I'm fairly new to Gentoo, so I'm actually confused that https://packages.gentoo.org 
always links to https://cgit.gentoo.org/repo/gentoo.git - I thought that
is the "source-of-truth" place then... but patches are going into the GH
repo. Who is actually sycing all that back to cgit then?

Maybe a solution would be to make the review + dev workflows
independent of the git solution?

In response to me asking about https://sourcehut.org, in a recent thread 
you described your workflow:

On Sat Jun 6, 2020 at 12:57 PM CEST, Joonas Niilola wrote:
> 1: Open https://github.com/gentoo/gentoo/pull/16029
>
> 2: Launch a container with up-to-date ~ stage3,
>
> 3: "fullget.sh 16029" (a bash script to download
> https://patch-diff.githubusercontent.com/raw/gentoo/gentoo/pull/XXXXXX.pa=
> tch
> and apply it to containers portage tree)(fullget.sh, because there is
> another script to cherry-pick commits),
>
> 4: pkgcheck scan --commits,
>
> 5: depmerge.sh package (emerge -1av --onlydeps --with-test-deps "$@"),
>
> 6: testmerge.sh package (emerge -1av with
> https://wiki.gentoo.org/wiki/Package_testing#make.conf these settings),
>
> 7: If all is good, switch to desktop shell and ::gentoo repo, use "pram
> 16029" (https://packages.gentoo.org/packages/app-portage/pram)
>
> (I'm looking to automate steps 3-6 with one command)
>
>
> With e-mail patches, I have to copypaste them manually into container,
> and then apply them manually to ::gentoo repo one-by-one. It's not a lot
> extra work, but it slows down the process a bit. And reviewing
> contribution is a bit tedious compared to Github, especially if there is
> a big contribution.

How much value would there be for you, as a first iteration of a
solution, to get patches on the mailing-list automatically submitted as
a PR (done by a bot) on GH?

	robert