xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: Ian Murray <murrayie@yahoo.co.uk>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Alex Bligh <alex@alex.org.uk>,
	xen-devel@lists.xen.org
Subject: Re: [Hackathon Minutes] Xen 4.4 Planning
Date: Fri, 14 Jun 2013 15:55:57 +0100	[thread overview]
Message-ID: <a0ebfdeb6cf2e893bb0cf1774a029b53@mail.shatteredsilicon.net> (raw)
In-Reply-To: <1371221090.45091.YahooMailNeo@web171304.mail.ir2.yahoo.com>

 On Fri, 14 Jun 2013 15:44:50 +0100 (BST), Ian Murray 
 <murrayie@yahoo.co.uk> wrote:
> ----- Original Message -----
>> From: Ian Campbell <Ian.Campbell@citrix.com>
>> To: Ian Murray <murrayie@yahoo.co.uk>
>> Cc: Alex Bligh <alex@alex.org.uk>; "xen-devel@lists.xen.org" 
>> <xen-devel@lists.xen.org>
>> Sent: Friday, 14 June 2013, 14:55
>> Subject: Re: [Xen-devel] [Hackathon Minutes] Xen 4.4 Planning
>>
>> On Fri, 2013-06-14 at 14:34 +0100, Ian Murray wrote:
>>>
>>>  >>
>>>  >>  so where is this publically available repo?
>>>  >
>>>  > repo.flexiant.com/ ..., which is installed by default for anyone 
>>> using
>>>  > our binaries.
>>>  >
>>>  > You'll obviously have found:
>>>  > http://docs.flexiant.com/display/DOCS/Open+Source+Software
>>>
>>>  Nope. Still can't find a link from the main site.
>>>
>>>  Besides, I am not sure if providing source via a repo who's 
>>> address
>>>  isn't publically published is really complying with your
>>>  resposibilities, is it?
>>
>> Assuming you are referring to the responsibilities of the GPL you 
>> should
>> probably read the license (or at least do some basic investigation 
>> of
>> the terms) to see what it actually requires before making these 
>> sorts of
>> accusations.
>>
>> There are options for applying the GPL which don't require anything 
>> like
>> what you seem to expect. There's certainly no requirement for a link 
>> on
>> ones website when one uses GPL software.
>>
>> The text of the GPL is freely available. I strongly suggest you go 
>> read
>> it, it's not all that long nor is it particularly full of legalese.
>>
>> Accusing someone of a license infringement is rather a serious 
>> matter
>> and you really should make sure you know what you are talking about
>> before doing so.
>>
>> I think you are totally out of order hounding Alex like this.
>>
>>>   Again, not a lawyer, just IMHO.
>>
>> Lawyer or otherwise I think you would be well advised to keep your
>> opinions to yourself until you've actually read the license in 
>> question.
>>
>> Ian.
>>
>
> My understanding is that source should be made available in a
> reasonable format to any 3rd party if you distribute modified code
> that is licenced to you via the GPL. Do I have that wrong?

 IANAL, but:

 Reasonable format can mean anything. For example the kernel source
 for the Toshiba AC100 (ARM based Android laptop) was provided by
 Toshiba upon request on a CD by snail mail when those of us playing
 with the device requested it.

 If nobody is requesting the source, it arguably doesn't matter.
 But if somebody is asking for it, it must be provided. That's
 about the size of it as far as I can work out.

 Gordan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-06-14 14:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 14:00 [Hackathon Minutes] Xen 4.4 Planning Lars Kurth
2013-06-13 14:22 ` Jan Beulich
2013-06-13 15:11   ` George Dunlap
2013-06-13 15:30     ` Jan Beulich
2013-06-13 15:39       ` Ian Campbell
2013-06-17  8:27         ` Fabio Fantoni
2013-06-17  9:52           ` Ian Campbell
2013-06-13 14:31 ` Ian Campbell
2013-06-13 14:52   ` George Dunlap
2013-06-13 15:06     ` Ian Campbell
2013-06-14 17:41   ` Konrad Rzeszutek Wilk
2013-06-13 14:43 ` George Dunlap
2013-06-13 17:09 ` Ben Guthro
2013-06-13 18:07   ` Pasi Kärkkäinen
2013-06-13 21:03 ` Alex Bligh
2013-06-13 23:56   ` Ian Murray
2013-06-14  7:01     ` Alex Bligh
2013-06-14  9:46       ` Ian Murray
2013-06-14 11:53         ` Alex Bligh
2013-06-14 12:32           ` Ian Murray
2013-06-14 12:49             ` Alex Bligh
2013-06-14 13:34               ` Ian Murray
2013-06-14 13:55                 ` Ian Campbell
2013-06-14 14:44                   ` Ian Murray
2013-06-14 14:55                     ` Gordan Bobic [this message]
2013-06-14 15:00                       ` George Dunlap
2013-06-14 15:09                     ` Ian Campbell
2013-06-14 15:43                   ` Alex Bligh
2013-06-14 21:05                     ` Ian Murray
2013-06-19 21:22                     ` Alex Bligh
2013-06-14 15:44                 ` Alex Bligh
2013-06-14 17:25         ` Konrad Rzeszutek Wilk
2013-06-14  8:15   ` Jan Beulich
2013-06-14  9:47     ` George Dunlap
2013-06-14  9:59     ` Lars Kurth
2013-06-14 10:45       ` Jan Beulich
2013-06-14 11:19         ` George Dunlap
2013-06-14 11:30         ` Gordan Bobic
2013-06-14 12:10       ` Sander Eikelenboom
2013-06-14 10:44   ` George Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2013-06-14 11:46 Alex Bligh
2013-06-14 12:26 ` Jan Beulich
2013-06-14 12:45   ` Alex Bligh
2013-06-14 18:55 Alex Bligh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a0ebfdeb6cf2e893bb0cf1774a029b53@mail.shatteredsilicon.net \
    --to=gordan@bobich.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=alex@alex.org.uk \
    --cc=murrayie@yahoo.co.uk \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).