All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bugzilla Status (pitiful, penoso, penible, bedauerlich)
Date: Fri, 27 Mar 2009 13:46:28 -0400	[thread overview]
Message-ID: <49CD10F4.5050609@balister.org> (raw)
In-Reply-To: <200903271652.33801.mickey@vanille-media.de>

[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

Michael 'Mickey' Lauer wrote:
> On Friday 27 March 2009 15:19:39 Cliff Brake wrote:
>> On Wed, Mar 25, 2009 at 8:49 AM, Michael 'Mickey' Lauer
>>
>> <mickey@vanille-media.de> wrote:
>>> Am Mittwoch, den 25.03.2009, 12:04 +0100 schrieb Koen Kooi:
>>>> On 25-03-09 11:14, Andrea Adami wrote:
>>>>> Bump
>>>> As I said, let's close it down.
>>> -1000. Lets continue cleaning it up.
>> Building on Chris's push for package maintainers -- perhaps we need to
>> insist on style guidelines for bugs as well where we prefix the bug
>> title with the component name (like repo commits), or create separate
>> components for every directory in recipes, machines, and perhaps a
>> catch-all for core files.  Then the maintainer for the component could
>> decide if the bug is valid, and close it if not.  If bugs collect for
>> a component, and nothing gets done, then we need to search for a
>> maintainer, or mark the recipe unmaintained.  I guess the difficult
>> part is all this needs active management.  Somehow if we can get bugs
>> assigned to the right people (listed in the maintainers file), then
>> maybe it would work better.
> 
> Good thinking. I actually love the GNOME folks bugzilla interface. They run 
> you through a set of questions / choices. That way it takes a bit longer to 
> create a bug but it's more structured.

Bugzilla came up in the IRC stable branch meeting. Basically, who is the 
audience for the OE bugzilla? Distro users? Distro's should really set 
up their own bug reporting system.

I'm not sure what the real answer is here, but we should put some effort 
into deciding who the intended users of bugzilla are, and make sure we 
meet their needs.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-03-27 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 10:14 Bugzilla Status (pitiful, penoso, penible, bedauerlich) Andrea Adami
2009-03-25 11:04 ` Koen Kooi
2009-03-25 12:35   ` Vitus Jensen
2009-03-25 14:13     ` Philip Balister
2009-03-25 12:49   ` Michael 'Mickey' Lauer
2009-03-27 14:19     ` Cliff Brake
2009-03-27 15:52       ` Michael 'Mickey' Lauer
2009-03-27 17:46         ` Philip Balister [this message]
2009-03-28 17:32           ` Cliff Brake
2009-03-29  9:26       ` Rolf Leggewie
2009-03-29 12:01         ` Frans Meulenbroeks

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=49CD10F4.5050609@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.