Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE Bugzilla Future
Date: Fri, 11 Mar 2011 13:17:16 +0100	[thread overview]
Message-ID: <ild3sc$enc$1@dough.gmane.org> (raw)
In-Reply-To: <20110311101752.GI7353@excalibur.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-03-11 11:17, Stefan Schmidt wrote:
> Hello.
> 
> On Fri, 2011-03-11 at 10:05, Koen Kooi wrote:
>> On 11-03-11 09:19, Stefan Schmidt wrote:
>>>
>>> This topic has come up several times now and it did come up again during a TSC
>>> meeting yesterday.
>>>
>>> It feels like the current OE bugzilla is not in really good shape. The question
>>> is how we are going to handle this. On the one hand it might be good to remove
>>> as it holds a lot outdated informations and it seems developers are not using it
>>> at all.
>>>
>>> On the other hand this would cut off a service for atcual users of OE.
>>>
>>> If we can find a group of people that is willing to clean the current bugzilla
>>> up improve it and make sure that problems in it are actually worked on it still
>>> have a chance to stay. We need a clear maintainership for it and bugs need
>>> atcually be worked.
>>>
>>> Comments? Volunteers?
>>
>> Just kill it already, for OE-core we can use the yocto bugzilla which
>> has dedicated maintainers.
> 
> That leaves still a big part of the metadat without bugzilla coverage.
> meta-openembedded. If we find a group of people maintaining it I don't see a
> problem with the OE bugzilla to stay.

I stopped using OE bugzilla when the maintainer at that time was closing
bugs because patches were posted to the mailinglist for review instead
of attached to bugzilla.
So if the new maintainers are crazy like that bugzilla will be useless.

Maybe we can use something like trac or redmine to have it more
integrated with the SCM. Hell, we could even abuse patchwork as
bugtracker :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNehLMMkyGM64RGpERAnZeAJ9I/A43aBEZmAQB2vYbVDdwEKGTkQCfQFT+
NBTU7ROL4oul5LWGnIIACwA=
=OEJI
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-03-11 12:19 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 [this message]
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

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='ild3sc$enc$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox