Quoting kjones (kjo...@columbus.k12.nc.us):
> I own a piece of hardware that has an embedded system that appears to
> be based in whole on a variant of linux.
>
> The firmware became corrupted, and so I naively went to the company
> asking if I could have a copy of the firmware that shipped with
License compatibility is mostly an FSF-made and GPL-specific
doctrine. I can't see how it would make any sense for the OSI to
provide guidance on license compatibility beyond acknowledging (as the
OSI occasionally has done) the FSF's authority on the topic.
On Wed, Feb 15, 2017 at 10:46:39PM
Quoting Simon Phipps (webm...@opensource.org):
> There are certainly list members who are keen for us all to believe
> that without too much question.
Fortunately, a comfortable amount of difference does exist between
discussing of law in abstract terms -- even in great detail as to
its
On Wed, Feb 15, 2017 at 9:17 PM, David Woolley
wrote:
> On 15/02/17 16:58, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote:
>
>> Does OSI have a license compatibility chart for the various approved
>> licenses?
>>
>
> I would have thought that any such document would
On 15/02/17 16:58, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote:
Does OSI have a license compatibility chart for the various approved licenses?
I would have thought that any such document would constitute legal
advice, which is illegal for half the list members to provide, and the
other
> -Original Message-
> From: License-discuss [mailto:license-discuss-boun...@opensource.org] On
> Behalf Of Christopher Sean Morrison
> Sent: Wednesday, February 15, 2017 2:17 PM
> To: license-discuss@opensource.org
> Subject: Re: [License-discuss] [Non-DoD Source] Re: OSI equivalent
>
>
Got it. Thank you! The URL will be helpful in this case then.
Thanks,
Cem Karan
> -Original Message-
> From: License-discuss [mailto:license-discuss-boun...@opensource.org] On
> Behalf Of Kevin Fleming
> Sent: Wednesday, February 15, 2017 2:05 PM
> To: license-discuss@opensource.org
>
> I was afraid of that... and so is our Legal department :(. We want to issue
> good general guidance to everyone in our workforce, but at the moment that
> appears to be 'go talk with Legal'.
>
> As for the image by Dr. Wheeler, it doesn't seem to have come through; can
> you try resending
On 02/15/2017 11:05 AM, Kevin Fleming wrote:
I see the image in his email, so it was indeed sent out by the list
server. It must have been eaten by something on your end, unfortunately.
It might be best to send a URL to where it can be found instead.
http://imgur.com/a/Zr5Q3
JD
--
Unless
I see the image in his email, so it was indeed sent out by the list server.
It must have been eaten by something on your end, unfortunately. It might
be best to send a URL to where it can be found instead.
On Wed, Feb 15, 2017 at 10:35 AM, Karan, Cem F CIV USARMY RDECOM ARL (US) <
> -Original Message-
> From: License-discuss [mailto:license-discuss-boun...@opensource.org] On
> Behalf Of Christopher Sean Morrison
> Sent: Wednesday, February 15, 2017 1:06 PM
> To: License Discussion Mailing List
> Subject: [Non-DoD Source] Re:
> On Feb 15, 2017, at 11:58 AM, Karan, Cem F CIV USARMY RDECOM ARL (US)
> wrote:
>
> Does OSI have a license compatibility chart for the various approved
> licenses?
> Something similar to https://www.gnu.org/licenses/license-list.html ? Our
> researchers are
Does OSI have a license compatibility chart for the various approved licenses?
Something similar to https://www.gnu.org/licenses/license-list.html ? Our
researchers are pulling in code from all kinds of sources, and we want to keep
them out of legal hot water, and a compatibility chart would
13 matches
Mail list logo