[MPlayer-dev-eng] re: FTP.mplayerhq.hu incoming/ dir administration

[James Courtier-Dutton]

compn wrote:
>>Hi,
> 
> 
> hello!
> 
> 
>>1. get a new, bigger disk (current one is 80GB, for ftp only,
>>  including samples archive and releases, and cvs snapshots)
>>
>>2. get someone to verify each file, and if it's shit, or already
>>  fixed (and not interesting enough to save at samples archive)
>>  then delete it. do it once a week or so again.
> 
> 
> i vote for this one, if it plays, delete it. (with no .txt anyways)
> should not be too hard for a couple people on fast connects to do.
> just gotta find volunteers, dev's need time to work on bugs, not sort
> files.
> 
> set up a simple interface (or bugzilla?) for each file, have min 3 people
> try playing it, then comment on each file's bugzilla/report
> audio/video works/fails , color probs, crash, etc
> 
> 
>>3. say a strict policy: if no .txt file (same basename) with
>>  description, the file will be deleted.
>>  it would mean deleting 80% of total data from incoming.
> 
> 
> how about a backup of all samples? on dvdr or cd? then remove
> working ones from mphq?
> 
> 
>>i vote for 3.
>>2. would be the best and 1. is the easiest.
> 
> 
> bigger disk = more shit to sort thru ;p
> 
> 
>>A'rpi / MPlayer, Astral & ESP-team
>>MPlayer's new image: happiness & peace & cosmetics & vmiklos
> 
> 
> -compn
> 

In case you have not noticed, there are other projects that use the 
samples archive on your site. e.g. xine.
It would be a shame to have to duplicate the entire archive, just so 
that a few needed samples don't get deleted.

Also, just because a sample plays now, does not mean it will always 
play. Some change to the mplayer code to fix one sample might break 
another sample, so it is a good idea to keep all samples you can, and 
use them to do tests before each release.