That sounds to me too like it'd be a good project. The biggest problem would be find a good way to wade through the mess. I have a lot of perl code laying around too, but not all of it is "production quality". I think it's great that you have 80% of what someone's looking for, but will it take them more time to learn your existing code and finish it than it would for them to start from scratch?

I think the code would have to be organized very well, and put into well-defined titles. There's a lot of potential for forking code when you look at smaller programs. Deciding between a script that queries CDDB for mp3s named Artist_Album_Song.mp3 versus a script that looks for Album_Artist_Song.mp3 would be a nightmare. It might be better to focus on larger projects than those that are more on the side of under 1000 line throwaway scripts.

Also, there are hundreds of sites out there where you can download one of thousands of CGI scripts. It's really hard to find good stuff there, and something that fits your needs. This couldn't be one of those sites. Again, maybe it would have to focus more on consolidating duplicate efforts so that there's less noise, and less bad code.

But yeah, if we can solve some of the implementation problems, it's definitely something I'd be interested in.