Merge of ayardley/upd_copyrights

Jonathan "Duke" Leto jonathan at leto.net
Mon Feb 27 22:21:35 UTC 2012


Howdy,

I must agree with Andy Lester. Here are our copyright updating guidelines:

1) When you start a new file, only the current year is put in the copyright
2) When you update a file, you should update the copyright year range,
so if it was 2007-2009, and you updated yesterday, that would become
2007-2012.
3) When the year changes, all files in parrot.git do not need their
copyrights updated. Only files that are actually touched should get
updated.

That being said, certain files, which *do* get updated all the time,
should have the latest copyright notices. For instance, when I run
"parrot --version", it still tells me it is copyright 2001-2011, which
is outdated.

Alvis, my suggestion is to reduce your changes to those that fall in
line with the above and create a new branch for it so people don't get
confused.

And thanks for working on this!

Duke

On Mon, Feb 27, 2012 at 12:59 PM, Alvis Yardley <ac.yardley at gmail.com> wrote:
> [Meant for parrot-dev]
>
> Coke, Andy, et.al.,
>
> I appreciate the quick feedback.  It's really not a problem, either way. I did
> the thing _thinking_ it was a good idea -- without discussing it on #parrot, I
> might add. That doesn't mean it was! :)
>
> And, fwiw, I probably have a fairly legalistic way of looking at copyright
> assertions, yada, yada. That is, more paperwork-shuffle, than functional and
> legally operative.
>
> Thanks.
>
> On Monday, February 27, 2012 at 15:34:27 (-0500), Will Coleda wrote:
>  >
>  > Based on conversations I've seen on perl5-porters, I'm not convinced
>  > this is necessary or worth the cycles... but that probably would have
>  > been a more useful statement to make before you wrote any code; sorry.
>  >
>  > --
>  > Will "Coke" Coleda
>
> --
> Alvis
>
> P.S. I'm very comfortable throwing it away.
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev



-- 
Jonathan "Duke" Leto <jonathan at leto.net>
Leto Labs LLC
209.691.DUKE // http://labs.leto.net
NOTE: Personal email is only checked twice a day at 10am/2pm PST,
please call/text for time-sensitive matters.


More information about the parrot-dev mailing list