Spins issue
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. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Spins SIG meetings starting up again
We are going to try to get Spins SIG meetings going again on Mondays at 20:00 UTC (this may change once DST is in play) in #fedora-meeting-1. If you guys are still interested in either having an ISO published or having a ks file included in the spin-kickstarts package, it would be good to have someone from Cloud SIG attend. While technically this is past the deadline, I think it is likely that exceptions will be made for spins that have been actively being developed while Spins SIG was in remission. Having someone join the spins list (if no one currently is) to keep an eye on updated information would also be a good idea. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Spins issue
On Tue, Mar 1, 2011 at 8:47 AM, Paul W. Frields sticks...@gmail.com 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: I've talked to Dennis about this already, and this was simply a miscommunication on his part. As we're moving towards having Koji generate the release images for EC2, he needed a place to store the EC2 kickstart file so that it was public and being tracked in revision control, and so that Koji could pull the kickstart file when it generated the images. As I understand it (and I'm sure Dennis will correct me if I'm wrong), Koji can either pull from packages.fedoraproject.org or from the spins git repo. So, to make a long story short, Dennis put the EC2 kickstart file in the spins git repo out of convenience. He wasn't trying to say that EC2 was a spin. I've got to admit that I never saw the EC2 images as being a spin per se, but that's certainly a discussion we can have going forward. As I re-read through the Spins guidelines, it's still not clear to me how this would even qualify as a spin -- it's really a different animal than our traditional spins. At the same time, I think it needs a lot of the same process for review, oversight, and QA that we currently have in place for spins, so there might be some ability to roll the cloud images into the spins concept. I'm certainly open to comments and suggestions either way. -- Jared Smith Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Spins issue
On Tue, Mar 01, 2011 at 11:20:52AM -0500, Jared K. Smith wrote: On Tue, Mar 1, 2011 at 8:47 AM, Paul W. Frields sticks...@gmail.com 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: I've talked to Dennis about this already, and this was simply a miscommunication on his part. As we're moving towards having Koji generate the release images for EC2, he needed a place to store the EC2 kickstart file so that it was public and being tracked in revision control, and so that Koji could pull the kickstart file when it generated the images. As I understand it (and I'm sure Dennis will correct me if I'm wrong), Koji can either pull from packages.fedoraproject.org or from the spins git repo. So, to make a long story short, Dennis put the EC2 kickstart file in the spins git repo out of convenience. He wasn't trying to say that EC2 was a spin. I've got to admit that I never saw the EC2 images as being a spin per se, but that's certainly a discussion we can have going forward. As I re-read through the Spins guidelines, it's still not clear to me how this would even qualify as a spin -- it's really a different animal than our traditional spins. At the same time, I think it needs a lot of the same process for review, oversight, and QA that we currently have in place for spins, so there might be some ability to roll the cloud images into the spins concept. I'm certainly open to comments and suggestions either way. OK, thanks for this explanation. At the time it wasn't clear why the kickstart file was coming to the spins-kickstart repo. If there was a need for it to be there, then I wanted to see the teams involved get into a conversation about it. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
