MIME-Version: 1.0
References: <24b91bd507e8151d41ac1d9866a4fd7a07febfe0.camel@cogitri.dev> <C1371RU6KTBL.2M1PT8PA0ZN98@homura>
In-Reply-To: <C1371RU6KTBL.2M1PT8PA0ZN98@homura>
From: Will Sinatra <wpsinatra@gmail.com>
Date: Thu, 5 Mar 2020 16:14:38 -0500
Message-ID: <CAJH62qngx01cLaXhTq3HSYOeL8sZzgL11H9PoFgCasLX2uY_tw@mail.gmail.com>
Subject: Re: Does it make sense to keep ~alpine/aports running?
To: Rasmus Thomsen <oss@cogitri.dev>
Cc: ~alpine/devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"

I've used it in the past as a contributor, and did find that the
patches I tried to send more or less went idle until I pinged someone
on IRC and explicitly asked for them to be reviewed. I switched to
Github, then Gitlab because I was specifically following the
example/trend set by the Alpine Devs, because I needed more
interaction and feedback to refine my own work.

I think Drew has a point though, if you want to fire off a patch and
forget, then the ML takes the least amount of time and effort to
contribute, and that's a benefit to some people.

On Thu, Mar 5, 2020 at 3:48 PM Drew DeVault <sir@cmpwn.com> 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.