-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
A couple of questions.
1) can we please stop making source isos? the source is available in the source tree.
2) cloud WG wants to be able to produce updates images, what are our requirements to ensuring source compliance with the GPL?
Today the sources for livecds and appliance images are only in the source tree and not separated out. if we do updates images some sources will be in the base source tree and some in updates, however the updates sources will go away if the package gets another update. the only single source where we could point people at is koji.
Dennis
On Tue, Feb 11, 2014 at 06:52:01AM -0600, Dennis Gilmore wrote:
- can we please stop making source isos? the source is available in
the source tree.
IMO this ought to be tied to resolution of https://bugzilla.redhat.com/show_bug.cgi?id=1001394 and collateral issues as to which I owe spot some language.
- RF
On Tue, Feb 11, 2014 at 10:01:03AM -0500, Richard Fontana wrote:
On Tue, Feb 11, 2014 at 06:52:01AM -0600, Dennis Gilmore wrote:
- can we please stop making source isos? the source is available in
the source tree.
IMO this ought to be tied to resolution of https://bugzilla.redhat.com/show_bug.cgi?id=1001394
[....]
That bug has been closed but I have submitted a new bug against fedora-release https://bugzilla.redhat.com/show_bug.cgi?id=1096434
- RF
On Sat, May 10, 2014 at 10:43:08AM -0400, Richard Fontana wrote:
On Tue, Feb 11, 2014 at 10:01:03AM -0500, Richard Fontana wrote:
On Tue, Feb 11, 2014 at 06:52:01AM -0600, Dennis Gilmore wrote:
- can we please stop making source isos? the source is available in
the source tree.
IMO this ought to be tied to resolution of https://bugzilla.redhat.com/show_bug.cgi?id=1001394
[....]
That bug has been closed but I have submitted a new bug against fedora-release https://bugzilla.redhat.com/show_bug.cgi?id=1096434
Okay, given the resolution of this bug my view is we can stop making source isos.
- RF
On 05/10/2014 01:23 PM, Richard Fontana wrote:
On Sat, May 10, 2014 at 10:43:08AM -0400, Richard Fontana wrote:
On Tue, Feb 11, 2014 at 10:01:03AM -0500, Richard Fontana wrote:
On Tue, Feb 11, 2014 at 06:52:01AM -0600, Dennis Gilmore wrote:
- can we please stop making source isos? the source is available in
the source tree.
IMO this ought to be tied to resolution of https://bugzilla.redhat.com/show_bug.cgi?id=1001394
[....]
That bug has been closed but I have submitted a new bug against fedora-release https://bugzilla.redhat.com/show_bug.cgi?id=1096434
Okay, given the resolution of this bug my view is we can stop making source isos.
For the record, I concur with both the general compilation relicense and no longer making the source isos.
~tom
== ¸.·´¯`·.´¯`·.¸¸.·´¯`·.¸><(((º> OSAS @ Red Hat University Outreach || Fedora Special Projects || Fedora Legal
On Tue, Feb 11, 2014 at 06:52:01AM -0600, Dennis Gilmore wrote:
- cloud WG wants to be able to produce updates images, what are our
requirements to ensuring source compliance with the GPL?
Today the sources for livecds and appliance images are only in the source tree and not separated out. if we do updates images some sources will be in the base source tree and some in updates, however the updates sources will go away if the package gets another update. the only single source where we could point people at is koji.
I'm trying to understand the possible concern - why would pointing people at koji not be good enough?
- Richard
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 13 Feb 2014 11:26:54 -0500 Richard Fontana rfontana@redhat.com wrote:
On Tue, Feb 11, 2014 at 06:52:01AM -0600, Dennis Gilmore wrote:
- cloud WG wants to be able to produce updates images, what are our
requirements to ensuring source compliance with the GPL?
Today the sources for livecds and appliance images are only in the source tree and not separated out. if we do updates images some sources will be in the base source tree and some in updates, however the updates sources will go away if the package gets another update. the only single source where we could point people at is koji.
I'm trying to understand the possible concern - why would pointing people at koji not be good enough?
If ponting people at koji is good enough that's okay. The images will be made available somewhere on the download server and via mirrors say under /pub/fedora/linux/releases/21/Update1/Images/
but to get the sources you would need to either go to koji where only unsigned copies are easily available sometimes the only copy available. We do clean up the signed copy of older updates, we keep the signature header and can reattach it if needed. or you need to look through the Base release or updates source trees where the signed copy of the rpm will be available. With knowledge you can always get the source from git.
My concern is over how easily do we need to make the source available? does the source need to be available in the same location as the binaries? do I need to have a source tree at /pub/fedora/linux/releases/21/Update1/SRPMS/ for instance to match above do we need to add a README.Sources or similar file that points the user to where to get the sources or do we not need to do anything?
Dennis
On Thu, Feb 13, 2014 at 11:30:23AM -0600, Dennis Gilmore wrote:
If ponting people at koji is good enough that's okay. The images will be made available somewhere on the download server and via mirrors say under /pub/fedora/linux/releases/21/Update1/Images/
but to get the sources you would need to either go to koji where only unsigned copies are easily available sometimes the only copy available. We do clean up the signed copy of older updates, we keep the signature header and can reattach it if needed. or you need to look through the Base release or updates source trees where the signed copy of the rpm will be available. With knowledge you can always get the source from git.
My concern is over how easily do we need to make the source available? does the source need to be available in the same location as the binaries?
do I need to have a source tree at /pub/fedora/linux/releases/21/Update1/SRPMS/ for instance to match above do we need to add a README.Sources or similar file that points the user to where to get the sources or do we not need to do anything?
Add a README.Sources or similar file that points the user to where to get the sources. They don't have to be available in the same location as the binaries, but they have to remain available for as long as Fedora is making the images available (which I assume would be the case if you point people to koji).
You can assume that the reader of README.Sources (or whatever) has the technical skill and knowledge of an average Fedora packager.
- Richard
-
Dennis Gilmore -
Richard Fontana -
Tom Callaway