[gstreamer-bugs] [Bug 336110] New: move taglib-based ID3 muxer to -good

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=336110
 GStreamer | gst-plugins-good | Ver: HEAD CVS

           Summary: move taglib-based ID3 muxer to -good
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


I would like to move the taglib-based ID3 muxer from -bad to -good.

Going through the checklist:

 * I am willing to actively maintain the element, but I'm sure that
   Christophe (who has written it originally) would be equally willing
   to maintain it.

 * plugin's code:
    - base class: N/A
    - uses boilerplate macros
    - conforms to GStreamer coding style
    - has a custom debug category
    - uses GST_*_OBJECT where possible

 * compiled plugin
    - shows up properly in gst-inspect

 * is in the correct location (/ext)

 * documented:
    - correct element description and plugin description
    - has a gtk-doc blurb with pipeline example

 * unit tests:
    - will be attached below
    - test is leak-free with valgrind

 * license:
    - plugin code is LGPL
    - taglib is LGPL

 * docs will be added to the build once it is actually in the -good repository.


Some CVS surgery to do the move would be nice, but is not essential.

In the course of the move, I would also like to rename the source files:

   gsttaglib.cc => gsttaglibmux.cc
   gsttaglib.hh => gsttaglibmux.hh


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.