Date: Fri, 06 Mar 2020 05:53:31 +0000
To: Drew DeVault <sir@cmpwn.com>, ~alpine/devel@lists.alpinelinux.org
From: Rasmus Thomsen <oss@cogitri.dev>
Reply-To: Rasmus Thomsen <oss@cogitri.dev>
Subject: Re: Does it make sense to keep ~alpine/aports running?
Message-ID: <dba6b9118dab0342eac8352fbcaddbd90a83c0d1.camel@cogitri.dev>
In-Reply-To: <C1371RU6KTBL.2M1PT8PA0ZN98@homura>
References: <C1371RU6KTBL.2M1PT8PA0ZN98@homura>
Feedback-ID: LZW2MXNaH7NSG88i8lGpebeqB0wmcl0-3TbzkSuzsmAwEQspn4GI-WRe8j3PhRL4SBmua4rQWq6fadPcLS5uxQ==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,

FWIW I think it doesn't take me longer than 5 seconds to open a MR
either due to the Gitlab API. Right now I just do:

git checkout -b branch
<do changes and commit>
mkmkr

And it creates a MR for me with the title, description etc. set. I'll
see with Leo if we can get that script so much up to speed that others
can use it without much effort too, so Gitlab can fit the "quickly send
changes" criterium too. Admittedly, it'll still be a little more effort
to make the first patch (one has to create an account/login via OAuth,
fork the repo and set an API key), but that doesn't take too long and=20
in return one gets the advantages I've noticed in my first email on
Gitlab.

Regards,

Rasmus Thomsen

On Thu, 2020-03-05 at 15:46 -0500, Drew DeVault wrote:
> It takes me almost no time to send a patch to the mailing list, under
> 5
> seconds every time. It's barely more work to send the patch than it
> is
> to update a package in the first place. Updating it on GitLab
> comparitively takes 5-10x longer - I have to make a branch, open my
> web
> browser, log in, push the branch, back to the browser, click a bunch
> of
> buttons... if the mailing lists are dropped then I'm probably going
> with
> it as a contributor.