#49: Spins Process for Cloud Images ---------------------+-------------------------------- Reporter: red | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Keywords: meeting ---------------------+-------------------------------- So, according to ausil, we're supposed to follow the standard Spin Process to create additional cloud products. Are we okay with that or do we want to cause some ruckus? :) It seems the process is also used by e.g. the (kinda special) ARM images, etc.
For reference: http://fedoraproject.org/wiki/Spins_Process
#49: Spins Process for Cloud Images ---------------------+--------------------------------- Reporter: red | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Resolution: Keywords: meeting | ---------------------+--------------------------------- Changes (by mattdm):
* cc: cwickert (added)
Comment:
I guess we can go forward with it and raise a ruckus if we hit problems. Mostly, it looks like we shouldn't have any. I don't think the guidelines all apply exactly, though -- we don't want these on the 'spins' download page, as that will just confuse people.
I guess we should ask Christoph, as spins wrangler, what he thinks.
#49: Spins Process for Cloud Images ---------------------+--------------------------------- Reporter: red | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Resolution: Keywords: meeting | ---------------------+---------------------------------
Comment (by mattdm):
You know, this has one huge advantage. I keep accidentally referring to our cloud image variants as "spins". Making them _actually_ spins would remove the need to come up with a new term. :)
#49: Spins Process for Cloud Images ---------------------+--------------------------------- Reporter: red | Owner: Type: task | Status: closed Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Resolution: fixed Keywords: meeting | ---------------------+--------------------------------- Changes (by red):
* resolution: => fixed * status: new => closed
Comment:
Discussed at our meeting today and we do agreed to go with the spins process as proposed. Figure we'll notice how well that works for images (for which it wasn't originally intended) as we move forward. jzb will open separate tickets for each planned image to follow the process.