[Fedora-spins] Spins issue

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/01/2011 09:57 AM, Justin M. Forbes wrote:
> On Tue, Mar 01, 2011 at 08:47:50AM -0500, Paul W. Frields wrote:
>> As I was going through some email this morning I saw that the Spins
>> SIG is concerned that the Cloud SIG hasn't followed the Spins process
>> to get their "ec2" labeled Spin included in the spins-kickstart
>> collection in git:
>>
>> http://lists.fedoraproject.org/pipermail/spins/2011-March/001734.html
>>
>> If the Cloud group needs to see this Spin included in the F15 release,
>> then my recommendation is to start talking with the Spins SIG about
>> the process.  I believe there's a deadline that's passed, although you
>> can request an exception and still make it into the release.
>>
>> To the Spins SIG, I would also recommend keeping lines of
>> communication open if something goes wrong.  A Cc: to the cloud@ list,
>> for example, would help raise the issue to more people in a way that
>> would help reach a solution faster.
>>
> I suppose if that is what needs to be done, it can be.  In all honestly it
> never crossed our minds because we didn't seek to be a "spin", but that is
> where releng wanted to put our kickstart.  If it makes sense to be labelled
> as a spin, I am happy to do that.  I am ill today, but will look a the spin
> process as soon as I get a chance.
> 

I think this is where the confusion comes.  I would like to see
spin-kickstarts become the place to store "blessed kickstart files",
maybe with a change of names.  These kickstarts can  be used to create
different kinds of livecds.  Some of these are spins, but some of these
could be used as the basis for others building appliances or cloud images.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk1tGc4ACgkQrlYvE4MpobODPACfQs53uugpIYS55+2Ukrm497f0
3CkAoL4HLrc+Pc5zuf48N3r1WqIN2bsS
=MJ6n
-----END PGP SIGNATURE-----