Re: Proper Copyright Year in PHP files now an automated QA tasks

jojodee <jojodee-8nna1qhvBBM9QQeoy3GH/[email protected]>
Newsgroups gmane.comp.cms.xaraya.devel
Organization Xaraya
Message-ID <[email protected]>
We went through this some years ago when we updated the information on
copyright to DDF.

It should be date range.

So if a file content is changed in the current year, then the copyright
is updated:
eg

2004 becomes 2004 -2009
2004 - 2006 would become 2004-2009

Jo



St.Ego wrote:
> Copyright year is, technically, "year of first publication". The
> question would remain, however, if we should consider each (major?)
> revision to be a republication or recompilation. Technically speaking,
> any time you download from mt, you get a new revision based on any
> recent updates. Keeping the copyright year current, based on versioning,
> etc, may also be prudent.
> 
> Personally, I'm in favor of date ranges. That idea kicks ass simply
> because it helps illustrate our "maturity" as a project.
> 
> -St.Ego
> 
> Jason wrote:
>> Hb wrote:
>>   
>>> It is not needed and considered harmful to solely update the year without other
>>> codes changes in future.
>>>     
>>
>> Not only is it considered harmful - it is plain wrong. If the file is not
>> changed for other reasons, then the copyright remains on the year it was last
>> changed.
>>
>> I think it is even harmful to update the year to the current year when things
>> are changed. I suspect we need to put date ranges in:
>>
>> 2004 becomes 2004-2009
>> or perhaps: 2004,2009
>>
>> I'm not expert, so it would be an idea if someone could find out for sure.
>>
>> -- Jason
>> _______________________________________________
>> Xaraya_devel mailing list
>> [email protected]
>> http://xaraya.com/mailman/listinfo/xaraya_devel
>>   


-- 
http://xarigami.com :: Creative web development with Xaraya
http://2skies.com   :: Open source hosting and development
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.