The developers and everyone having the will to test the encoder will have the opportunity to share their results using standard web forms. The features will include:1. availability of standard samples which are known to cause problems as losslessly compressed files with a brief description of the problem2. for each sample, there will be seperate test result sets for each version of the encoder3. under each sample and encoder version there will be a forum-like "thread" where anyone could post their test results. Discussions will not be allowed and the users will be asked to discuss the results on dedicated forums and mailing lists. (NOTE: I could add the possibility to rate the sample in 0-5 scale and/or a poll with fixed answers instead of writing a comment in the thread)4. for anyone who tested the encoder on a custom sample, a seperate page for upload and results. (NOTE: or only a possibility to send a link to the custom sample, instead of uploading it, in order to avoid getting copyrighted files)5. the uploaded samples which turn out to address a yet unaddressed issue of the encoder will eventually be moved to the standard-samples area by the admins.(thanks to Alexander for the suggestions)It's a very simple scheme. Any suggestions are welcome. Once it's complete, the main advantage of it will be that empty sample/encoder-version fields will indicate that they haven't been tested yet. It will be clear what is yet to be done. It will also be clear in which version a certain increase or decrease in quality occured. Results of the tests which have already been done may be easily moved to the database by myself with some help from the testers.Please let me know what do you think of the idea. Do you find the framework useful?
"development is too erratic to ever expect any one thing at a given time"(but isn't it the difference between a full-time job and a project your only working on free time?)
Ouch. You sound like you're being awfully harsh on the LAME developers (other than takehiro)
I think the bug submission is a good idea, it would help provide a communal area for all the developers, add to it a wiki for the developers to communicate easily with eachother and it could work. Each of them just needs a line, I'm working on : __ __ __ __ __ __
That way, Gabriel could be working on the preliminary work, testing and whatnot, then his results get put on the wiki for other people, helping them to know what can be done and where it could go. And with users posting the initial problems that drive the prelim work, it could all work smoothly.
I've had similar problems. 5 people working independantly on some code, although it ended up with nothing getting done. I tried having a wiki for communication, and it seems it could work. It's simpler, but slower having just 1 person working on everything, which is my case now. People can go on my forums though, posting bugs and suggestions, those go to me and the ideas people, then to the coder. That works quite well tbh
So who is going to manage that?
What would you see as HA's role in this?
QuoteSo who is going to manage that?Why not Dibrom ?