Why limit the project, though? It shouldn't be that difficult to create an application that organizes and indexes ANYTHING, from books and CDs to flowers to pigs. In fact, if we simply create a databasing engine and a front end, we could create a standard module for any type of index.
For example, you take the base application and write a module for it that defines what the objects are, what the index key is, and other useful bits. It could be from something as simple as a text file to as complex as a program extension with added functionality. So we could create (to follow your example) a CD Library module that simply defines the key fields (Title, Artist, Track listings, Year, Label, Personal rating 1 - 10) or we could create a module that defines all that AND includes the functionality to populate the fields from CDDB. Someone else might code a module to define MP3s - and the extended functionality is to create playlists for XMMS or WinAmp. A book module with the extended functionality of searching $bookseller_of_choice for other works by the same author, or (later on) eBook versions of the title.
Who needs a CD or book manager when you can have both?
For site hosting, I'm sure server space could be found; I don't think Perl Monks should actually host it. I'd be in favor of posting the code to Perl Monks at every stage, though, and regular updates on how the project is working and organized in the much-debated Projects section.
In reply to RE: Community Teaching Project
by Ozymandias
in thread Community Teaching Project
by jcwren
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |