> -----Original Message-----
> From: Christian Grobmeier [mailto:[email protected]]
> Sent: Monday, 27 April 2009 5:01 PM
> To: Log4PHP Dev
> Subject: Getting rid of author tags:
> 
> Hi,
> 
> I have a commit ready for getting rid of the author tags and would
> like to apply. Since a user complained about this and I am unsure
> about all this legal stuff, I would like to have your "go"s for this
> commit. (Please don't check the patch applied to the bug, I have
> re-created it)
> 
> In my opinion it's enough to give credits in the NOTICE file of the
> project. We do this at Commons to. I also think that it is enough to
> credit real names, not names like VXA or something.
> 
> See also: https://issues.apache.org/jira/browse/LOG4PHP-1
> 
> If no other opinions occur, I will go ahead and commit it.

Yep I agree, it is part of the 'Apache Way' if you like. Contributions such
as donated code (whether an initial import, a patch or a commit) belongs to
the project overall and not an individual. Any file
donated/committed/patched is owned by the project.

Usually, patches are recognised by their authors in any number of ways - via
the Jira Issue Tracker, via an svn commit message "..fixes blah, due to Joe
Bloggs" .

As far as an initial import, it is sometimes noted in a NOTICE file where it
came from and if it was a developer rather than another project then his/her
name is mentioned. I would not go as far as listing for instance 100
developers but rather the group(s) they belonged to. And I would not
continue to use a NOTICE file in this way.

To give an example of Apache Forrest for instance uses a CHANGES file (per
version) to note significant contributions and who it came from. I think
this would be a better way forward than continuing to use the NOTICE file.

We do not have to follow it but have a look at 

http://forrest.apache.org/guidelines.html#contribution

and the generated CHANGES at

http://forrest.apache.org/docs_0_90/changes.html


Gav...


> 
> Cheers,
> Christian
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.557 / Virus Database: 270.12.4/2081 - Release Date: 4/26/2009
> 9:44 AM

Reply via email to