[PATCH app-transset] COPYING: make the content reflect the copyright statements in source code
Gaetan Nadon
memsize at videotron.ca
Fri Feb 3 14:47:57 PST 2012
On 12-02-02 09:13 PM, Daniel Forchheimer wrote:
> Hi Arnaud, Gaetan and Bart
>
> I wrote several patches for transset which I released as transset-df.
> I would suspect that around 50% of transset-df is my code, the rest
> was there from before (transSet.c in xapps) and a few lines have been
> send to me as patches to transset-df.
>
> When I started writing my patches the file transSet.c had the
> following in the header.
> By Matthew Hawn
> Use however you want. I can't stop you.
>
> I wanted to honor the original contributor and not impose anything
> stricter like GPL or even MIT so in my version it says:
> Licence: Use however you want.
If you are not sure how this can be interpreted and cannot afford a
lawyer :-), I recommend using the the X.Org preferred license. The
maintainer can add this license text in each source file and fill in the
year and the copyright holder name(s).
The X.Org Foundation has chosen the following format of the MIT License
as the
preferred format for code included in the X Window System distribution.
This is
a slight variant of the common MIT license form published by the Open Source
Initiative at http://www.opensource.org/licenses/mit-license.php.
Copyright ©[year] [copyright holder]
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"),
to deal in the Software without restriction, including without
limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice (including the
next
paragraph) shall be included in all copies or substantial portions
of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
>
> I don't know the legal status of such a message but my intensions and
> interpretation has been that I allow anyone to do any thing they want.
> No right of any kind is claimed. I can definitely say that: Permission
> is hereby granted, free of charge, to any person obtaining a copy of
> this software and associated documentation files (the "Software"), to
> deal in the Software without restriction, including without limitation
> the rights to use, copy, modify, merge, publish, distribute,
> sublicense, and/or sell copies of the Software, and to permit persons
> to whom the Software is furnished to do so, subject to the following
> conditions:
>
> Do let me know if there is anything else I need to do for Arnaud to be
> able to proceed. But really, he has my consent to do whatever he feels
> is necessary.
>
> Regards
> Daniel
>
> On Feb 1, 2012, at 9:49 AM, Bart Massey wrote:
>
>> Uh, if the code's keithp's or dstone's or somebody like that, just ask
>> them to fix it. They will likely respond both promptly and positively.
>> --Bart
>>
>> On Fri, Jan 27, 2012 at 7:42 AM, Gaetan Nadon <memsize at videotron.ca
>> <mailto:memsize at videotron.ca>> wrote:
>>> On 12-01-26 09:19 PM, Arnaud Fontaine wrote:
>>>> Hello,
>>>>
>>>> Gaetan Nadon <memsize at videotron.ca <mailto:memsize at videotron.ca>>
>>>> writes:
>>>>
>>>>> The author of the code should submit a patch to clarify his rights
>>>>> over the code. The X.Org <http://X.Org> preferred license
>>>>> can be found here:
>>>>> http://www.x.org/releases/X11R7.6/doc/xorg-docs/License.html#id2521948
>>>> That would be great indeed.
>>>>
>>>>> The role of the COPYING file is to reflect (or summarize) the
>>>>> copyright statements in the source code. Currently it is wrong. If
>>>>> this patch makes it correct, it should be applied. If and when the
>>>>> source code changes, the COPYING file would need to be updated again
>>>>> (business as usual).
>>>> I agree with you, but the patch you sent only reflects the
>>>> copyright
>>>> statements of a part of dsimple.{c,h}.
>>> So we agree in principle, what other Copyright statements have I missed?
>>> I admit I do not read each source file but I do a grep on "Copyright".
>>> If there are none, then that is the end of it.
>>>
>>> I don't search for missing copyright statements, typos, or for any
>>> comment that could be interpreted as a copyright like "public domain" or
>>> "do what you want". I don't know how to handle these or if they have any
>>> legal significance.
>>>
>>> That's the limit of my understanding :-)
>>>>
>>>> Regards,
>>>
>>> _______________________________________________
>>> xorg-devel at lists.x.org <mailto:xorg-devel at lists.x.org>: X.Org
>>> <http://X.Org> development
>>> Archives: http://lists.x.org/archives/xorg-devel
>>> Info: http://lists.x.org/mailman/listinfo/xorg-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20120203/cf85b5d7/attachment.html>
More information about the xorg-devel
mailing list