1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Scott Shawcroft wrote: |
5 |
> The bugday database would hold additional bug information. Not the |
6 |
> data found in bugzilla. We get the available info from the bugzilla |
7 |
> DB. The bugday DB is a supplement. |
8 |
|
9 |
your origional email said "User logins using usernames and passwords from |
10 |
bugzilla." this implies that you would be porting the login db from bugzy to |
11 |
b-day. perhaps i misread that, but if you use the same db for logins, how will |
12 |
you keep the two synced? if i change my password on bugzy, would it be changed |
13 |
on bday too? |
14 |
|
15 |
> They would 'vote' via either adding a bug id or adding a vote to an |
16 |
> existing bugday bug via a link.* |
17 |
|
18 |
this again implies that you would need the bugzilla database. how else would |
19 |
you keep track of which bug is which? iirc, jforman said it was about 1.7gb... |
20 |
thats alot to manage in *two* places. this is more of a technical issue than a |
21 |
problem with your plan, but i'm just wondering how you plan to do this. |
22 |
|
23 |
>>>the problem i see is that easy bugs will simply be fixed by |
24 |
>>>developers. the more difficult bugs will be either swept under the |
25 |
>>>carpet or passed to maintainer-needed or bday. |
26 |
> |
27 |
> |
28 |
> Could you explain this more? What developers actively work on has no |
29 |
> direct link to bugdays. First and foremost bugdays are to give |
30 |
> direction to users. However, since users cannot commit changes, the |
31 |
> developers are involved. |
32 |
|
33 |
you said that bugs would be ranked by difficulty and users with experience "x" |
34 |
could work on bugs of the same experience level. say, for instance, a user is |
35 |
very new to gentoo, or at least to portage. if a dev gets a bug saying "package |
36 |
x does not install doc y", the dev knows that all (s)he has to do is add y to |
37 |
dodoc. consequently, the dev does it in a matter of seconds and the bug is gone. |
38 |
|
39 |
if i understand correctly, developers add their own bugs to the bugday list. |
40 |
since simple bugs like the above take just about as much time to solve as to |
41 |
add to an arbitrary list, i don't see any easy bugs being added to bday for |
42 |
newbie users to solve. |
43 |
|
44 |
maybe i'm wrong, but thats how i would generally do things. |
45 |
|
46 |
> To see how well it works is yet to be seen. However, it would be nice |
47 |
> to extend the community into actual meetings. I believe (disclaimer) |
48 |
> that learning techniques for bughunting and the like could be better |
49 |
> learned in person. Having multiple people in one location is more |
50 |
> effective and prevents bughunting from being too individual of an |
51 |
> experience when its really focused on community. |
52 |
|
53 |
this is true. if you can manage to arrange it, and its not too far away (i'm |
54 |
pretty poor :-), i'd love to come. |
55 |
|
56 |
the sense of community would also be strengthened a good deal. i read an |
57 |
article about obsd's hackathon, and it seems as if they are all one big group |
58 |
of friends. maybe a stronger sense of community would cut down on some of the |
59 |
silly arguments too... |
60 |
|
61 |
>>>occasionally user input. ex: if i can't reproduce and a user takes |
62 |
>>>a month to do something that should have taken a few seconds, it is |
63 |
>>>hard to progress quickly on the bug |
64 |
> |
65 |
> |
66 |
> Right and bugdays could prevent these instances from being over a |
67 |
> month long. It may also a way to bring more attention and knowledge |
68 |
> about bugzilla. |
69 |
|
70 |
well... if a user files a bug and the next bugday isn't for 3 weeks, that |
71 |
doesn't seem to help much, unless i am misunderstanding you. |
72 |
|
73 |
- -- |
74 |
|
75 |
smithj |
76 |
|
77 |
Gentoo Developer |
78 |
[ desktop stuff && network monitoring && documentation ] |
79 |
|
80 |
|
81 |
-----BEGIN PGP SIGNATURE----- |
82 |
Version: GnuPG v1.4.1 (GNU/Linux) |
83 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
84 |
|
85 |
iD4DBQFC3PVrl5AvwDPiUowRAneFAJ9aNbDKsEvmYY9tkjesho/emIrOYgCXdB9C |
86 |
vufdotedDfe3P8FTncqlVw== |
87 |
=0wll |
88 |
-----END PGP SIGNATURE----- |
89 |
-- |
90 |
gentoo-dev@g.o mailing list |