You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stephen Colebourne <sc...@btopenworld.com> on 2004/01/02 03:31:17 UTC
[collections][lang] 2004
I am planning on running licence update scripts across [collections] and
[lang].
Any objections to the all file approach? Every file will get the same
copyright dates.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections][lang] 2004
Posted by Martin Cooper <ma...@apache.org>.
On Thu, 1 Jan 2004, Phil Steitz wrote:
> Stephen Colebourne wrote:
> > I am planning on running licence update scripts across [collections] and
> > [lang].
> >
> > Any objections to the all file approach? Every file will get the same
> > copyright dates.
>
> The guidlines here http://jakarta.apache.org/site/source.html
>
> say
>
> " Committers should update the copyright notice on the Apache License to
> include the current year when they revise a source file. If it is 2002,
> and you revise a source file from 1999, change the copyright notice in the
> license to cite "1999, 2002". If the file was from 2001, we would change
> it to 2001-2002. And so forth. This will happen most often in the early
> part of a year, but maintenance of the copyright date should occur
> year-round, as needed."
>
> That would indicate to me that what we should be doing is updating the
> notices when we change files. One thing that we probably do *not* want to
> do is to just replace the 2003 references with 2004, since that would make
> the files from 2003 look like their protection began in 2004.
>
> Is there an ASF policy on this?
I'm not aware of an ASF policy per se, but what you quote above is correct
according to (US and, I believe, UK) copyright law, and is what all of my
employers, past and present, have required.
--
Martin Cooper
>
> Phil
>
>
>
> >
> > Stephen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections][lang] 2004
Posted by steve cohen <sc...@javactivity.org>.
Aw, phooey.
I just changed the dates on all the commons-net classes. Wish I had seen
these instructions beforehand. On the other hand, with one exception they
all contained "2001", which, as far as I can recall, was before these classes
came under the Jakarta umbrella. If memory serves, they entered the Sandbox
in 2002 and Commons proper in 2003.
On Thursday 01 January 2004 09:14 pm, Phil Steitz wrote:
> Stephen Colebourne wrote:
> > I am planning on running licence update scripts across [collections] and
> > [lang].
> >
> > Any objections to the all file approach? Every file will get the same
> > copyright dates.
>
> The guidlines here http://jakarta.apache.org/site/source.html
>
> say
>
> " Committers should update the copyright notice on the Apache License to
> include the current year when they revise a source file. If it is 2002,
> and you revise a source file from 1999, change the copyright notice in the
> license to cite "1999, 2002". If the file was from 2001, we would change
> it to 2001-2002. And so forth. This will happen most often in the early
> part of a year, but maintenance of the copyright date should occur
> year-round, as needed."
>
> That would indicate to me that what we should be doing is updating the
> notices when we change files. One thing that we probably do *not* want to
> do is to just replace the 2003 references with 2004, since that would make
> the files from 2003 look like their protection began in 2004.
>
> Is there an ASF policy on this?
>
> Phil
>
> > Stephen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections][lang] 2004
Posted by Phil Steitz <ph...@steitz.com>.
Henri Yandell wrote:
>
> On Thu, 1 Jan 2004, Phil Steitz wrote:
>
>
>>notices when we change files. One thing that we probably do *not* want to
>>do is to just replace the 2003 references with 2004, since that would make
>>the files from 2003 look like their protection began in 2004.
>
>
> I assume we'd replace -2003 with -2004. So not a problem, then ([^-])2003
> with \12003-2004 perhaps to add those on.
And 2001, 2003, etc. The problem is that I am not sure that blast
updating when there is no change to the protected content is correct. I
am not a lawyer, but my understanding is that the last date in the
copyright notice should be the year when the content was last changed. I
am -0 to doing a blast update.
Phil
>
> Hen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections][lang] 2004
Posted by Henri Yandell <ba...@generationjava.com>.
On Thu, 1 Jan 2004, Phil Steitz wrote:
> notices when we change files. One thing that we probably do *not* want to
> do is to just replace the 2003 references with 2004, since that would make
> the files from 2003 look like their protection began in 2004.
I assume we'd replace -2003 with -2004. So not a problem, then ([^-])2003
with \12003-2004 perhaps to add those on.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections][lang] 2004
Posted by Phil Steitz <ph...@steitz.com>.
Stephen Colebourne wrote:
> I am planning on running licence update scripts across [collections] and
> [lang].
>
> Any objections to the all file approach? Every file will get the same
> copyright dates.
The guidlines here http://jakarta.apache.org/site/source.html
say
" Committers should update the copyright notice on the Apache License to
include the current year when they revise a source file. If it is 2002,
and you revise a source file from 1999, change the copyright notice in the
license to cite "1999, 2002". If the file was from 2001, we would change
it to 2001-2002. And so forth. This will happen most often in the early
part of a year, but maintenance of the copyright date should occur
year-round, as needed."
That would indicate to me that what we should be doing is updating the
notices when we change files. One thing that we probably do *not* want to
do is to just replace the 2003 references with 2004, since that would make
the files from 2003 look like their protection began in 2004.
Is there an ASF policy on this?
Phil
>
> Stephen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org