-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Shawcroft wrote: > The bugday database would hold additional bug information. Not the > data found in bugzilla. We get the available info from the bugzilla > DB. The bugday DB is a supplement.
your origional email said "User logins using usernames and passwords from bugzilla." this implies that you would be porting the login db from bugzy to b-day. perhaps i misread that, but if you use the same db for logins, how will you keep the two synced? if i change my password on bugzy, would it be changed on bday too? > They would 'vote' via either adding a bug id or adding a vote to an > existing bugday bug via a link.* this again implies that you would need the bugzilla database. how else would you keep track of which bug is which? iirc, jforman said it was about 1.7gb... thats alot to manage in *two* places. this is more of a technical issue than a problem with your plan, but i'm just wondering how you plan to do this. >>>the problem i see is that easy bugs will simply be fixed by >>>developers. the more difficult bugs will be either swept under the >>>carpet or passed to maintainer-needed or bday. > > > Could you explain this more? What developers actively work on has no > direct link to bugdays. First and foremost bugdays are to give > direction to users. However, since users cannot commit changes, the > developers are involved. you said that bugs would be ranked by difficulty and users with experience "x" could work on bugs of the same experience level. say, for instance, a user is very new to gentoo, or at least to portage. if a dev gets a bug saying "package x does not install doc y", the dev knows that all (s)he has to do is add y to dodoc. consequently, the dev does it in a matter of seconds and the bug is gone. if i understand correctly, developers add their own bugs to the bugday list. since simple bugs like the above take just about as much time to solve as to add to an arbitrary list, i don't see any easy bugs being added to bday for newbie users to solve. maybe i'm wrong, but thats how i would generally do things. > To see how well it works is yet to be seen. However, it would be nice > to extend the community into actual meetings. I believe (disclaimer) > that learning techniques for bughunting and the like could be better > learned in person. Having multiple people in one location is more > effective and prevents bughunting from being too individual of an > experience when its really focused on community. this is true. if you can manage to arrange it, and its not too far away (i'm pretty poor :-), i'd love to come. the sense of community would also be strengthened a good deal. i read an article about obsd's hackathon, and it seems as if they are all one big group of friends. maybe a stronger sense of community would cut down on some of the silly arguments too... >>>occasionally user input. ex: if i can't reproduce and a user takes >>>a month to do something that should have taken a few seconds, it is >>>hard to progress quickly on the bug > > > Right and bugdays could prevent these instances from being over a > month long. It may also a way to bring more attention and knowledge > about bugzilla. well... if a user files a bug and the next bugday isn't for 3 weeks, that doesn't seem to help much, unless i am misunderstanding you. - -- smithj Gentoo Developer [ desktop stuff && network monitoring && documentation ] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD4DBQFC3PVrl5AvwDPiUowRAneFAJ9aNbDKsEvmYY9tkjesho/emIrOYgCXdB9C vufdotedDfe3P8FTncqlVw== =0wll -----END PGP SIGNATURE----- -- [email protected] mailing list
