On 2/27/12 3:59 PM, Alvis Yardley 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.


You might also want to glance at t/codingstd/copyright.t. This tests for the presence of copyright statements -- in a specific format -- in a large subset of our source code.

(There are a few oddball cases where someone other than Parrot foundation is listed as copyright owner.)

This test file doesn't, however, test for recency of copyright date, i.e., whether the copyright for a file that was created before 2012 and modified in 2012 has been updated to: *-2012. I haven't looked at your branch, but it would be great to have your program test for recency as per the copyright policy cited by Duke.

Thank you very much.
Jim Keenan
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev

Reply via email to