-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Shawcroft wrote: > - Have pre-bugday and post-bugday podcasts designed to present > information in an alternate form.
i like it, but also make it available as an .mp3 or a more common format (i know nothing about podcasting or if mplayer could play it ;-) > The pre-bugday podcast would include how-tos/tips in addition to a > run down of the top bugs. > The post-bugday podcast would include a debrief and highlight the > most effective bugday individuals and teams. > - User logins using usernames and passwords from bugzilla. > - In accordance with the above, user bug additions and voting on bugs > may also be supported. ok... but couldn't that get complicated? how are you going to sync the bugzy and bday databases? is there an elegant way to do so? would people be able to vote on _any_ bug, or just hose in a special list? if the latter, who makes the list? on what criterion? > - Classification of bugs by difficulty and language skills (if any) > required. > - Reference links to helpful articles on languages relating to a bug. > - Points awarded to users for solving bugs. These points are the also > the priority votes. 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. > - Association with bug hunting groups/teams which either form over the > internet or in real life. > - Event planner for real life bugday sessions. > - IRC bot interface to new website. > - New logo. all of this is nice in theory, but how are you going to accomplish it? real-life bughunting? sounds a little like openbsd's hackathon, which would be *GREAT*, except for the fact that i bet it would be mostly devs who would come. on the other hand, i'm not sure that said fact is necessarily a problem. > In addition to feedback on these ideas, I'd like to get some feedback > on ways to improve bugdays for developers. > Do you as a dev participate regularly? Why or why not? i know i'm a new dev, but i don't really participate. even when i was a user, i didn't. maybe its because i simply did/do gentoo work whenever i feel like it, but having a special day set asside seems odd to me. > What bottlenecks exist in closing bugs? time. time. time. we need more qualified devs imho. 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 - -- 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 iD8DBQFC3GrXl5AvwDPiUowRAvLhAKCGCaiYzRoSxV5h2jzHyQdOHhPy5QCgg7eW ZqbzK6DBknxuaSMNUAUvopE= =Irgx -----END PGP SIGNATURE----- -- [email protected] mailing list
