diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101020/001282.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101020/001282.html | 169 |
1 files changed, 169 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101020/001282.html b/zarb-ml/mageia-dev/20101020/001282.html new file mode 100644 index 000000000..c6f0aa21e --- /dev/null +++ b/zarb-ml/mageia-dev/20101020/001282.html @@ -0,0 +1,169 @@ +<!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=%3C4CBEF89E.3060108%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="001283.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>andré</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=%3C4CBEF89E.3060108%40laposte.net%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">andr55 at laposte.net + </A><BR> + <I>Wed Oct 20 16:11:42 CEST 2010</I> + <P><UL> + + <LI>Next message: <A HREF="001283.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1282">[ date ]</a> + <a href="thread.html#1282">[ thread ]</a> + <a href="subject.html#1282">[ subject ]</a> + <a href="author.html#1282">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Ahmad Samir a écrit : +><i> On 16 October 2010 17:31, Marc Paré<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marc at marcpare.com</A>> wrote: +</I>><i> +</I>>><i> Le 2010-10-16 02:56, Luca Berra a écrit : +</I>>><i> +</I>>>><i> On Fri, Oct 15, 2010 at 10:00:14PM -0500, Fernando Parra wrote: +</I>>>>><i> The basic/novice user doesn't read anything, +</I>>>>><i> +</I>>>><i> remove basic/novice from the sentence and i will agree ;) +</I>>>><i> +</I>>>>><i> doesn't request anything to some like a bugzilla, +</I>>>>><i> +</I>>>><i> but give him a forum and he probably will +</I>>>><i> +</I>>><i> This statement I totally agree with! If a user is told to submit in +</I>>><i> bugzilla, I find that they will not do it. Reporting to bugzilla for a user, +</I>>><i> is one more level of serious commitment on their part and most will not want +</I>>><i> to commit themselves to it. +</I>>><i> +</I>>><i> However, if they can report to a forum, this is different. Users view forums +</I>>><i> as community involvement with community feedback. They may be ask to test +</I>>><i> out the problem and report back on the result (just like in bugzilla) but +</I>>><i> they know that other community members will be there to lend a hand and +</I>>><i> support. +</I>>><i> +</I>><i> And other community members are there in bugzilla to to lend a hand +</I>><i> and support (although a bit different kind of support as bugzilla's +</I>><i> have stricter rules, more organised). +</I>><i> +</I>>><i> If we are going to be really interested in quashing bugs with a lot of +</I>>><i> community involvement, IMHO, I think that we should offer +</I>>><i> +</I>>><i> -- bugzilla for the enthused and commited users. These people are interested +</I>>><i> on reporting bugs the right way and will replicated and help in debugging. +</I>>><i> +</I>>><i> -- but for ordinary users, we could offer them a "Report a bug" forum where +</I>>><i> they can report a bug; the community could then replicated the bug; have a +</I>>><i> "Bug-ambassador" or "bug-reporter" or .... who could then submit it +</I>>><i> officially on bugzilla. Tracking of that particular bug could then be the +</I>>><i> responsibility of the "Bug-ambassador"; once the bug is quashed, the +</I>>><i> "Bug-ambassador" could report back to the "Report a bug" forum of the bug +</I>>><i> fix and thank the community for their help. This would help validate the +</I>>><i> user who reported the bug and make him/her feel like a part of the +</I>>><i> contributing team. +</I>>><i> +</I>>><i> IMHO, this would work a lot better for the majority of users who do not want +</I>>><i> to commit to any more than reporting the bug; the devs would get a more +</I>>><i> constant stream of bug submissions by "Bug-ambassadors" who are able to +</I>>><i> triage submitted bugs on the forum. +</I>>><i> +</I>>><i> Doing it this way would still make bugzilla the only place where devs would +</I>>><i> go to pick up bug information and the "Bug-ambassadors" would be the people +</I>>><i> who triage the bugs at the forum level. +</I>>><i> +</I>>><i> Marc +</I>>><i> +</I>><i> Backport requests are a special case as they're usually a 2-line +</I>><i> report "hey, could you backport the latest version of package foo to +</I>><i> <stable release I am running>?", so basically anyone can do it, either +</I>><i> the user or someone on his behalf. +</I>><i> +</I>><i> But generally reporting bugs by proxy is always a bad idea, unless the +</I>><i> guy who'll play middle-man can reproduce the exact same bug on his own +</I>><i> box. You see, triage team / package maintainer / dev will ask for info +</I>><i> about the bug, more than once depending on the bug itself; now Mr. +</I>><i> middle-man will have to go to and fro a lot of times, taking info from +</I>><i> the user and posting it in bugzilla then taking questions/info from +</I>><i> the bugzilla and conveying it to the user; now that's a tedious and +</I>><i> tiresome job that's very prone to failure. (it's like a friend being +</I>><i> sick and instead of him going to the doctor he sends you on his behalf +</I>><i> because "you know the symptoms" :)). +</I>><i> +</I>Good analogy :) +It's like an accellerated version of "pass a message to the person to +the left in the circle". By the time it completes the circle and comes +back (to the right), the original message is unrecognisable. +><i> It's much better to help the user formulate a useful bug report, +</I>><i> that's easier / more productive for all involved parties. +</I>><i> +</I>True. Even the most naïve user can produce a good bug report with some +help, if they are willing to put in some effort. A thank you email +would be a nice touch, especially for challenged users. (I forget if +Bugzilla already acknowleges bug reports.) + +The critical part is the ability to directly contact the user with the +problem. For Bugzilla, you have to log in, so there is an email adresse +for contact. And this is generally the case for forums. If we use a +forum for submitting bugs, we need the same login so that Bugzilla has a +contact email available. This is doable, and would also be more +convenient for all contributors. +Of course, there is still the barrier of getting the user to sign up for +an account ... :) + +Another possibility is to have a Bugzilla assistant on the desktop, +where the user is asked to describe the problem, give an email adresse, +which is sent to Bugzilla. + +The approach of OpenOffice (official) could always be used for crashes. +A bug report page opens as OpenOffice restarts automatically on a crash. +Relevent info has already been gathered, viewable on a sub-page. +The user is asked to optionally describe what he was doing, and is +invited to optionally enter their email adresse if there are furthur +questions (and informed that it will only be used for the purposes of +the bug in question). +And if the user provides an email adresse, they receive a thank you +email with the bug tracking number. +Very easy, and probably provides as much info as the average bugzilla +report. +Of course, only useful when a program crashes, where it can be +automatically sensed that there is a problem. And it will produce a lot +of duplicate bug reports, evidently. + +my 2 cents :) + +- André (andre999) +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="001283.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1282">[ date ]</a> + <a href="thread.html#1282">[ thread ]</a> + <a href="subject.html#1282">[ subject ]</a> + <a href="author.html#1282">[ 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> |