[FFmpeg-devel] [PATCH] Add paragraph to website about posting attitude on project mailing lists
donmoir at comcast.net
Tue Aug 20 22:32:35 CEST 2013
----- Original Message -----
From: "Paul B Mahol" <onemda at gmail.com>
To: "FFmpeg development discussions and patches" <ffmpeg-devel at ffmpeg.org>
Sent: Tuesday, August 20, 2013 12:54 PM
Subject: Re: [FFmpeg-devel] [PATCH] Add paragraph to website about posting attitude on project mailing lists
> On 8/13/13, Robert Krueger <krueger at lesspain.de> wrote:
>> On Mon, Aug 12, 2013 at 10:00 PM, Lou Logan <lou at lrcd.com> wrote:
>>> On Sun, 11 Aug 2013 18:27:50 +0200, Robert Krueger wrote:
>>>> On Sun, Aug 11, 2013 at 6:22 PM, Lou Logan <lou at lrcd.com> wrote:
>>>> > On Sat, Aug 10, 2013, at 11:43 PM, Robert Krueger wrote:
>>>> >> That sounds like a good idea. As I wrote, the main reason for posting
>>>> >> this was to have something to link to [...]
>>>> > I'll make the wiki page within a few days and then provide a link for
>>>> > you to contribute to. Thanks.
>>>> Thank you.
>> I modified the original text and the suggestion would be to add this
>> to the page as the last paragraph. I hope it does not still sound
>> <h2 id="Generalremarks">Some general remarks</h2>
>> When posting on one of the lists, we would kindly ask you to consider
>> the following before complaining about things that are not the way the
>> should be (documentation, features, bugs).
>> FFmpeg is developed and maintained by volunteers, predominantly in
>> their spare time for no pay. You get something for free that could
>> very well be the most comprehensive and powerful set of media library
>> libraries and command line tools on the planet, while commercial
>> alternatives typically cost thousands of dollars. Pointing out
>> problems or suggesting improvements is very important and helps the
>> project, if done properly (see <a href="bugreports.html">Bug
>> Reports</a>). Simply complaining does not. There is no guarantee
>> someone will fix the problems you reported, because it is nobody's job
>> to do it, not because they are not important or there is something
>> wrong with your bug report. There may be cases where your only option
>> is to either submit a patch (for instructions see <a
>> href="http://ffmpeg.org/contact.html">ffmpeg.org/contact.html</a>) or
>> pay/sponsor someone who does it for you (see <a
>> We are looking forward to your participation on the mailing lists.
> It looks fine IMHO, add/edit/modify text on wiki is open to anyone.
Just a note that on some rare occasions it is not possible to reproduce the problem with ffmpeg command line tools but I am sure you
want the problem reported. The one main case that comes to mine is when multi-threading multiple videos at the same time. This only
happened once but spent much time trying to report it. It got fixed and then ticket was marked as invalid. Not everything falls into
a neat template as you know.
More information about the ffmpeg-devel