From: Hans de Goede <hdegoede@redhat.com>
To: Theodore Kilgore <kilgota@banach.math.auburn.edu>
Cc: linux-media@vger.kernel.org
Subject: Re: Licensing question regarding SN9C2028 decompression (fwd)
Date: Thu, 28 May 2009 20:16:14 +0200 [thread overview]
Message-ID: <4A1ED4EE.2040508@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0905280928540.3619@banach.math.auburn.edu>
On 05/28/2009 04:34 PM, Theodore Kilgore wrote:
>
>
> On Thu, 28 May 2009, Hans de Goede wrote:
>
>>
>>
>> On 05/27/2009 11:43 PM, Theodore Kilgore wrote:
>>>
>>> Hans,
>>>
>>> Here is the answer which I got about the question of GPL->LGPL licensing
>>> in regard to the sn9c2028 decompression code.
>>>
>>
>> Hmm,
>>
>> Given that you did have contact with the original author years ago and
>> he also did ok it back then, and that large parts of the code are written
>> by you, I'm ok with moving forward changing the license to LGPL and then
>> committing the patch.
>>
>> Regards,
>>
>> Hans
>
> If you think it is appropriate, I can include the mail as part of the
> file. I notice that this is done in some other files, for example in
> pac207.c.
Ack,
But given that you are one of the authors of the original code in this case,
and the mail isn't a 100% clear re-license permission, I think its best to
just change the license and be done with it, without including the mail,
I think if anything the mail will only lead to confusion.
> But as far as contact with the author is concerned, it is even
> more accurate to say that the cooperation was a two-way street. I
> understand that some of my LGPL code for other camera drivers has been
> put to use, too, in the macam project. For example, they also have
> drivers for the SQ cameras and the mr97310a cameras. Clearly, I do not
> have a problem with that any more than Harald has with my using the
> sn9c2028 decompression algorithm. In fact, as he called the
> decompression algorithm to my attention, I brought to his attention the
> work which I had done on those other cameras.
Ack, as said I think relicensing is fine.
> Sorry I did not keep all
> the e-mails, though.
>
No problem,
Regards,
Hans
prev parent reply other threads:[~2009-05-28 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 21:43 Licensing question regarding SN9C2028 decompression (fwd) Theodore Kilgore
2009-05-28 7:08 ` Hans de Goede
2009-05-28 14:34 ` Theodore Kilgore
2009-05-28 18:16 ` Hans de Goede [this message]
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=4A1ED4EE.2040508@redhat.com \
--to=hdegoede@redhat.com \
--cc=kilgota@banach.math.auburn.edu \
--cc=linux-media@vger.kernel.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