Hello, After having a talk with Sebastien (aka sping), I think it is time to give a clear reply from my side to this discussion, given that I am still a member of the project and I am willing to rescue it.
At this moment, the Bugday Project is starving because no one feeds it. It needs to eat bugs, so before anything let's fill up the plate with as many of them as possible. In order to do this, we need to change a few things here and there so that the bugs flow correctly towards the project. The first thing that would help us a lot is to actually have a keyword 'bugday' in our bugzilla. This will definitely help us out a lot when managing all the tickets and be able to produce some sort of report. The second thing that comes to my mind is pretty internal, but requires some external interaction. We need to work ahead of the Bug Day and be capable of having everything needed ready. Having the proper tools is very important for this task, and getting control of bugday.gentoo.org and be able to upload our own content would be great. It's a virtual apache host running in the same place as bugs.gentoo.org, as it requires access to the database (although this does not necessarily need to be like this if the database is accessible through the network). The third thing that we need is the proper audience. We need more PR. My proposal here is to start with an announcement two weeks before the Bug Day, followed by an announcement the week before and a reminder the day before. This needs to happen in publicly visible places (and has happened in some of them as far as I recall): forums, gentoo-user, gentoo-dev, gentoo-announce, gentoo-dev-announce, the newsletter (dead?) and the website. Having people related to the Bug Day project posting to their blogs can help a lot in this case as well. The fourth thing, is to actually get the proper information in the proper format. We need a compromise from each of the teams, so that they send us at least one bug every month that can be delegated to our users. Then the Bugday Project can decide whether the bug is appropriate or not for delegation, and tag it with the before-mentioned 'bugday' keyword. The teams should send the list of bugs, with each bug filling a skeleton similar to the following: * Ticket number. * Title. * Clear, easy to understand, short description of what we want to delegate to our users. * Topic of the task (as in networking, C/C++, python, ebuild, etc.). * Difficulty of the task. * Detailed step-by-step description of the task. Let me hear of what you have to say to all this. Regards. If we have this piece of information, we can organize ourselves better. On Mon, Mar 1, 2010 at 2:35 AM, Joshua Saddler <[email protected]> wrote: > On Sun, 28 Feb 2010 21:04:04 +0100 > Sebastian Pipping <[email protected]> wrote: > >> On 02/28/10 20:54, Markos Chandras wrote: >> > Do we still have bugdays? Who is taking care of this project and the >> > respective webpage? I think we first need to answer these questions before >> > we even consider resurrect this project >> >> welp -> away > > He's not away, he's retired. It's just taken several months to close his bug. > >> gurligebis -> no reply yet > > I thought gurli was also retired. > > -- Ioannis Aslanidis http://www.deathwing00.org <deathwing00[at]gentoo.org> 0x47F370A0
