On Mon, Aug 01, 2011 at 02:07:14PM -0700, Jesse Keating wrote: > On Aug 1, 2011, at 1:45 PM, Robyn Bergeron wrote: > > > > http://fedoraproject.org/wiki/Legal:Trademark_guidelines#Virtual_images_or_appliances_with_unmodified_Fedora_software > > > > "It is permissible to use the Fedora Trademarks without prior permission > > in connection with the provision and sale of virtual images or appliance > > distributions pre-loaded with Fedora software, provided that..." > > > > Fedora on EC2 complies with all of this. So I'm ... puzzled, I suppose, > > as to why I'm running around trying to have an "officially sanctioned" > > test day, some sort of signoff sheet, and blessing by release > > engineering, for an image that the SIG itself is entirely capable of > > creating in 5 minutes now, and obviously would test anyhow because > > people take pride in what they do, etc. > > The concern is probably how the preloading is being done, and if we start offering it now, will we continue offering it in the future, and should it be a releng task to get them uploaded at the same time we do the rest of the release. The preloading is being done using strictly tools that are already a part of Fedora. And, while the goal is to move the image generation to releng, the reality is releng is using tools that the community cannot really use. As a result, we will have to maintain this image process through all releases anyway. The cloud SIG will be maintaining the appliance spec in the cloud-kickstarts git repo for all future releases. As for the actual generation/upload, we are down to less than an hour to get all of the images up for each availability region, and only 5 minutes of that is interactive time at the command line. I am all for migrating to a full releng run process, but don't think there is any reason to block on it personally. Migrate when it is ready and tested. Justin _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
