summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016661.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016661.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016661.html146
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016661.html b/zarb-ml/mageia-dev/2012-June/016661.html
new file mode 100644
index 000000000..cfc1af4be
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016661.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Collaboration policy
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Collaboration%20policy&In-Reply-To=%3CCA%2B0WU1Rzz3%3DjdZbKJ0w9oDztmvCNBM%3D6b5079H1RBu0wHqHXuQ%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="016584.html">
+ <LINK REL="Next" HREF="016707.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Collaboration policy</H1>
+ <B>Per &#216;yvind Karlsen</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Collaboration%20policy&In-Reply-To=%3CCA%2B0WU1Rzz3%3DjdZbKJ0w9oDztmvCNBM%3D6b5079H1RBu0wHqHXuQ%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Collaboration policy">peroyvind at mandriva.org
+ </A><BR>
+ <I>Wed Jun 20 03:05:15 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016584.html">[Mageia-dev] Collaboration policy
+</A></li>
+ <LI>Next message: <A HREF="016707.html">[Mageia-dev] Collaboration policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16661">[ date ]</a>
+ <a href="thread.html#16661">[ thread ]</a>
+ <a href="subject.html#16661">[ subject ]</a>
+ <a href="author.html#16661">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>2012/6/18 Colin Guthrie &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>&gt;:
+&gt;<i> 'Twas brillig, and Olivier Blin at 14/06/12 22:25 did gyre and gimble:
+</I>&gt;&gt;<i> David Walser &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">luigiwalser at yahoo.com</A>&gt; writes:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Olivier Blin &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at ...</A>&gt; writes:
+</I>&gt;&gt;&gt;&gt;<i> Crediting patchs from others by only mentionning the source
+</I>&gt;&gt;&gt;&gt;<i> (i.e. Mandriva, Fedora, XBMC, ...) is not enough IMHO.
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> If we want to give proper credits, we should also mention the author of
+</I>&gt;&gt;&gt;&gt;<i> the patch.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> It doesn't say we don't give credit to the patch author. &#160;It just says in our
+</I>&gt;&gt;&gt;<i> package changelog (a.k.a. our SVN commit messages), you mention where you got
+</I>&gt;&gt;&gt;<i> the patch from, because at that level you want to be concise and that's a much
+</I>&gt;&gt;&gt;<i> more useful piece of information.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> It says that we prefer to mention &quot;source&quot; over &quot;author&quot;.
+</I>&gt;&gt;<i> That's not good enough IMHO if we want to be ok with credits.
+</I>&gt;&gt;<i> The &quot;source&quot; is not the one retaining the copyright on a change, only
+</I>&gt;&gt;<i> the author owns this.
+</I>&gt;&gt;<i> And mentionning an author's name is the minimum reward when
+</I>&gt;&gt;<i> cherry-picking a change.
+</I>&gt;<i>
+</I>&gt;<i> Well IMO, this is a trade off that relates to practical usefulness.
+</I>&gt;<i>
+</I>&gt;<i> The options for the commit message are:
+</I>&gt;<i> &#160;1. Mention the source
+</I>&gt;<i> &#160;2. Mention the author
+</I>&gt;<i> &#160;3. Mention both source+author
+</I>&gt;<i>
+</I>&gt;<i> IMO 3 is too verbose for package changelogs, but I agree it would be
+</I>&gt;<i> nice to be able to do this if it were made concise.
+</I>&gt;<i>
+</I>&gt;<i> I also think that 2 is not ideal as this would then make it harder to
+</I>&gt;<i> record the source. We'd either have to write a comment in the spec above
+</I>&gt;<i> the PatchNN: line or put something into the patch itself to indicate the
+</I>&gt;<i> source. This is typically a good idea anyway (I try to put any fedora
+</I>&gt;<i> patches etc. in their own little section of the spec). If patches are
+</I>&gt;<i> generated from git then you don't really want to add unmanaged extra
+</I>&gt;<i> info in the patch file as when it is regenerated, this information would
+</I>&gt;<i> be lost.
+</I>&gt;<i>
+</I>&gt;<i> The opposite is not true - if option 1 were picked, then the author
+</I>&gt;<i> would typically be included already in the patch itself if it is a git
+</I>&gt;<i> formatted patch. I accept this is not always the case, so this isn't a
+</I>&gt;<i> fool-proof alternative.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> So, in the end, I'm not against mentioning the author directly in commit
+</I>&gt;<i> messages, but I think it's somewhat impractical and thus it is my
+</I>&gt;<i> opinion that it should not be in the message.
+</I>Then you're mixing two different things, this thing was about credting
+authors, right?
+But now you're replacing it with practical value in changelogs, which
+is an entirely different issue about a totally different subject!
+If you want to actually credit the person doing the work, then you
+need to credit the actual authors of the work itself, a distribution
+is certainly not what to be creditting itself for the work done by
+others, they were the ones who put the distribution together, not the
+distribution who put them together (lacking consciousness, thus no
+assurance needs to fill, desire for recognition not possible).
+If you're going to push this argument a bit further, for anything else
+of software in the distribution that we've packaged with it, neither
+would the authors of this software be the ones to be creditted for
+their work, but rather the distribution carrying it!
+
+So if in Mandriva, we'd actually were to fully recognize your
+arguments adopt this policy which you propose for Mageia iin Mandriva
+again, we'd have to start mess with all the rest of the software we
+ship to make sure that it credits Mandriva as we're carrying their
+work (I'd veto against this, no matter what anyone else might try
+propose and pushing)!
+And while I myself actually don't wanna meddle in Mageia's businiss
+(despite mine being meddled in first), I *really* don't think Mageia
+should do so either..
+
+And I *really* hope that this extremely bizarre example illustrates
+for you that it's not even remotely far out at all.
+
+I just find this awkward, and not on my part, so I'll just leave it
+with that.. :|
+
+--
+Getta grip,
+Per &#216;yvind
+</PRE>
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016584.html">[Mageia-dev] Collaboration policy
+</A></li>
+ <LI>Next message: <A HREF="016707.html">[Mageia-dev] Collaboration policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16661">[ date ]</a>
+ <a href="thread.html#16661">[ thread ]</a>
+ <a href="subject.html#16661">[ subject ]</a>
+ <a href="author.html#16661">[ 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>