Using the community to help solve core bugs

[Hans de Goede]

Hi all,

I've just taken a good look at ImageMagick after being bitten by a bug
in convert, which I use in some of my spec files.

The open bug list on ImageMagick is quite long (not really long though)
and some of those bug look like they are not too hard to fix. So it
looks like ImageMagick could use some love and attention.

Now without doubt the same goes for many other core packages. I have the
feeling that with the ever growing and competent FE community we are
missing out on a chance here. We need some kinda mechanism for Core
package maintainers to mark bugs as
"easy fix" or
"fixing this should be doable, packaging"
"fixing this should be doable, C programming"
"fixing this should be doable, PERL"
etc.

So that Core package maintainers who as we all know are a bit swamped
can mark bugs, which look like low priority but should be fixed never
the less, with one of these and FE contributers interested in helping
out can then find these bugs by these markers (blocker bugs / keywords?)
and write a patch.

Preferably in the end some in the community should get direct access to
FC cvs / svn so that we can really _scale_ up the developer effort put
into core.

Regards,

Hans