The key to license compliance is to post the SRPMs corresponding to the bits in the image, concurrent with the image, and on the same lifetime, so people have the opportunity (not the requirement) to download the SRPMs when they download the image. If they choose not to download the SRPMs at that time, and you delete both the image and SRPMs concurrently, then the user is out of luck if they later decide they want the SRPMs, but it's not a violation on your part. -- Matt Domsch Technology Strategist Dell | Office of the CTO ________________________________________ From: infrastructure-bounces@xxxxxxxxxxxxxxxxxxxxxxx [infrastructure-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Matthew Miller [mattdm@xxxxxxxxxxxxxxxxx] Sent: Wednesday, November 14, 2012 8:37 AM To: Fedora Infrastructure Subject: Re: tools for building cloud images in the buildsystem On Wed, Nov 14, 2012 at 09:31:44AM -0500, Seth Vidal wrote: > >But we do for releases, from which all previous release images > >have been spun, AFAIK. The cloud SIG made sure of that quite > >early on in its lifetime to keep everything GPL-compliant, and it > >might be worth keeping in mind as we consider how to build images > >for future releases. > and I a pretty sure for releases we're talking about something else. > This is for continual/nightly image generation, unless I'm mistaken. I was thinking we'd generate the releases in the same way, but am willing to be disabused of that notion. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
