Date: Wed, 16 Dec 2020 16:28:43 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Mike Crute <mike@crute.us>
Cc: Ariadne Conill <ariadne@dereferenced.org>,
 ~alpine/devel@lists.alpinelinux.org, tomalok@gmail.com
Subject: Re: [3.14] Release process change proposal: Add official Alpine
 Linux cloud images
Message-ID: <20201216162843.450affb9@ncopa-desktop.lan>
In-Reply-To: <20201215163719.GB1500235@crute.us>
References: <134020455.7nPEQRCJ1u@nanabozho>
	<20201215030452.GA359703@crute.us>
	<25544517.Nm2VenqIb5@nanabozho>
	<20201215163719.GB1500235@crute.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 15 Dec 2020 08:37:19 -0800
Mike Crute <mike@crute.us> wrote:

> On Tue, Dec 15, 2020 at 06:07:59AM +0000, Ariadne Conill wrote:
> >> I started the community images that you are referring to and am one 
> >> of the maintainers of them. I completely support pulling these into 
> >> the upstream Alpine project and treating them as official release. I 
> >> would be happy to assist in doing that and, with my co-maintainers, 
> >> continuing to maintain and release them as part of the Cloud team 
> >> going forward.  
> >
> > Yes, this is basically the idea I had in mind after talking to you 
> > about it on IRC.  I would prefer to see you lead this new team in 
> > fact, since you're already producing the community images anyway.  
> 
> That works for me. I'm happy to lead the cloud team and to get these 
> images pulled into Alpine proper. I've spoken with my co-maintainer and 
> he's onboard as well.

Awesome!
 
> >> We've been primarily focused on stability and feature completeness 
> >> for AWS at this point and I think we're on good footing there. I'd 
> >> recommend releasing those images as official as soon as reasonably 
> >> possible, then we can start to investigate the work that would be 
> >> required to begin adding support for other clouds. This would also 
> >> put us into a good position to advertise the images on the AWS 
> >> marketplace as official Alpine images and to make the case for the 
> >> removal of the existing, predatory, images.  
> >
> > Right that is my hope that we can have this for 3.14, and thus put 
> > that $2500/ year image out of business.  I think it is something 
> > achievable.  Obviously getting something together for 3.13 is not 
> > doable, since we are already close to release.  
> 
> What makes this not doable for 3.13? If we can have images ready the day 
> or week of the 3.13 release, would that make this workable? I'm happy to 
> start getting things ready for a migration in 3.14 but would prefer, if 
> possible, to get these officially released sooner rather than later.

The only thing is that we are already late with 3.13 release and we
want avoid anything that delays the release. But if can manage to
on-board you to the Alpine infra team and you can do the glue, then I
don't see anything preventing it for 3.13.

 
> >> I've opened issues in our GitHub project [0] to begin research on the 
> >> other items you've mentioned.
> >>
> >> [0] https://github.com/mcrute/alpine-ec2-ami/issues  
> >
> > We will probably want to move the github repo into the Alpine gitlab, 
> > but for now, we can work through issues over on github until the 
> > necessary infrastructure begins to be set up.  
> 
> Agreed. I suggest that we work in parallel to get the Alpine infra setup 
> and then migrate everything over. Until that's ready we'll continue to 
> work on GitHub.
> 
> ~mike