After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 569317 - [PLUGIN-MOVE] Move twolame plugin from -bad to -ugly
[PLUGIN-MOVE] Move twolame plugin from -bad to -ugly
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
git master
Other Linux
: Normal blocker
: 0.10.11
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-27 11:24 UTC by Sebastian Dröge (slomo)
Modified: 2009-03-10 01:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2009-01-27 11:24:50 UTC 
Hi,
it'd be nice if the twolame plugin could be moved from -bad to -ugly for the next release. It has documentation and the code is based on the code of the lame plugin and should be at least as good ;)
Comment 1 Jan Schmidt 2009-01-27 11:47:56 UTC 
Why to -ugly? Isn't the point of twolame that it doesn't have the encumbrance issues of lame/mp3?
Comment 2 Sebastian Dröge (slomo) 2009-01-27 11:57:13 UTC 
If that's the case and there are no doubts it could as well go to -good, right ;)

But then we probably also want mp3parse and friends in -good (mp3parse is needed for muxing (two)lame output into most containers)... and people are usually scared if they hear "MPEG" and immediately think of patent issues :)
Comment 3 Michael Smith 2009-01-27 17:59:14 UTC 
mpeg audio Layer 2 still has patent encumbrance issues afaik, though (unlike mp3) I don't know of anyone actively trying to enforce them, and there are fewer issues to begin with. It's also possible that the relevant patents are all expired by now - but unless we have clear advice that it's safe, I'd prefer to keep it in -ugly.

Moving mp3parse to -good is an independent issue; we should probably do that at some point (it's confusing to people to have it in -ugly).
Comment 4 Edward Hervey 2009-03-06 08:49:33 UTC 
Are we moving it or not ? And if so, where ?
Comment 5 Jan Schmidt 2009-03-06 23:31:44 UTC 
In the absence of clearer guidelines, and since it'd be best to have mp3parse in -good too if it went there, I'm moving it to -ugly.
Comment 6 Jan Schmidt 2009-03-10 01:33:00 UTC 
The plugin has been moved to ugly.