
I have been revising some code that claims // Copyright Paul A. Bristow 2006. // Use, modification and distribution are subject to 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) but now it is 2007 - (even though it seems like I wrote it yesterday ;-) I was tempteed to update // Copyright Paul A. Bristow 2007. but I then realised that this would imply that it was written in 2007, so if this date was to be used to squash some of the absurd software patent claims - for example see http://news.zdnet.com/2100-3513_22-6183437.html and many other comments on this, an issue that has re-surfaced again recently. I see an important side effect of software leaders like Boost is to preempt any attempt by companies to claim (or even threaten to claim) bogus patent rights by providing clear evidence of prior art. Do Boosters have any views on how we could or should be able to show date of writing? Is there going to be an archive of old releases by which we could establish a writing date? Or better is there going to be an archive of stuff *before* it gets reviewed and released (often at least a year earlier in the past and I doubt if it will get much less than a year even if we smarten up our act). Some of these claims go back a long time - a decade or so. Does the copyright claim date have any relevance to this? Should I write // Copyright Paul A. Bristow 2006 - 7. to show 1st date and developments? IANAL - still ;-) --- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539561830 & SMS, Mobile +44 7714 330204 & SMS pbristow@hetp.u-net.com

Hi! I've been told by some lawyer at some point that while "Copyright <name> 2006 - 2007" is clear enough, it's "better" (for reasons I don't understand, might have been told, but if so, forgot) to list each year separately, i.e. "Copyright <name> 2006, 2007". Also, there's no need to update copyrights unless you change the code. That is, if it's written in 2006 and hasn't been modified in 2007, no need to touch on the date. Having said that, I'm not really involved in boost development, so I can't speak for boost-specific preferences. -- Jens

Paul A Bristow wrote:
I have been revising some code that claims
// Copyright Paul A. Bristow 2006.
// Use, modification and distribution are subject to 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)
but now it is 2007 - (even though it seems like I wrote it yesterday ;-)
I was tempteed to update
// Copyright Paul A. Bristow 2007.
but I then realised that this would imply that it was written in 2007,
so if this date was to be used to squash some of the absurd software patent claims - for example see
http://news.zdnet.com/2100-3513_22-6183437.html
and many other comments on this, an issue that has re-surfaced again recently.
I see an important side effect of software leaders like Boost is to preempt any attempt by companies to claim (or even threaten to claim) bogus patent rights by providing clear evidence of prior art.
Do Boosters have any views on how we could or should be able to show date of writing? Is there going to be an archive of old releases by which we could establish a writing date? Or better is there going to be an archive of stuff *before* it gets reviewed and released (often at least a year earlier in the past and I doubt if it will get much less than a year even if we smarten up our act).
Some of these claims go back a long time - a decade or so.
Does the copyright claim date have any relevance to this?
Should I write
// Copyright Paul A. Bristow 2006 - 7.
to show 1st date and developments?
Usually we use: // Copyright Ada Lovelace 1815-1852 Which tends to establish prior art :-) Oh, OK, so you want a serious answer :-) Look at some boost source files, and you should see plenty in the above general format. But specifying individual years is fine too. BTW, One of the advantages of an open source control mechanism, is that we have a complete revision history, so who did what when should be pretty clear... not that that will necessarily stop all the chancers though :-( John.

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of John Maddock Sent: 22 August 2007 18:07 To: boost@lists.boost.org Subject: Re: [boost] How to claim copyright (and potentially claim priorart?)
Paul A Bristow wrote:
I have been revising some code that claims
// Copyright Paul A. Bristow 2006. Usually we use:
// Copyright Ada Lovelace 1815-1852
Which tends to establish prior art :-)
:-))
Oh, OK, so you want a serious answer :-) Look at some boost source files, and you should see plenty in the above general format. But specifying individual years is fine too.
BTW, One of the advantages of an open source control mechanism, is that we have a complete revision history, so who did what when should be pretty clear... not that that will necessarily stop all the chancers though :-(
Are we sure we/anyone could produce this in 10 years time? We've moved from Sourceforge - do we still have snapshots from the beginning of Boost-time? Paul --- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539561830 & SMS, Mobile +44 7714 330204 & SMS pbristow@hetp.u-net.com

Paul A Bristow wrote:
Should I write
// Copyright Paul A. Bristow 2006 - 7.
to show 1st date and developments?
I believe that the years in the copyright statement should reflect the dates when you made significant contributions to the file. Copyright 2003, 2004, 2007 <name> This basically claims that some portions of the file are copyright 2003 <name>, others are copyright 2004 <name>, and yet others are copyright 2007 <name>. You can use the shorthand 2003-2007 to indicate ongoing development, such as a company making regular changes to the file.
IANAL - still ;-)
Ditto.
participants (4)
-
Jens Finkhäuser
-
John Maddock
-
Paul A Bristow
-
Peter Dimov