[FFmpeg-user] ffmpeg user list rules

[Lou]

On Thu, Feb 16, 2012 at 08:18:17AM +0100, Boštjan Strojan wrote:
> On Wed, Feb 15, 2012 at 1:00 AM, Lou <lou at lrcd.com> wrote:
> > Additions? Questions? Comments?
> 
> Thanks,
> 
> an overview/questions/additions:
> 
> ------------------------------------------------
> 
> ffmpeg-user mailing list specific rules:
> * Avoid top-posting. Interleaved replying is standard etiquette.
> an example of what you should NOT do
> http://en.wikipedia.org/wiki/Posting_style#Top-posting
> 
> * Do not hijack threads (replying to a thread and changing the subject
>  line to something completely unrelated that was not being discussed
>  within the original thread).
> 
> * Configure your mail client to break lines after 70-80 characters.
> (why exactly?)

Unbroken lines are hard to read if they keep going and horizontal
scrolling is annoying.

> p.s. it appears that gmail should break at 78 char.
>
> How to provide the right information:
> * Use recent ffmpeg from Git or a supported version of ffmpeg (see
>  download page) if possible.
> 
> * Show your ffmpeg command and the complete, uncut console output
>  of your command.
> 
> * If you attach files avoid compressing small files; uncompressed is
>  preferred. (that's probably for patches/text files?)

Yes. Perhaps config.log if it isn't obese, or console output attached
as text file for some reason, etc.
 
> * Use minimal commands to help narrow down what is causing the issue.
>  Exclude filters and external encoders (usually anything lib*, such as
>  libx264) if possible. (So there is no support for external encoders
> such as x264, vp8?)

External encoders are supported, but it's often easier to narrow down
the problem if you can exclude an external encoder as a cause.
 
> * Provide a link to samples if applicable (see datafilehost.com or
>  mediafire.com if you need a file service).
> 
> * Avoid posting command lines that use shell variables. We need
>  commands that allow anyone to easily duplicate your issue.
> 
> * I was told off for using HTML format (on by default in gmail) - is
> that a rule?

Normal, text-only messages are preferred of course, but I would call
this a preference more than a rule, personally; especially in this world
of "value-added" mail clients (including webmail) that default to ugly,
stupid HTML email and other general sillyness.

Providing adequate information is more important in my opinion. I want
users to be comfortable asking (detailed) questions rather than be
intimidated by too many rules.

How about this:

* Plain text messages are preferred. Please disable HTML email if you
  can.

> * Deleting attributions is a tad impolite as well; I have to go upthread
> to find out who you were quoting.
> 
> 
> ------------------------------------------------
> 
> somebody should put that out of engrish and drop to some ffmpeg related web,
> link could then be in the footer of all messages of this list?

Yes, that is my plan. I want to get input and suggestions from actual users
first, and then I'll make a patch for http://ffmpeg.org/contact.html

As for the footer, I think adding more to it will make it too verbose.

> Examples would help as well, for example i had to google to
> understand/remember what is "top posting".

I'll add a link to explain top-posting. I intended to do that, but it
wasn't easy to show in my list. If only we used HTML email...also all of
this could be in purple Comic Sans.