summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101017/001246.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101017/001246.html')
-rw-r--r--zarb-ml/mageia-dev/20101017/001246.html146
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101017/001246.html b/zarb-ml/mageia-dev/20101017/001246.html
new file mode 100644
index 000000000..b8285875f
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101017/001246.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] How will be the realese cycle?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3Ci9dpgk%243od%241%40dough.gmane.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001244.html">
+ <LINK REL="Next" HREF="001247.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] How will be the realese cycle?</H1>
+ <B>Marc Par&#233;</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3Ci9dpgk%243od%241%40dough.gmane.org%3E"
+ TITLE="[Mageia-dev] How will be the realese cycle?">marc at marcpare.com
+ </A><BR>
+ <I>Sun Oct 17 05:11:16 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001244.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="001247.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1246">[ date ]</a>
+ <a href="thread.html#1246">[ thread ]</a>
+ <a href="subject.html#1246">[ subject ]</a>
+ <a href="author.html#1246">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 2010-10-16 18:35, Romain d'Alverny a &#233;crit :
+&gt;<i> On Sat, Oct 16, 2010 at 21:29, Marc Par&#233;&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marc at marcpare.com</A>&gt; wrote:
+</I>&gt;&gt;<i> Le 2010-10-16 12:36, Ahmad Samir a &#233;crit :
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> It's much better to help the user formulate a useful bug report,
+</I>&gt;&gt;&gt;<i> that's easier / more productive for all involved parties.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> There would be no middle man. Once the middle-man could replicate the bug
+</I>&gt;&gt;<i> and verify the bug with other users, then the middle-man would submit to
+</I>&gt;&gt;<i> bugzilla. That's it. From there on, the middle-man will take care of testing
+</I>&gt;&gt;<i> requests from devs.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> As far as reporting back to the original user who reported the bug, as an
+</I>&gt;&gt;<i> extra gesture of kindness, the middle-man would just post on the &quot;Report a
+</I>&gt;&gt;<i> bug&quot; forum that the bug has been quashed or is still under review ... but
+</I>&gt;&gt;<i> not to the user but to the &quot;Report a bug&quot; forum.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> The idea is to keep the flow of possible bug reports coming in an organised
+</I>&gt;&gt;<i> way. The middle-man would have to be someone with a little more experience
+</I>&gt;&gt;<i> than that of a new user and also someone who has an interest in working this
+</I>&gt;&gt;<i> way. We will get more bug reports from users by keeping it simple and easy.
+</I>&gt;<i>
+</I>&gt;<i> Yes, and for everyone.
+</I>&gt;<i>
+</I>&gt;<i> I tend to agree with Ahmad, as well as with you.
+</I>&gt;<i>
+</I>&gt;<i> You may as well imagine we improve the Bugzilla process with a
+</I>&gt;<i> front-process, guiding the reporter about her bug report.
+</I>&gt;<i>
+</I>&gt;<i> That may be a forum with people active there, educating the user about
+</I>&gt;<i> the bug and the reporting process;
+</I>&gt;<i>
+</I>&gt;<i> And/or that may be a better designed bug reporting process with a
+</I>&gt;<i> better flow (providing and getting info to/from the user), querying a
+</I>&gt;<i> knowledge-base, filtering known/resolved queries out of
+</I>&gt;<i> yet-another-duplicate-bug-report and ultimately opening a bug in
+</I>&gt;<i> Bugzilla with a specific interaction to the user (so she knows what
+</I>&gt;<i> happens next).*
+</I>&gt;<i>
+</I>&gt;<i> That removes the middle-man issue and that filters out as well people
+</I>&gt;<i> that are not concerned enough to report/follow-up on a bug (provided
+</I>&gt;<i> the process is, indeed, better designed and better welcomes the end
+</I>&gt;<i> user).
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> * moreover, I believe this type of improvement would benefit many,
+</I>&gt;<i> many, if not all, projects using a bug report tool.
+</I>&gt;<i>
+</I>&gt;<i> Cheers,
+</I>&gt;<i>
+</I>&gt;<i> Romain
+</I>&gt;<i>
+</I>
+Thanks for the note Romain.
+
+I think what this all boils down to is, does the Mageia project want to
+actively seek out bugs and encourage its users to report bugs? If Mageia
+is interested in seriously quashing bugs, then the reporting process has
+to be streamlined in such a way as to encourage the reporting of bug as
+painlessly as possible for users. Human nature being what it is, people
+will gladly report a bug if there is a way to do so quickly and easily.
+However, it gets more complicated if you ask users to follow up on their
+bug report, as in bugzilla.
+
+IMHO, it would be easier if Mageia offered users:
+
+-- The reporting of bugs through bugzilla as is usually done, and the
+devs can work out these problems with the normal messaging that normally
+goes along with the bugzilla process.
+
+-- For users who have no intention of being part of bugzilla and who
+would still like to report a bug, a forum discussion where a &quot;middle
+man&quot; or &quot;bug facilitator&quot; would help triage the bugs in this forum,
+verify the bug and then submit it in their name. The user would not be
+obligated from this point on to involve herself with the testing of
+possible bug repairs. The &quot;bug facilitator&quot; would be obligated to the
+usual bugzilla process. Of course if the user wished to learn more and
+participate in the bugzilla process, then the &quot;bug-facilitator&quot; could
+help mentor the user to the bugzilla process.
+
+This way the user would have 2 methods of reporting, one with a certain
+amount of commitment and the other with no commitments other than
+reporting and doing a quick verification with the help of the &quot;bug
+facilitator&quot;.
+
+The devs would not be part of this process and would work through the
+bugzilla as usual. And the bug reporting would, IMOH, be more streamlined.
+
+Marc
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001244.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="001247.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1246">[ date ]</a>
+ <a href="thread.html#1246">[ thread ]</a>
+ <a href="subject.html#1246">[ subject ]</a>
+ <a href="author.html#1246">[ 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>