| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Scott Shawcroft wrote: |
| 5 |
> - Have pre-bugday and post-bugday podcasts designed to present |
| 6 |
> information in an alternate form. |
| 7 |
|
| 8 |
i like it, but also make it available as an .mp3 or a more common format (i |
| 9 |
know nothing about podcasting or if mplayer could play it ;-) |
| 10 |
|
| 11 |
> The pre-bugday podcast would include how-tos/tips in addition to a |
| 12 |
> run down of the top bugs. |
| 13 |
> The post-bugday podcast would include a debrief and highlight the |
| 14 |
> most effective bugday individuals and teams. |
| 15 |
> - User logins using usernames and passwords from bugzilla. |
| 16 |
> - In accordance with the above, user bug additions and voting on bugs |
| 17 |
> may also be supported. |
| 18 |
|
| 19 |
ok... but couldn't that get complicated? how are you going to sync the bugzy |
| 20 |
and bday databases? is there an elegant way to do so? |
| 21 |
|
| 22 |
would people be able to vote on _any_ bug, or just hose in a special list? if |
| 23 |
the latter, who makes the list? on what criterion? |
| 24 |
|
| 25 |
> - Classification of bugs by difficulty and language skills (if any) |
| 26 |
> required. |
| 27 |
> - Reference links to helpful articles on languages relating to a bug. |
| 28 |
> - Points awarded to users for solving bugs. These points are the also |
| 29 |
> the priority votes. |
| 30 |
|
| 31 |
the problem i see is that easy bugs will simply be fixed by developers. the |
| 32 |
more difficult bugs will be either swept under the carpet or passed to |
| 33 |
maintainer-needed or bday. |
| 34 |
|
| 35 |
> - Association with bug hunting groups/teams which either form over the |
| 36 |
> internet or in real life. |
| 37 |
> - Event planner for real life bugday sessions. |
| 38 |
> - IRC bot interface to new website. |
| 39 |
> - New logo. |
| 40 |
|
| 41 |
all of this is nice in theory, but how are you going to accomplish it? |
| 42 |
real-life bughunting? sounds a little like openbsd's hackathon, which would be |
| 43 |
*GREAT*, except for the fact that i bet it would be mostly devs who would come. |
| 44 |
on the other hand, i'm not sure that said fact is necessarily a problem. |
| 45 |
|
| 46 |
> In addition to feedback on these ideas, I'd like to get some feedback |
| 47 |
> on ways to improve bugdays for developers. |
| 48 |
> Do you as a dev participate regularly? Why or why not? |
| 49 |
|
| 50 |
i know i'm a new dev, but i don't really participate. even when i was a user, i |
| 51 |
didn't. maybe its because i simply did/do gentoo work whenever i feel like it, |
| 52 |
but having a special day set asside seems odd to me. |
| 53 |
|
| 54 |
> What bottlenecks exist in closing bugs? |
| 55 |
|
| 56 |
time. time. time. we need more qualified devs imho. |
| 57 |
|
| 58 |
occasionally user input. ex: if i can't reproduce and a user takes a month to |
| 59 |
do something that should have taken a few seconds, it is hard to progress |
| 60 |
quickly on the bug |
| 61 |
|
| 62 |
- -- |
| 63 |
|
| 64 |
smithj |
| 65 |
|
| 66 |
Gentoo Developer |
| 67 |
[ desktop stuff && network monitoring && documentation ] |
| 68 |
|
| 69 |
|
| 70 |
-----BEGIN PGP SIGNATURE----- |
| 71 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 72 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 73 |
|
| 74 |
iD8DBQFC3GrXl5AvwDPiUowRAvLhAKCGCaiYzRoSxV5h2jzHyQdOHhPy5QCgg7eW |
| 75 |
ZqbzK6DBknxuaSMNUAUvopE= |
| 76 |
=Irgx |
| 77 |
-----END PGP SIGNATURE----- |
| 78 |
-- |
| 79 |
gentoo-dev@g.o mailing list |
Archives