[MPlayer-users] P L E A S E ! ! !

[Ivan Kalvachev]

This is reply to arpi's P L E A S E ! ! !

  It is normal begginer users to come here and ask one and same questions.
  How a regular user installs new program:
     1. Go to the web site. Go to download page. Find the main
package and download it
     2. gunzip,untar
     3. read the README and INSTALL files in the main direcory.
The begginers usually skip this step.
Some people make ./configure --help
     4.configure, make , make install
     5. mplayer test.avi
     6. if mplayer doesn't start -> man mplayer
     7. if mplayer doesn't work they look for help
     8. if they can't find help they take a vacation and start
reading the manual. If they find it of cource. Becouse currently
html dicumentation is not installed with mplayer.

You see that reading manual is the last step. What could be done:
1. Write (short) README and INSTALL files. Add things like from
where to download additional packages (divx4linux,ffmpeg, faad,
mad etc...). README with text like : "Read 'War And Peace' before
installing mplayer" is not the right one.
2. It is mythe that user don't help users. Go to www.divx.com or
some of the other over-crowded project. User really help users.
3. Propoce official user irc channel. There is one in
irc.openprojects.net #mplayer. Irc is the fastest way to ask
right questions, and help compleate newbie users. A lot of
people just stay in their favorite program channel and could
answer questions like 'how to add subtitles?', 'can mplayer do that'.
3. Make a forum. It is easyer to browse in forum.
4. All repeating question from the forum should go in the FAQ.
5. FAQ, forum ,channel and Documentation should be visible at
first look in the web homepage.
6. newbie-user could be made if forum is not enough.
7. At least one skin should be included in the realese.
8. It is not bad to include a short video clip to test does mplayer work
at all.9. A lot of users say that mplayer is slow. By default mplayer uses
11. Maybe configure could be used to chose best (xv,sdl) driver.
Or simple script that ask for option and write them in the ~/.mplayer/config
10. Automated Bugreport. Something like ./mkbugreport test.avi

On developer side:
1. There must have some way to track the bugs. Some bugs are
daleied and then forgoten.

Finaly. If mplayer projects need more documentation writes
then add an advertisement in the mphq homepage. Resently I sow a
xmms developer looking for apartment:O

Best Regards
  Ivan Kalvachev

p.s. not all ideas here are mine, the original autors could send patches
with their names;)