| 1 |
Hello, |
| 2 |
|
| 3 |
After having a talk with Sebastien (aka sping), I think it is time to |
| 4 |
give a clear reply from my side to this discussion, given that I am |
| 5 |
still a member of the project and I am willing to rescue it. |
| 6 |
|
| 7 |
At this moment, the Bugday Project is starving because no one feeds |
| 8 |
it. It needs to eat bugs, so before anything let's fill up the plate |
| 9 |
with as many of them as possible. |
| 10 |
|
| 11 |
In order to do this, we need to change a few things here and there so |
| 12 |
that the bugs flow correctly towards the project. |
| 13 |
|
| 14 |
The first thing that would help us a lot is to actually have a keyword |
| 15 |
'bugday' in our bugzilla. This will definitely help us out a lot when |
| 16 |
managing all the tickets and be able to produce some sort of report. |
| 17 |
|
| 18 |
The second thing that comes to my mind is pretty internal, but |
| 19 |
requires some external interaction. We need to work ahead of the Bug |
| 20 |
Day and be capable of having everything needed ready. Having the |
| 21 |
proper tools is very important for this task, and getting control of |
| 22 |
bugday.gentoo.org and be able to upload our own content would be |
| 23 |
great. It's a virtual apache host running in the same place as |
| 24 |
bugs.gentoo.org, as it requires access to the database (although this |
| 25 |
does not necessarily need to be like this if the database is |
| 26 |
accessible through the network). |
| 27 |
|
| 28 |
The third thing that we need is the proper audience. We need more PR. |
| 29 |
My proposal here is to start with an announcement two weeks before the |
| 30 |
Bug Day, followed by an announcement the week before and a reminder |
| 31 |
the day before. This needs to happen in publicly visible places (and |
| 32 |
has happened in some of them as far as I recall): forums, gentoo-user, |
| 33 |
gentoo-dev, gentoo-announce, gentoo-dev-announce, the newsletter |
| 34 |
(dead?) and the website. Having people related to the Bug Day project |
| 35 |
posting to their blogs can help a lot in this case as well. |
| 36 |
|
| 37 |
The fourth thing, is to actually get the proper information in the |
| 38 |
proper format. We need a compromise from each of the teams, so that |
| 39 |
they send us at least one bug every month that can be delegated to our |
| 40 |
users. Then the Bugday Project can decide whether the bug is |
| 41 |
appropriate or not for delegation, and tag it with the |
| 42 |
before-mentioned 'bugday' keyword. The teams should send the list of |
| 43 |
bugs, with each bug filling a skeleton similar to the following: |
| 44 |
|
| 45 |
* Ticket number. |
| 46 |
* Title. |
| 47 |
* Clear, easy to understand, short description of what we want to |
| 48 |
delegate to our users. |
| 49 |
* Topic of the task (as in networking, C/C++, python, ebuild, etc.). |
| 50 |
* Difficulty of the task. |
| 51 |
* Detailed step-by-step description of the task. |
| 52 |
|
| 53 |
Let me hear of what you have to say to all this. |
| 54 |
|
| 55 |
Regards. |
| 56 |
|
| 57 |
|
| 58 |
If we have this piece of information, we can organize ourselves better. |
| 59 |
On Mon, Mar 1, 2010 at 2:35 AM, Joshua Saddler <nightmorph@g.o> wrote: |
| 60 |
> On Sun, 28 Feb 2010 21:04:04 +0100 |
| 61 |
> Sebastian Pipping <sping@g.o> wrote: |
| 62 |
> |
| 63 |
>> On 02/28/10 20:54, Markos Chandras wrote: |
| 64 |
>> > Do we still have bugdays? Who is taking care of this project and the |
| 65 |
>> > respective webpage? I think we first need to answer these questions before |
| 66 |
>> > we even consider resurrect this project |
| 67 |
>> |
| 68 |
>> welp -> away |
| 69 |
> |
| 70 |
> He's not away, he's retired. It's just taken several months to close his bug. |
| 71 |
> |
| 72 |
>> gurligebis -> no reply yet |
| 73 |
> |
| 74 |
> I thought gurli was also retired. |
| 75 |
> |
| 76 |
> |
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
-- |
| 81 |
Ioannis Aslanidis |
| 82 |
http://www.deathwing00.org |
| 83 |
<deathwing00[at]gentoo.org> 0x47F370A0 |
Archives