1 |
g2boojum |
1.1 |
GLEP: 6 |
2 |
|
|
Title: Gentoo Linux monthly bug day |
3 |
g2boojum |
1.4 |
Version: $Revision: 1.3 $ |
4 |
|
|
Last-Modified: $Date: 2003/07/28 18:40:18 $ |
5 |
liquidx |
1.2 |
Author: Brian Jackson <iggy@gentoo.org> |
6 |
g2boojum |
1.4 |
Status: Final |
7 |
g2boojum |
1.1 |
Type: Standards Track |
8 |
|
|
Content-Type: text/x-rst |
9 |
|
|
Created: 02-Jul-2003 |
10 |
g2boojum |
1.3 |
Post-History: 09-Jul-2003, 28-Jul-2003 |
11 |
g2boojum |
1.1 |
|
12 |
|
|
|
13 |
|
|
Credits |
14 |
|
|
======= |
15 |
|
|
|
16 |
|
|
I stole this idea from liquidx who probably stole it from one of the many |
17 |
|
|
projects that do something similar. |
18 |
|
|
|
19 |
|
|
|
20 |
|
|
Abstract |
21 |
|
|
======== |
22 |
|
|
|
23 |
|
|
Gentoo Linux should have one day a month that is devoted to clearing out bugs, |
24 |
|
|
and accepting new ebuilds from bugzilla. This one day a month should not |
25 |
|
|
replace a developers normal bug tracking duties. This "bug day" should become |
26 |
|
|
something that involves the user community to make them feel closer to the |
27 |
|
|
developers. |
28 |
|
|
|
29 |
|
|
Motivation |
30 |
|
|
========== |
31 |
|
|
|
32 |
|
|
I believe this would help keep the number of bugs in bugzilla at a lower level. |
33 |
|
|
This would also be a good chance for some user submitted ebuilds to be commited |
34 |
|
|
that would normally go overlooked. I think this is a good idea. We could turn |
35 |
|
|
this into a big deal for the user community |
36 |
|
|
|
37 |
|
|
Specification |
38 |
|
|
============= |
39 |
|
|
|
40 |
|
|
This doesn't require any coding. It just requires one day each month that |
41 |
|
|
little other than bug closing will happen. I would like to see all developers |
42 |
|
|
participate, but I know it's unlikely that we could get everybody free on the |
43 |
liquidx |
1.2 |
same day. The majority of the people that have had an opinion have |
44 |
|
|
suggested a weekend day. We will have bugday's on a Saturday. Gentoo |
45 |
|
|
developers can try to get some of the users to help them out. A prize to |
46 |
|
|
the most succesful developer was suggested. This is an idea to keep in |
47 |
|
|
mind for the future. I guess I'm going to be the one coordinating this |
48 |
|
|
until I get help, but when I do get help in coordinating this we can |
49 |
|
|
coordinate via irc if all parties are capable, or email if not. I will |
50 |
|
|
send out a notice telling the details at least one week in advance to the |
51 |
|
|
-dev, -core, and -user mailing lists. |
52 |
g2boojum |
1.1 |
|
53 |
|
|
Rationale |
54 |
|
|
========= |
55 |
|
|
|
56 |
liquidx |
1.2 |
Gnome [1]_ , Mozilla, Zope [2]_ , and other open source projects do something similar with good |
57 |
g2boojum |
1.1 |
success. |
58 |
|
|
|
59 |
liquidx |
1.2 |
References |
60 |
|
|
========== |
61 |
|
|
|
62 |
|
|
.. [1] http://developer.gnome.org/projects/bugsquad/triage/faq.html#II |
63 |
|
|
|
64 |
|
|
.. [2] http://dev.zope.org/CVS/BugDays |
65 |
g2boojum |
1.1 |
|
66 |
|
|
Copyright |
67 |
|
|
========= |
68 |
|
|
|
69 |
|
|
This document has been placed in the public domain. |
70 |
|
|
|