public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Levente Kurusa <levex@linux.com>
To: "Gideon D'souza" <gidisrael@gmail.com>,
	Nick Krause <xerofoify@gmail.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Cleanup of Kernel Bugzilla
Date: Sun, 29 Jun 2014 09:21:46 +0200	[thread overview]
Message-ID: <53AFBE8A.3020408@linux.com> (raw)
In-Reply-To: <CAPNrq4yZTFXhPG4U5H4mqFw-xbvJL5Ht-XofwKTqApgM2jsAGQ@mail.gmail.com>

Hi,

[Why was stable on Cc?]

On 06/29/2014 08:33 AM, Gideon D'souza wrote:
>> Why do you want an up to date list of kernel bugs?
>
> Even I'm a newbie and was looking for the same thing. I read
> eventually somewhere that bugzilla isn't maintained by kernel devs so
> I entirely gave up trying to find a bug to adopt.
>
> Many open source projects I've worked on (web frameworks mostly) have
> a well maintained list of bugs and tag the right ones "newbie" or
> "beginner suitable" and newbies can learn the ropes and get started
> easy. Even chromium has a "GoodFirstBug" tag for newbies.

I think that is because they are relatively young and they are generally
used for one direct purpose. The kernel has to make sure it works in a lot
of different situations and hence a lot of different bugs arise.

The kernel is old, and hence most of the JuniorJobs (as KDE calls them)
are either already fixed, or fixed right on the spot when they are discovered.

>
> With the linux kernel not only doesn't anything exist, the project
> itself is so bloody hard right, kernel programming, most of the
> bugzilla bugs I can barely understand let alone even begin to deduce
> what is going on. Now given that the list itself isn't maintained
> makes things extremely hard.

There are still methods to extract various unresolved bugs from the
bugzilla though. Look in any subsystem you find delicious and then
just sort the bugs by the date they were modified. This will yield
a list of nice fresh bugs along with some recently fixed bugs.

>
> Thanks @Nick for bringing this up. I would love to help you clean up
> the bugs, give me an email of any ideas you have on how to start.
>

I brought this up as well on the Kernel Summit list. There wasn't any
feedback on this :-), I guess there are some maintainers who care about
bugzilla, but the rest (and the majority probably) does not care.

I tend to think that even if we clean up the bugzilla, it will only be a
question of time until it gets to the state that it is in now.

Thanks,
     Levente Kurusa

  reply	other threads:[~2014-06-29  7:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 18:11 Cleanup of Kernel Bugzilla Nick Krause
2014-06-28  2:45 ` Nick Krause
2014-06-28 16:06   ` Nick Krause
2014-06-28 16:55     ` Theodore Ts'o
2014-06-28 16:36   ` Theodore Ts'o
2014-06-28 19:18   ` One Thousand Gnomes
2014-06-29  3:04     ` Nick Krause
2014-06-29  6:33       ` Gideon D'souza
2014-06-29  7:21         ` Levente Kurusa [this message]
2014-06-29 21:32           ` Theodore Ts'o
2014-06-30  2:09             ` Nick Krause
2014-06-30 12:42               ` Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2014-06-27  2:44 Nick Krause

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=53AFBE8A.3020408@linux.com \
    --to=levex@linux.com \
    --cc=gidisrael@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xerofoify@gmail.com \
    /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