-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jonathan Smith wrote:
> 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 > ;-) For the record, podcasts are a collection of audio files wrapped in an RSS feed. > >> 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? 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. > > 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? > They would 'vote' via either adding a bug id or adding a vote to an existing bugday bug via a link.* > >> - 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. 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. > >> - 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. 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. > >> 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. Its not for everyone. Once again, its also about the community. > >> What bottlenecks exist in closing bugs? > > > time. time. time. we need more qualified devs imho. I think bugdays are a way to groom more qualified devs. > > 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. > -- > > smithj > > Gentoo Developer [ desktop stuff && network monitoring && > documentation ] * All of this is tenative. ~Scott -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3IdF10ekhar8gdURAiCYAKDXQkP2zp7wyZ1vXqWCaPFa0e3C5QCgkjZk 2OK4VtmlnGrXLeq6EsfnimQ= =6LQ1 -----END PGP SIGNATURE----- -- [email protected] mailing list
