On Tue, 24 Sep 2013 13:04:18 +0000
"Jóhann B. Guðmundsson" <johannbg(a)gmail.com> wrote:
> I've added it because have stated "bugs" go
unanswered.
> That is the "problem" need fixing, not bugzilla.
There are 4 reasons that happens.
1. the packager is gone awol
1a: Not a buzilla problem, housekeeping
2. the packager does not know how to fix
2a: If it a bug, that is know upstream link it,
if it's fedora packing\config issue, help him understand
3. the maintainer lacks time to fix it.
3a: Then should he be maintainer, if he cannot maintain?
4. bugzilla is not the interface the maintainer finds effective so
he ignores it
It it part of fedora, help him learn it's ways
>
> Is missing maintainer period too long?
> Extra co-maintainers needed, with commit access?
>
> Now can you throw as much endeavour into helping resolve that
>
To effectively resolve that you need to reduce the total number of
components in the distribution as well as how many components
maintainer is allowed to maintain as well as finding the
communication interface with the maintainer which he finds
effective.
Agreed, or get maintainers in, and help them understand Fedora ways.
But, I agree if John Does, want to bring in package foo,
as his admittance price. Then he best know it's every inch.
Reporting upstream is one solution to the interface problem,
What if they too have bugzilla, bummer.
The problem with many upstream is the dreaded "Works for me"
detecting poorly maintained packages as well as orphaning
unmaintained packages and coming up with a time sharing program
takes care of the rest.
(1a) ^
With the exception of reporting directly upstream which I have been
always against, I pointed out the other things and you can find the
discussion surrounding that in the archives on devel.
I'm not against reporting upstream, for a specific issue,
where maintainer has said, can you please report upstream,
as problem is agnostic.
Gnome is a special case, as upstream <> downstream can be overlapped,
and the gnome-sig know their pkgs.
--
Regards,
Frank
www.frankly3d.com