Bug#247312: konqueror: opening of bookmarks is much slower when clicking directly on Bookmarks menu
* Hervé Eychenne [Fri, 07 Jan 2005 03:57:56 +0100]:
> > can I ask you a simple question: why haven't done it yourself?
> Done what? Forwarded it to KDE people and tagged the bug as upstream,
> you mean?
yes.
> Simply because I'm not a Debian developper myself, just a simple user,
> and mostly because the Debian way of doing things (correct me if I'm wrong)
> offers the possibility to report bugs to Debian and let the package
> maintainers deal with them whether they are Debian-specific or not.
ok, that's an answer. not that I agree with it, but yes, Debian says
it will take care of bugs and it will. but...
> So, if some Debian maintainers should "refuse" to tag and forward
> upstream bugs to upstream, let's all get rid of this upstream tag
> everywhere, let's inform users explicitely that they have to deal with
> upstream directly, and modify the Debian procedures accordingly.
it's *not* a question of "refusing". it's a question of *time*. KDE
maintenance is a very time consuming time, and there is currently not
enough people.
we always welcome contributors, but we also expect users to understand
that we are overloaded, and we'd like them to assume that, if they
don't get a timely response, it's because we missed the report or
can't deal with it, *not* because we are just sitting there, doing
nothing, watching bug reports pass by...
> But until that change is decided/done, if some Debian maintainers are
> unable to do this tagging and forwarding within a decent amount of time,
> they should really be considered as failling to do their maintainer's
> job properly, ok?
yes, but there my be alleviating circumstances. bugs are being worked
on, really. not to blow my own horn, but see #288779: I *doubt* you
can get better response than that... bugs are trying to be handled, to
the best of our capabilities.
what's the difference between #288779 and yours? simply, #288779 is
*recent*. yours is buried in my mailbox, together with >400 old bugs
that receive no traffic and that we should check sometime [your
message from July 2nd is marked as unread; if I had had chance to read
it, you would have gotten a reply].
see, when you pinged us back, you got a response. right, I could have
be more helpful, but I already give much of my time to KDE, and,
frankly, you catched me in a bad moment. some other day, I would've
looked into the report. everybody has a bad day, right?
> So, I did fill this bug to Debian because I could, and because I
> (naively) thought it would be a so simple and usual thing for them
> to process.
note that my question was not "why did you initially report this to
Debian and not to upstream directly?". the question was: "why did you
not report upstream *after* seeing no action from Debian people?" as I
said, we weren't sitting idle, doing nothing, and wathing bug reports
go by. and you? (no, you needn't answer that.)
> What I would like to understand now is why the Debian counterpart failed
> to manage such a simple thing til now (more than 7 months of delay for a
> few minutes operation, let's face it).
time, as I said.
> But frankly, I would prefer that, instead of replying to this post,
> any responsible Debian person would step up and take these 2 minutes
> of his time to do it at last.
I would have certainly done that yesterday. Will try to do tomorrow,
or perhaps somebody else steps in.
> Herve
dato.
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
He has never been known to use a word that might send a reader to the
dictionary.
-- William Faulkner (about Ernest Hemingway)
Reply to: