[MPlayer-advusers] [POLICY] reviewing incoming

compn tempn at twmi.rr.com
Sun Nov 19 07:08:46 CET 2006


thought i'd try to start a howto or policy for reviewing /incoming
maybe put it in docs/tech if we can agree on it.

how exactly do you want the report to be formatted?
what kind of info do you want in the report?
something like:

filename
problem/status
what to do
test results

what are the requirements for moving a file from incoming to samples?
new codecs obviously, but what about existing codecs?
different framerates? diff samplerates? diff containers?

for files without txt descriptions, test only playback?
search on the mailing list and/or google for description?

for sending the reports, i was thinking of grouping similar files.
e.g. send all libavcodec bugs in one email, and all mplayer demuxer
bugs in another email. what list do you want the reports to go to?
-advusers for all? dev-eng for mplayer and ffmpeg-devel for ffmpeg?

below are some incoming reports using the above format.
if anyone has reccomendations, please speak up.

/incoming
At_the_End_high.mov
incomplete upload
delete
tested url in txt , worksforme

toto
empty dir
delete


/incoming/old-incoming
mrkiko.ogg
pebcak
delete
worksforme, txt file -v output says his config was forcing -ac +libmad for all files

garelka.au
support added by dev
delete or move to samples?
worksforme

-compn



More information about the MPlayer-advusers mailing list