From: Ioannis Aslanidis <aslanidis@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Marking bugs for bugday?
Date: Mon, 1 Mar 2010 23:26:53 +0100 [thread overview]
Message-ID: <ea440b1d1003011426hdc97dc4p55666fa51f34bcee@mail.gmail.com> (raw)
In-Reply-To: <e117dbb91003011419if3b25fnef03dc6c0e86e69d@mail.gmail.com>
I understand that the implication and the time demand of this last
point may be a little excessive. If anyone still has the time to fill
the skeleton in, they are still welcome to do it. Otherwise with the
bug list it will be enough. I would prefer to keep the keyword for
Bugday Members to administer.
On Mon, Mar 1, 2010 at 11:19 PM, Ben de Groot <yngwin@gentoo.org> wrote:
> On 1 March 2010 22:17, Ioannis Aslanidis <aslanidis@gmail.com> wrote:
>> [...]
>
> Great ideas!
>
>> 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.
>
> This will not work. You need to keep things really simple for our devs.
> I don't see anybody but the most dedicated ones, who also happen
> to have a lot of time on their hands, fill out such a detailed form.
>
> I'd say let devs just nominate bugs, either by adding BugDay to
> the keywords field or something similar, or by passing the bugday
> team a list of bug numbers. Then the bugday team can sort these
> and see if any instructions are needed. They could always ask the
> involved devs/teams for more info when necessary.
>
> Cheers,
> --
> Ben de Groot
> Gentoo Linux developer (qt, media, lxde, desktop-misc)
> ______________________________________________________
>
>
--
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0
next prev parent reply other threads:[~2010-03-01 22:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 4:18 [gentoo-dev] Marking bugs for bugday? Sebastian Pipping
2010-02-27 15:39 ` Roy Bamford
2010-02-27 17:42 ` Sebastian Pipping
2010-02-27 16:22 ` Mark Loeser
2010-02-27 17:38 ` Sebastian Pipping
2010-02-27 18:14 ` Roy Bamford
2010-02-27 20:15 ` Sebastian Pipping
2010-02-27 20:46 ` Dale
2010-02-27 20:48 ` Mark Loeser
2010-02-27 21:45 ` Ben de Groot
2010-02-27 23:14 ` Mark Loeser
2010-02-28 9:36 ` Dawid Węgliński
2010-02-28 13:15 ` Alexander Færøy
2010-02-28 0:22 ` [gentoo-dev] " Ryan Hill
2010-02-28 19:54 ` [gentoo-dev] " Markos Chandras
2010-02-28 20:04 ` Sebastian Pipping
2010-03-01 1:35 ` Joshua Saddler
2010-03-01 21:17 ` Ioannis Aslanidis
2010-03-01 22:19 ` Ben de Groot
2010-03-01 22:26 ` Ioannis Aslanidis [this message]
2010-03-02 0:02 ` Sebastian Pipping
2010-03-02 0:15 ` Ioannis Aslanidis
2010-03-02 1:09 ` [gentoo-dev] " Duncan
2010-03-02 1:32 ` Alec Warner
2010-03-02 19:09 ` Sebastian Pipping
2010-03-02 19:08 ` Sebastian Pipping
2010-03-02 19:17 ` Ulrich Mueller
2010-03-02 19:28 ` Nathan Zachary
2010-03-02 19:39 ` Sebastian Pipping
2010-03-02 19:42 ` Nathan Zachary
2010-03-06 14:45 ` Robert Buchholz
2010-03-06 15:26 ` Ioannis Aslanidis
2010-03-06 19:09 ` David Leverton
2010-03-06 20:22 ` Ioannis Aslanidis
2010-03-07 4:30 ` Sebastian Pipping
2010-03-07 12:23 ` David Leverton
2010-03-08 3:19 ` Ryan Hill
2010-03-01 22:46 ` [gentoo-dev] " George Prowse
2010-03-01 22:48 ` Mark Loeser
2010-03-02 19:36 ` Sebastian Pipping
2010-03-02 20:47 ` Alec Warner
2010-03-02 21:05 ` Sebastian Pipping
2010-03-02 21:28 ` Alec Warner
2010-03-02 20:59 ` Ioannis Aslanidis
2010-03-04 19:13 ` Roy Bamford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea440b1d1003011426hdc97dc4p55666fa51f34bcee@mail.gmail.com \
--to=aslanidis@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox