public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Low hanging bug fruit patterns
Date: Mon, 08 Mar 2010 18:31:22 +0100	[thread overview]
Message-ID: <4B95346A.5070403@gentoo.org> (raw)
In-Reply-To: <20100308170809.GM30005@halcy0n.com>

On 03/08/10 18:08, Mark Loeser wrote:
> What is this even in reference to?  Its not at all clear what you are
> trying to do.

Okay, sorry.

I was wondering what classes of bugs there are that are

 - reoccuring (therefore beloning to a "class" or "pattern")

 - relatively easy to fix

 - ideally suited for non-maintainer updates,
     i.e. stuff where the original maintainer just won't mind
     that you touched "his" ebuild, even if he feels more or less
     like its owner

From such patterns I expect:

 - to find candidates more easy when I myself want to fix something
   within limited time

 - raising awareness on these bugs in hope other feel motivated
   to look outr and fix for some of those, too.

 - use these patterns to find future bugday candidates

A bit clearer now?



Sebastian



  reply	other threads:[~2010-03-08 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 10:06 [gentoo-dev] Low hanging bug fruit patterns Sebastian Pipping
2010-03-08 13:13 ` Róbert Čerňanský
2010-03-08 17:37   ` Sebastian Pipping
2010-03-08 23:17   ` Jeroen Roovers
2010-03-09 18:24     ` Róbert Čerňanský
2010-03-09 23:17     ` [gentoo-dev] " Duncan
2010-03-08 13:27 ` [gentoo-dev] " Markos Chandras
2010-03-08 17:33   ` Sebastian Pipping
2010-03-08 14:42 ` Angelo Arrifano
2010-03-08 17:08 ` Mark Loeser
2010-03-08 17:31   ` Sebastian Pipping [this message]
2010-03-08 18:00 ` Mike Frysinger

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=4B95346A.5070403@gentoo.org \
    --to=sping@gentoo.org \
    --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