From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-39625-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NmD0F-0005AF-FS
for garchives@archives.gentoo.org; Mon, 01 Mar 2010 21:18:11 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 2DA84E0A7E;
Mon, 1 Mar 2010 21:18:07 +0000 (UTC)
Received: from mail-ew0-f222.google.com (mail-ew0-f222.google.com [209.85.219.222])
by pigeon.gentoo.org (Postfix) with ESMTP id 29223E09E3
for <gentoo-dev@lists.gentoo.org>; Mon, 1 Mar 2010 21:17:43 +0000 (UTC)
Received: by ewy22 with SMTP id 22so2086059ewy.26
for <gentoo-dev@lists.gentoo.org>; Mon, 01 Mar 2010 13:17:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type
:content-transfer-encoding;
bh=cjS3exrxm7njq7OkyA/m9EqChTpvYsiaJ7Ui+nZOtuA=;
b=mBanpjmJJMvd11NvSUv63i3ERU8J3bU/sfwEttSUBjxFa6XAd+PWnGRv0DNqDYXhMX
jny8HEHglYgVn3gCFJ78PdN2FrPhzK06QagWZ3dbjJHITCYgQ24tNHWsZWQCTffLuk70
Rsdpho8pGqtFNMOGyO0fpawQtuTbdi0G0WMok=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type:content-transfer-encoding;
b=jncKuoRBIc8/ROL2PbDn1sSqHGD3j9KizzgQU2uXj/YlFCwNfR8M6Y7jrRsULLNNMn
3ggwqBK9fgMFQC74IrbeW0KkEUd53/M6Nex2qH4m2SBVwbggEB6g+UwJK8GFsZHm0YhN
+sJezXAXMkWEdaYIMAO7GZKsUCdVyvz1/FVJQ=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.213.2.75 with SMTP id 11mr3696061ebi.14.1267478262225; Mon, 01
Mar 2010 13:17:42 -0800 (PST)
In-Reply-To: <20100228173504.78eea0b1@angelstorm>
References: <4B889D1F.3040304@gentoo.org>
<201002282154.35130.hwoarang@gentoo.org> <4B8ACC34.7000600@gentoo.org>
<20100228173504.78eea0b1@angelstorm>
Date: Mon, 1 Mar 2010 22:17:42 +0100
Message-ID: <ea440b1d1003011317j24a550b2id2653d8061757c94@mail.gmail.com>
Subject: Re: [gentoo-dev] Marking bugs for bugday?
From: Ioannis Aslanidis <aslanidis@gmail.com>
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 811a5de9-643c-4e70-bd25-ffe3cd433d54
X-Archives-Hash: 70ea5930d2f374020bbcd884e826d0a9
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 <nightmorph@gentoo.org> wrot=
e:
> On Sun, 28 Feb 2010 21:04:04 +0100
> Sebastian Pipping <sping@gentoo.org> 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 be=
fore
>> > we even consider resurrect this project
>>
>> welp =C2=A0 =C2=A0 =C2=A0 =C2=A0 -> away
>
> He's not away, he's retired. It's just taken several months to close his =
bug.
>
>> gurligebis =C2=A0 -> no reply yet
>
> I thought gurli was also retired.
>
>
--=20
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0