summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-September/008164.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/008164.html')
-rw-r--r--zarb-ml/mageia-dev/2011-September/008164.html126
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/008164.html b/zarb-ml/mageia-dev/2011-September/008164.html
new file mode 100644
index 000000000..4faafbeb7
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-September/008164.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia-discuss%5D%20MANDATORY%20READ%20%3A%207%20days%20before%0A%20misc%20unleashes%20CERBERUS%20%21&In-Reply-To=%3C4E73C17D.3030503%40iki.fi%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="008162.html">
+ <LINK REL="Next" HREF="008377.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !</H1>
+ <B>Anssi Hannula</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia-discuss%5D%20MANDATORY%20READ%20%3A%207%20days%20before%0A%20misc%20unleashes%20CERBERUS%20%21&In-Reply-To=%3C4E73C17D.3030503%40iki.fi%3E"
+ TITLE="[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !">anssi.hannula at iki.fi
+ </A><BR>
+ <I>Fri Sep 16 23:37:01 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="008162.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
+</A></li>
+ <LI>Next message: <A HREF="008377.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#8164">[ date ]</a>
+ <a href="thread.html#8164">[ thread ]</a>
+ <a href="subject.html#8164">[ subject ]</a>
+ <a href="author.html#8164">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 16.09.2011 19:48, Colin Guthrie wrote:
+&gt;<i> 'Twas brillig, and Michael Scherer at 16/09/11 14:39 did gyre and gimble:
+</I>&gt;&gt;<i> Le vendredi 16 septembre 2011 &#224; 12:44 +0200, Guillaume Rousse a &#233;crit :
+</I>&gt;&gt;&gt;<i> Le 16/09/2011 11:47, Sander Lepik a &#233;crit :
+</I>&gt;&gt;&gt;&gt;<i> 15.09.2011 21:43, Maarten Vanraes kirjutas:
+</I>&gt;&gt;&gt;&gt;&gt;<i> I have a script ready to set the last comittor (that's a full
+</I>&gt;&gt;&gt;&gt;&gt;<i> packager) as
+</I>&gt;&gt;&gt;&gt;&gt;<i> maintainer. perhaps it can be activated before the GREAT PURGE.
+</I>&gt;&gt;&gt;&gt;<i> That's not so good idea. What we maybe can do is that we send out a
+</I>&gt;&gt;&gt;&gt;<i> warning that if you commit to a package after the warning and the
+</I>&gt;&gt;&gt;&gt;<i> package has no maintainer yet then you become one. So that people would
+</I>&gt;&gt;&gt;&gt;<i> first check what they get on their name. Many packages were imported by
+</I>&gt;&gt;&gt;&gt;<i> Anne, i'm not sure that she's going to maintain them all. :)
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> I would do something like that:
+</I>&gt;&gt;&gt;&gt;<i> 2 months of warning period, if you touch package that has no maintainer
+</I>&gt;&gt;&gt;&gt;<i> you become its maintainer. After 2 months we start dropping those
+</I>&gt;&gt;&gt;&gt;<i> packages that have still no maintainer.
+</I>&gt;&gt;&gt;<i> This whole idea of 'touch a package, become its maintainer' assumes than
+</I>&gt;&gt;&gt;<i> anyone modifying a package has an obvious interest in it.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Then we can increase the heuristic, like &quot;upgrade to a new version&quot;, or
+</I>&gt;&gt;<i> &quot;do several commit on it&quot;. Someone upgrading a package either :
+</I>&gt;&gt;<i> - is interested in it for the package ( and thus would be a maintainer )
+</I>&gt;&gt;<i> - is interested into having it upgraded for using on another package
+</I>&gt;&gt;<i> ( and thus, as a user of the rpm for another rpm, has a interest to not
+</I>&gt;&gt;<i> make it disappear ).
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> And i doubt that someone would do X commit on a rpm if not interested in
+</I>&gt;&gt;<i> it.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Are heuristics a good idea? How about just making mgarepo ask you if you
+</I>&gt;<i> want to become the maintainer with a Y/n option (Y being default) when
+</I>&gt;<i> you call submit on an unmaintained package.
+</I>&gt;<i>
+</I>&gt;<i> This should be simple enough that people genuinely maintaining it can
+</I>&gt;<i> just hit return and also easy enough to opt out in the case of drive by
+</I>&gt;<i> upgrades.
+</I>
+This seems like a nice idea :)
+
+--
+Anssi Hannula
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="008162.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
+</A></li>
+ <LI>Next message: <A HREF="008377.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#8164">[ date ]</a>
+ <a href="thread.html#8164">[ thread ]</a>
+ <a href="subject.html#8164">[ subject ]</a>
+ <a href="author.html#8164">[ 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>