Date: Tue, 10 Mar 2020 16:28:49 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Ariadne Conill <ariadne@dereferenced.org>
Cc: Drew DeVault <sir@cmpwn.com>, Rasmus Thomsen <oss@cogitri.dev>, Cosmo
 Borsky <me@cosmoborsky.com>, ~alpine/devel
 <~alpine/devel@lists.alpinelinux.org>
Subject: Re: Does it make sense to keep ~alpine/aports running?
Message-ID: <20200310162849.7a5bdebf@ncopa-desktop.copa.dup.pw>
In-Reply-To: <4c140756-b287-48a0-9d81-bc7421f72743@localhost>
References: <a1b36f583778cb14b50726289cb72a8d46b89d65.camel@cogitri.dev>
	<4c140756-b287-48a0-9d81-bc7421f72743@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 6 Mar 2020 12:35:33 -0500
Ariadne Conill <ariadne@dereferenced.org> wrote:
> > On Mar 6, 2020 at 8:23 AM, Drew DeVault  <sir@cmpwn.com>  wrote:  
> >  On Fri Mar 6, 2020 at 6:13 AM, Rasmus Thomsen wrote:  >  * No CI.
> > I see there's a todo for that in sr.ht and I don't mean to  >
> > disrespect anyone's efforts - sr.ht is a lot better than other ML
> > >  things for me already :), but we _still_ don't have CI on there,
> > > so I'm  >  not exactly hopeful that we'll get it soon. The ticket
> > > doesn't show much, but there has been consistent progress on this
> > > for some time now. Here's the current workstream:
> > > https://github.com/libgit2/pygit2/pull/982   
> 
>  A key point here that others have not raised is that this would
> require either moving the gitlab CI to use builds.sr.ht or
> maintaining two sets of CI.    I doubt either is truly worth it, as
> the alternate CI is probably less featureful in gitlab.

I asked in the #alpine-infra channel and they say that they don't have
the capacity or interest in either moving CI to build.sr.ht or run
double set of CI. We also don't have enough hardware for running two
sets of CI.

-nc