Copyright and authorship notices
Hi all, what is the policy of adding a Copyright notice and entries to the author list when patching existing files? I found http://www.boost.org/development/requirements.html#Ownership, but it is not completely helpful. -- Jens
on Wed Jan 04 2012, Jens Müller <blog-AT-tessarakt.de> wrote:
Hi all,
what is the policy of adding a Copyright notice and entries to the author list when patching existing files?
I found http://www.boost.org/development/requirements.html#Ownership, but it is not completely helpful.
I don't think we have an official policy. My personal policy has always been that I don't add myself as an author for bug fixes, but for any "creative" work, I usually do. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Am 05.01.2012 02:39, schrieb Dave Abrahams:
I don't think we have an official policy. My personal policy has always been that I don't add myself as an author for bug fixes, but for any "creative" work, I usually do.
OK, and what about Copyright notices? Are they only for organizations? -- Jens
on Wed Jan 04 2012, Jens Müller <blog-AT-tessarakt.de> wrote:
Am 05.01.2012 02:39, schrieb Dave Abrahams:
I don't think we have an official policy. My personal policy has always been that I don't add myself as an author for bug fixes, but for any "creative" work, I usually do.
OK, and what about Copyright notices? Are they only for organizations?
No. The way I indicate authorship is by adding my name to the copyright. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Am 05.01.2012 03:24, schrieb Dave Abrahams:
on Wed Jan 04 2012, Jens Müller<blog-AT-tessarakt.de> wrote:
Am 05.01.2012 02:39, schrieb Dave Abrahams:
I don't think we have an official policy. My personal policy has always been that I don't add myself as an author for bug fixes, but for any "creative" work, I usually do.
OK, and what about Copyright notices? Are they only for organizations? No. The way I indicate authorship is by adding my name to the copyright.
Yeah, just found an example for this, boost/graph/adjacency_list.hpp: //======================================================================= // Copyright 1997, 1998, 1999, 2000 University of Notre Dame. // Copyright 2010 Thomas Claveirole // Authors: Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek, Thomas Claveirole // // Distributed under the Boost Software License, Version 1.0. (See // accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) //======================================================================= Thanks. -- Jens
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Dave Abrahams Sent: Thursday, January 05, 2012 1:40 AM To: boost@lists.boost.org Subject: Re: [boost] Copyright and authorship notices
on Wed Jan 04 2012, Jens Müller <blog-AT-tessarakt.de> wrote:
Hi all,
what is the policy of adding a Copyright notice and entries to the author list when patching existing files?
I found http://www.boost.org/development/requirements.html#Ownership, but it is not completely helpful.
I don't think we have an official policy. My personal policy has always been that I don't add myself as an author for bug fixes, but for any "creative" work, I usually do.
I think that this is a good policy (though I would widen the scope to all non-trivial bug fixes). It provides some element of history of modification (for a time when the SVN history might be lost) and some clues on who to ask when, years later, the reason for decision or changes is puzzling. And in the event of someone questioning patent 'prior art', it provides an additional person who can vouch for the authenticity and history of the software. This looks horribly likely to continue to be potentially important as the bogus software patent wars escalate. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
participants (3)
-
Dave Abrahams -
Jens Müller -
Paul A. Bristow