Comment 9 for bug 43319

I wrote software for over a decade and worked with many testers and I know
that rejecting a bug against the person who went to the trouble of isolating
and filing the bug isn't good either. When a bug gets rejected and forgotten
about, the knowledge gets lost.

Yes, I definitely agree you guys have lots of bugs to fix, but just because
you are buried in bugs doesn't mean you should start rejecting them. It
might make you feel better, but it doesn't make the codebase any better.

You tell me to file a bug upstream, but then shouldn't this bug stay around?
Are you saying that bugs with upstream links should be rejected?

I watch videos but also listen to a lot of music--Totem isn't just about
video otherwise it wouldn't have visualizations.

I would open a bug upstream if I knew for sure it happened there. Who added
goom to totem--Debian or Gnome?

I don't know why you keep saying this bug is a collection of different
issues. Its all related to visualizations and totem-gstreamer. I could see
breaking it up into 2 bugs:
goom in totem-gstreamer doesn't support high resolution
visualization choices in totem-gstreamer aren't the same as totem-xine.

Would it make you feel better if I filed it as 2 bugs? Or would you just
reject those as well?

the point about sabdfl is that I'll bet he wouldn't consider this a 'pie in
the sky' wishlist feature.

On 5/10/06, Sebastien Bacher <email address hidden> wrote:
>
> Some points to reply to your flood of comment:
> - usually playing with the bug settings against the maintainers willing
> will not force them to accept your opinion but rather make them ignore you
> or conflict on that rather discussing on the bug, better to argue to get
> them changing those than trying to force them by yourself
> - the codebase is not the same, the visualizations come from libxine and
> gstreamer, goom for totem-gstreamer is by example:
> gstreamer0.10-plugins-good: /usr/lib/gstreamer-0.10/libgstgoom.so
> - upstream keep feature request because they are the guys who write the
> code and where a new feature is likely to be coded, we do packaging,
> stabilization, integration, bug fixing, etc so we have no interest to keep
> feature requests we will no work on
> - usually we forward feature request upstream but that one is a collection
> of different issue, with no precise points and with most assigned to wrong
> place
> - if you want feel free to show that bug to the sabdfl, look at the
> launchpad list, there is lot of bugs to fix but few people working on them
> so it'll take time and we have to prioritize the work, he probably knows
> about that
> - I don't think people will stop using the video player because it has not
> good visualization, they watch videos with it
>
> Now you want try something? Open the same bug you opened here on
> bugzilla.gnome.org and wait if upstream has a better reply for it,
> upstream is the right place to get that worked anyway
>
> ** Changed in: totem (Ubuntu)
> Severity: Normal => Wishlist
> Priority: None => Low
> Status: Unconfirmed => Rejected
>
> --
> Visualization options are worse than totem-xine
> https://launchpad.net/bugs/43319
>