[Mageia-dev] Contributors using real name/working email? or not? or maybe?

[Thomas Backlund]

Romain d'Alverny skrev 3.3.2011 16:00:

> The points to decide here are:
>   a) should a contributor provide a public email address, to be used in
> changelogs, commits and everywhere her contribution to the project
> needs an id or contact id? (for instance changelog, commit, document
> authoring)
>   b) should a contributor provide a real name for the same goals? or is
> a fake name/alias ok, as long as there are people that do know/meet
> the person?
>


I for one like the idea/workflow on LKML and kernel contributions, as 
specified by section 12 in the  Documentation/SubmittingPatches

(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches)

<quote>
12) Sign your work

To improve tracking of who did what, especially with patches that can
percolate to their final resting place in the kernel through several
layers of maintainers, we've introduced a "sign-off" procedure on
patches that are being emailed around.

The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as a open-source patch.  The rules are pretty simple: if you
can certify the below:

         Developer's Certificate of Origin 1.1

         By making a contribution to this project, I certify that:

         (a) The contribution was created in whole or in part by me and I
             have the right to submit it under the open source license
             indicated in the file; or

         (b) The contribution is based upon previous work that, to the best
             of my knowledge, is covered under an appropriate open source
             license and I have the right under that license to submit that
             work with modifications, whether created in whole or in part
             by me, under the same open source license (unless I am
             permitted to submit under a different license), as indicated
             in the file; or

         (c) The contribution was provided directly to me by some other
             person who certified (a), (b) or (c) and I have not modified
             it.

         (d) I understand and agree that this project and the contribution
             are public and that a record of the contribution (including all
             personal information I submit with it, including my 
sign-off) is
             maintained indefinitely and may be redistributed consistent 
with
             this project or the open source license(s) involved.

then you just add a line saying

         Signed-off-by: Random J Developer <random at developer.example.org>

using your real name (sorry, no pseudonyms or anonymous contributions.)
</quote>

The same applies to more and more projects when sending patches 
upstream, namely proper sign-off is required.

So IMHO the same idea can be applied to changelogs, as they are a 
automated "Sign-off" by the submitter.

--
Thomas