diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110303/002910.html')
-rw-r--r-- | zarb-ml/mageia-dev/20110303/002910.html | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110303/002910.html b/zarb-ml/mageia-dev/20110303/002910.html new file mode 100644 index 000000000..303d18a63 --- /dev/null +++ b/zarb-ml/mageia-dev/20110303/002910.html @@ -0,0 +1,134 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Contributors using real name/working email? or not? or maybe? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Contributors%20using%20real%20name/working%20email%3F%20or%0A%20not%3F%20or%09maybe%3F&In-Reply-To=%3C4D6FC021.1030608%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002914.html"> + <LINK REL="Next" HREF="002911.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Contributors using real name/working email? or not? or maybe?</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Contributors%20using%20real%20name/working%20email%3F%20or%0A%20not%3F%20or%09maybe%3F&In-Reply-To=%3C4D6FC021.1030608%40iki.fi%3E" + TITLE="[Mageia-dev] Contributors using real name/working email? or not? or maybe?">tmb at iki.fi + </A><BR> + <I>Thu Mar 3 17:21:53 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002914.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe? +</A></li> + <LI>Next message: <A HREF="002911.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2910">[ date ]</a> + <a href="thread.html#2910">[ thread ]</a> + <a href="subject.html#2910">[ subject ]</a> + <a href="author.html#2910">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Romain d'Alverny skrev 3.3.2011 16:00: + +><i> The points to decide here are: +</I>><i> a) should a contributor provide a public email address, to be used in +</I>><i> changelogs, commits and everywhere her contribution to the project +</I>><i> needs an id or contact id? (for instance changelog, commit, document +</I>><i> authoring) +</I>><i> b) should a contributor provide a real name for the same goals? or is +</I>><i> a fake name/alias ok, as long as there are people that do know/meet +</I>><i> the person? +</I>><i> +</I> + +I for one like the idea/workflow on LKML and kernel contributions, as +specified by section 12 in the Documentation/SubmittingPatches + +(<A HREF="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches">http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches</A>) + +<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 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">random at developer.example.org</A>> + +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 +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002914.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe? +</A></li> + <LI>Next message: <A HREF="002911.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2910">[ date ]</a> + <a href="thread.html#2910">[ thread ]</a> + <a href="subject.html#2910">[ subject ]</a> + <a href="author.html#2910">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |