| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Jonathan Smith wrote: |
| 5 |
|
| 6 |
> Scott Shawcroft wrote: |
| 7 |
> |
| 8 |
>> - Have pre-bugday and post-bugday podcasts designed to present |
| 9 |
>> information in an alternate form. |
| 10 |
> |
| 11 |
> |
| 12 |
> i like it, but also make it available as an .mp3 or a more common |
| 13 |
> format (i know nothing about podcasting or if mplayer could play it |
| 14 |
> ;-) |
| 15 |
|
| 16 |
For the record, podcasts are a collection of audio files wrapped in an |
| 17 |
RSS feed. |
| 18 |
|
| 19 |
> |
| 20 |
>> The pre-bugday podcast would include how-tos/tips in addition to |
| 21 |
>> a run down of the top bugs. The post-bugday podcast would include |
| 22 |
>> a debrief and highlight the most effective bugday individuals and |
| 23 |
>> teams. - User logins using usernames and passwords from bugzilla. |
| 24 |
>> - In accordance with the above, user bug additions and voting on |
| 25 |
>> bugs may also be supported. |
| 26 |
> |
| 27 |
> |
| 28 |
> ok... but couldn't that get complicated? how are you going to sync |
| 29 |
> the bugzy and bday databases? is there an elegant way to do so? |
| 30 |
|
| 31 |
The bugday database would hold additional bug information. Not the |
| 32 |
data found in bugzilla. We get the available info from the bugzilla |
| 33 |
DB. The bugday DB is a supplement. |
| 34 |
|
| 35 |
> |
| 36 |
> would people be able to vote on _any_ bug, or just hose in a |
| 37 |
> special list? if the latter, who makes the list? on what criterion? |
| 38 |
> |
| 39 |
They would 'vote' via either adding a bug id or adding a vote to an |
| 40 |
existing bugday bug via a link.* |
| 41 |
|
| 42 |
> |
| 43 |
>> - Classification of bugs by difficulty and language skills (if |
| 44 |
>> any) required. - Reference links to helpful articles on languages |
| 45 |
>> relating to a bug. - Points awarded to users for solving bugs. |
| 46 |
>> These points are the also the priority votes. |
| 47 |
> |
| 48 |
> |
| 49 |
> the problem i see is that easy bugs will simply be fixed by |
| 50 |
> developers. the more difficult bugs will be either swept under the |
| 51 |
> carpet or passed to maintainer-needed or bday. |
| 52 |
|
| 53 |
Could you explain this more? What developers actively work on has no |
| 54 |
direct link to bugdays. First and foremost bugdays are to give |
| 55 |
direction to users. However, since users cannot commit changes, the |
| 56 |
developers are involved. |
| 57 |
|
| 58 |
> |
| 59 |
>> - Association with bug hunting groups/teams which either form |
| 60 |
>> over the internet or in real life. - Event planner for real life |
| 61 |
>> bugday sessions. - IRC bot interface to new website. - New logo. |
| 62 |
> |
| 63 |
> |
| 64 |
> all of this is nice in theory, but how are you going to accomplish |
| 65 |
> it? real-life bughunting? sounds a little like openbsd's hackathon, |
| 66 |
> which would be *GREAT*, except for the fact that i bet it would be |
| 67 |
> mostly devs who would come. on the other hand, i'm not sure that |
| 68 |
> said fact is necessarily a problem. |
| 69 |
|
| 70 |
To see how well it works is yet to be seen. However, it would be nice |
| 71 |
to extend the community into actual meetings. I believe (disclaimer) |
| 72 |
that learning techniques for bughunting and the like could be better |
| 73 |
learned in person. Having multiple people in one location is more |
| 74 |
effective and prevents bughunting from being too individual of an |
| 75 |
experience when its really focused on community. |
| 76 |
|
| 77 |
> |
| 78 |
>> In addition to feedback on these ideas, I'd like to get some |
| 79 |
>> feedback on ways to improve bugdays for developers. Do you as a |
| 80 |
>> dev participate regularly? Why or why not? |
| 81 |
> |
| 82 |
> |
| 83 |
> i know i'm a new dev, but i don't really participate. even when i |
| 84 |
> was a user, i didn't. maybe its because i simply did/do gentoo work |
| 85 |
> whenever i feel like it, but having a special day set asside seems |
| 86 |
> odd to me. |
| 87 |
|
| 88 |
Its not for everyone. Once again, its also about the community. |
| 89 |
|
| 90 |
> |
| 91 |
>> What bottlenecks exist in closing bugs? |
| 92 |
> |
| 93 |
> |
| 94 |
> time. time. time. we need more qualified devs imho. |
| 95 |
|
| 96 |
I think bugdays are a way to groom more qualified devs. |
| 97 |
|
| 98 |
> |
| 99 |
> occasionally user input. ex: if i can't reproduce and a user takes |
| 100 |
> a month to do something that should have taken a few seconds, it is |
| 101 |
> hard to progress quickly on the bug |
| 102 |
|
| 103 |
Right and bugdays could prevent these instances from being over a |
| 104 |
month long. It may also a way to bring more attention and knowledge |
| 105 |
about bugzilla. |
| 106 |
|
| 107 |
> -- |
| 108 |
> |
| 109 |
> smithj |
| 110 |
> |
| 111 |
> Gentoo Developer [ desktop stuff && network monitoring && |
| 112 |
> documentation ] |
| 113 |
|
| 114 |
* All of this is tenative. |
| 115 |
~Scott |
| 116 |
-----BEGIN PGP SIGNATURE----- |
| 117 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 118 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 119 |
|
| 120 |
iD8DBQFC3IdF10ekhar8gdURAiCYAKDXQkP2zp7wyZ1vXqWCaPFa0e3C5QCgkjZk |
| 121 |
2OK4VtmlnGrXLeq6EsfnimQ= |
| 122 |
=6LQ1 |
| 123 |
-----END PGP SIGNATURE----- |
| 124 |
|
| 125 |
-- |
| 126 |
gentoo-dev@g.o mailing list |
Archives