From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE Bugzilla Future
Date: Mon, 21 Mar 2011 09:23:36 +0100 [thread overview]
Message-ID: <im71u8$eol$1@dough.gmane.org> (raw)
In-Reply-To: <4D86B486.6030205@mentor.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 21-03-11 03:14, Tom Rini wrote:
> On 03/18/2011 12:57 AM, Frans Meulenbroeks wrote:
>> 2011/3/17 Richard Purdie<richard.purdie@linuxfoundation.org>:
>>> On Thu, 2011-03-17 at 19:10 +0100, Michael 'Mickey' Lauer wrote:
>>>> I'm in favor of keeping it, cleaning it up, and improve
>>>> the integration with patchwork / git. Throwing it away
>>>> would be a very bad sign to all those countless people
>>>> who've gone through the pains of actually working with
>>>> the bugtracker.
>>>
>>> The simple question is who is actually going to sort out the mess its
>>> in?
>>>
>>> Who is going to look after it on a continuing basis?
>>>
>>> If there isn't ownership, nothing is going to change.
>>
>> Actually I feel the real problem is that:
>> - people did not want to get bugs assigned to them (at least that was
>> what someone told me in the past)
>> - we're lacking a good notion of package or recipe ownership, so even
>> if we had someone acting as a bug manager, (s)he would have a hard
>> time to find out who to assign an issue to.
>>
>> and of course it takes discipline to look at regular intervals in the
>> bug tracker to see if there are issues that affect the recipes you
>> feel responsible for.
>> A discipline that few people have and that is also easy to forget if
>> there is only very rarely something for you.
>>
>> So it is more of a process issue.
>> (btw this may be something that could be picked up by the TSC).
>
> The feeling of the TSC thus far has been "where are the active
> volunteers to use BTS (bugzilla, whatever)". This far in the thread I
> count one.
I count none, actually, since you said 'active volunteers'.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNhwsIMkyGM64RGpERApNUAJ9V86nRpwP8mTNW9b48FdaTjrTBMgCfXteG
GzEx7YQ0Mpuw1Yq1A2ZH6ao=
=UJ6A
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-03-21 8:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 8:19 OE Bugzilla Future Stefan Schmidt
2011-03-11 9:05 ` Koen Kooi
2011-03-11 10:17 ` Stefan Schmidt
2011-03-11 12:17 ` Koen Kooi
2011-03-11 10:00 ` Graeme Gregory
2011-03-11 14:38 ` Philip Balister
2011-03-11 15:27 ` Eric Bénard
2011-03-11 15:39 ` Tom Rini
2011-03-11 16:27 ` Graeme Gregory
2011-03-11 18:05 ` Otavio Salvador
2011-03-11 22:01 ` Khem Raj
2011-03-17 18:10 ` Michael 'Mickey' Lauer
2011-03-17 21:14 ` Richard Purdie
2011-03-18 7:57 ` Frans Meulenbroeks
2011-03-18 10:15 ` Phil Blundell
2011-03-19 1:03 ` Richard Purdie
2011-03-19 8:28 ` Frans Meulenbroeks
2011-03-20 16:02 ` Philippe De Swert
2011-03-20 18:18 ` Khem Raj
2011-03-20 21:08 ` Frans Meulenbroeks
2011-03-21 1:24 ` Khem Raj
2011-03-21 10:08 ` Richard Purdie
2011-03-21 12:33 ` Frans Meulenbroeks
2011-03-21 2:14 ` Tom Rini
2011-03-21 3:24 ` Khem Raj
2011-03-21 8:23 ` Koen Kooi [this message]
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='im71u8$eol$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.