Please follow the netiquette when posting on Libav mailing lists, especially avoid top-posting and thread hijacking (that is, replying to a thread and changing the subject line to something completely unrelated that was not being discussed within the original thread). Configuring your mail client to break lines after 70 or so characters is a plus. If you attach files, avoid compressing small files, uncompressed is preferred. Also please try to avoid posting mails with overly long signatures or nonsense corporate disclaimers that claim the content of your mails is confidential.
Attached patches should not have application/octet-stream as mime-type, but
text/plain or even better text/x-diff or text/x-patch.
If you send us a patch, please make it some form of unified diff. We prefer
patches made using
git format-patch from your Libav local clone,
they can be sent directly using
More detailed guidelines are available in the
submitting patches section
of our developer documentation.
This list is for development of Libav itself. It is not for
development of software that use the Libav libraries and not
for bug reports.
libav-commits: This list gets all changes to the Libav sources.
libav-stable: This list gets all the commits destined for and discussion related to the stable branches of Libav.
libav-api: This list is for development with the Libav libraries.
libav-tools: This list is for regular user questions like compilation troubles, command-line issues and usage of the Libav tools.
libav-security: Security contact, report vulnerabilities here.
libav-bugs: All messages from the Bugzilla bug tracking system. Please respond via Bugzilla rather than directly to this list.
To read up on past discussions, read the mailing list archives. It is highly likely that you will find an answer to your questions there, so make sure to browse the archives before posting questions.
The archives of the old FFmpeg mailing lists are still all at.
Libav has two official channels on the freenode IRC network. Both channels are open and unmoderated. Developers with commit rights have operator status, contributors with patches in Libav have voice in the channels.
#libav is for user support and general questions similar to the libav-api and libav-tools and mailing lists.
#libav-devel is strictly dedicated to Libav development. This means development of Libav itself. Development of other software that uses the Libav libraries is offtopic there.