Leon wrote: > Hans de Goede <j.w.r.degoede@xxxxxx> writes: > >> 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 > > This is excellent idea. For example, the firefox miniicon[1] issue. It's > an easy fix but probably takes 4-5 years before the developers address > it. There are just too many bugs. > This indeed looks like an easy fix, why don't you create a (tested) patch against the latest spec file in the devel branch fixing this. That would make the chances of it getting fixed much bigger. Regards, Hans -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
