> As the ffmpeg developers do not follow nor even notice bugs > launchpad, and additionally have clear instructions for reporting such > bugs (which are clearly not followed here), I don't see what we as > ubuntu developers can do about this bug other than asking the submitters > to follow the ffmpeg upstream's bug submission guidelines > (i.e. submitting a proper example file).
Pretend you're me for a minute (Joe User) and you think you might have a high level understanding of the process (but you most likely do not). You take the time to file a bug because you see this as a way to contribute to the Ubuntu project. Then you're told that you did it wrong, your bug is closed and no feedback given as to how to "do it right". Imagine how interested you'll be the next time you see an opportunity to "help make Ubuntu better". Seriously, how am I suppose to know that ffmpeg developers don't come here? How am I suppose to know _where_ to visit the ffmpeg upstream bug submission site? How am I suppose to know what the ffmpeg upstream bug submission guidelines are? Anyways, cheers. I gave up on this whole bug a few months ago, stopped donating money to Canonical, got smart and realized that if I want to have proper media support, that I'd need to purchase a Mac. -- Missing support for AVCHD (MTS/M2TS) https://bugs.launchpad.net/bugs/327872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
