OK. So we agree that contributions via patches become credits in svn
commit messages and in the changes file.

What should we do with the currently existing authors?
Most of the tags name Apache members, these are not a problem. But
some of them came into code with the initial import. I don't have an
idea what these authors really did and when.
Is it enough to mention in changes.xml "Refactoring and clean up of
code written by: x, y, z"

Cheers,
Christian

> 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