There are a few patterns for potentially low hanging fruits among Gentoo
bugs:
SRC_URI errors
Missing depencies
...
What else?
Anything you look after repeatedly that doesn't "take days" to get it fixed?
Sebastian
03-08-2010, 12:13 PM
Róbert Čerňanský
Low hanging bug fruit patterns
On Mon, 08 Mar 2010 11:06:40 +0100
Sebastian Pipping <sping@gentoo.org> wrote:
> There are a few patterns for potentially low hanging fruits among
> Gentoo bugs:
>
> SRC_URI errors
> Missing depencies
(Sorry for answering a developer targeted question while I'm not one.)
- Minor version bumps (After examination what upstream changed and
after confirmation with mantainer, if any.)
And perhaps also:
- Stable requests
- New ebuilds
Robert
--
Robert Cernansky
E-mail: hslists2@zoznam.sk
Jabber: hs@jabber.sk
03-08-2010, 12:27 PM
Markos Chandras
Low hanging bug fruit patterns
On Monday 08 March 2010 12:06:40 Sebastian Pipping wrote:
> Hello!
>
>
> There are a few patterns for potentially low hanging fruits among Gentoo
> bugs:
>
> SRC_URI errors
> Missing depencies
> ...
>
> What else?
>
> Anything you look after repeatedly that doesn't "take days" to get it
> fixed?
>
>
>
> Sebastian
Documentation installation
There are few packages that call missing documents on dodoc commands
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
03-08-2010, 01:42 PM
Angelo Arrifano
Low hanging bug fruit patterns
On Seg, 2010-03-08 at 11:06 +0100, Sebastian Pipping wrote:
> Hello!
>
>
> There are a few patterns for potentially low hanging fruits among Gentoo
> bugs:
>
> SRC_URI errors
> Missing depencies
> ...
>
> What else?
>
> Anything you look after repeatedly that doesn't "take days" to get it fixed?
>
>
>
> Sebastian
>
* Missing/crappy ebuild USE flag description on metadata.
That is something, I think, that always help users. There is nothing
worse than rebuilding a entire package just because the USE flag purpose
was not what we think it was.
Sebastian Pipping <sping@gentoo.org> said:
> Hello!
>
>
> There are a few patterns for potentially low hanging fruits among Gentoo
> bugs:
>
> SRC_URI errors
> Missing depencies
> ...
>
> What else?
>
> Anything you look after repeatedly that doesn't "take days" to get it fixed?
What is this even in reference to? Its not at all clear what you are
trying to do.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
03-08-2010, 04:31 PM
Sebastian Pipping
Low hanging bug fruit patterns
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
03-08-2010, 04:33 PM
Sebastian Pipping
Low hanging bug fruit patterns
On 03/08/10 14:27, Markos Chandras wrote:
> Documentation installation
> There are few packages that call missing documents on dodoc commands
any idea how to find all these bugs?
sebastian
03-08-2010, 04:37 PM
Sebastian Pipping
Low hanging bug fruit patterns
On 03/08/10 14:13, Róbert Čerňanský wrote:
> On Mon, 08 Mar 2010 11:06:40 +0100
> Sebastian Pipping <sping@gentoo.org> wrote:
>
>> There are a few patterns for potentially low hanging fruits among
>> Gentoo bugs:
>>
>> SRC_URI errors
>> Missing depencies
>
> (Sorry for answering a developer targeted question while I'm not one.)
happy to have your input.
> - Minor version bumps (After examination what upstream changed and
> after confirmation with mantainer, if any.)
needs good care and a little luck, but still, yes.
> - Stable requests
only if you're an arch tester.
> - New ebuilds
that's a tough one too, because it's often not a good idea to pull
something into the tree, e.g. when you don't use it yourself on a
regular basis. i have done that before, but i think twice by now.
sebastian
03-08-2010, 05:00 PM
Mike Frysinger
Low hanging bug fruit patterns
On Monday 08 March 2010 05:06:40 Sebastian Pipping wrote:
> There are a few patterns for potentially low hanging fruits among Gentoo
> bugs:
work with the bugday guys to get this incorporated into their documentation
On Mon, 08 Mar 2010 14:13:30 +0100
Róbert Čerňanský <hslists2@zoznam.sk> wrote:
> - Minor version bumps (After examination what upstream changed and
> after confirmation with mantainer, if any.)
The stuff you put in brackets is exactly the sort of stuff that
tends to make version bumps hard to fix.
You would first have to determine what major/minor means, on a per
package-version basis, so these aren't really as trivial to fix as (non)
package maintainer as a "minor version change" might suggest.
Also, any version bump is a splendid occasion on which to revise the
ebuild (introduce missing features, check for novel QA issues, move up
an EAPI to cut out a few build phases, review COPYING to make sure
the LICENSE variable is still OK, figure out that one slight syntax
change might serve to fix a compilation error with a
newer-toolchain-than-you-use).
So I generally don't regard a version bump as a low hanging fruit,
as you might end up painfully ignoring the wasps' nest hanging
directly beside it.