1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
<!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=%3CAANLkTikA3WLDFB0%3DgSkOej_Jf%3D1XvWBuEyXQWgMb-DwO%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="001283.html">
<LINK REL="Next" HREF="001285.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Robert Xu</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=%3CAANLkTikA3WLDFB0%3DgSkOej_Jf%3D1XvWBuEyXQWgMb-DwO%40mail.gmail.com%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">robxu9 at gmail.com
</A><BR>
<I>Wed Oct 20 18:14:54 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001283.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001285.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1284">[ date ]</a>
<a href="thread.html#1284">[ thread ]</a>
<a href="subject.html#1284">[ subject ]</a>
<a href="author.html#1284">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, Oct 20, 2010 at 10:11, andré <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> wrote:
[snip!]
><i>
</I>><i> Good analogy :)
</I>><i> It's like an accellerated version of "pass a message to the person to the
</I>><i> left in the circle".  By the time it completes the circle and comes back (to
</I>><i> the right), the original message is unrecognisable.
</I>>><i>
</I>>><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>><i>
</I>><i> True.  Even the most naïve user can produce a good bug report with some
</I>><i> help, if they are willing to put in some effort.  A thank you email would be
</I>><i> a nice touch, especially for challenged users.  (I forget if Bugzilla
</I>><i> already acknowleges bug reports.)
</I>><i>
</I>><i> The critical part is the ability to directly contact the user with the
</I>><i> problem.  For Bugzilla, you have to log in, so there is an email adresse for
</I>><i> contact.  And this is generally the case for forums.  If we use a forum for
</I>><i> submitting bugs, we need the same login so that Bugzilla has a contact email
</I>><i> available.  This is doable, and would also be more convenient for all
</I>><i> contributors.
</I>><i> Of course, there is still the barrier of getting the user to sign up for an
</I>><i> account ... :)
</I>><i>
</I>><i> Another possibility is to have a Bugzilla assistant on the desktop, where
</I>><i> the user is asked to describe the problem, give an email adresse, which is
</I>><i> sent to Bugzilla.
</I>><i>
</I>><i> The approach of OpenOffice (official) could always be used for crashes.
</I>><i> A bug report page opens as OpenOffice restarts automatically on a crash.
</I>><i> Relevent info has already been gathered, viewable on a sub-page.
</I>><i> The user is asked to optionally describe what he was doing, and is invited
</I>><i> to optionally enter their email adresse if there are furthur questions (and
</I>><i> informed that it will only be used for the purposes of the bug in question).
</I>><i> And if the user provides an email adresse, they receive a thank you email
</I>><i> with the bug tracking number.
</I>><i> Very easy, and probably provides as much info as the average bugzilla
</I>><i> report.
</I>><i> Of course, only useful when a program crashes, where it can be automatically
</I>><i> sensed that there is a problem.  And it will produce a lot of duplicate bug
</I>><i> reports, evidently.
</I>><i>
</I>
You could use a tool like abrt, which can detect duplicate bug
reports, if I am correct.
It'll also make filing bug reports easier...
Maybe you could modify it to give a personal UUID for each computer,
so that the user
is not forced to register?
--
later, Robert Xu
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001283.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001285.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1284">[ date ]</a>
<a href="thread.html#1284">[ thread ]</a>
<a href="subject.html#1284">[ subject ]</a>
<a href="author.html#1284">[ 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>
|
