Dependencies

• python (http://www.python.org)
• python-xml
• python-mutagen
• oggenc (http://www.vorbis.com/)psycopg2
• sox (http://sox.sourceforge.net/)
• flac (http://flac.sourceforge.net/)
• lame (http://lame.sourceforge.net/)
• ecasound (http://eca.cx/ecasound/)
• wavbreaker (http://huli.org/wavbreaker/)
• festival (http://www.cstr.ed.ac.uk/projects/festival/)
• par2

For future development

1. Web interface
   • webpy : a pure python http framework
     • homepage : http://webpy.org/
     • community : http://webpy.infogami.com
   • pyweb : another Python Active HTML Framework
     • homepage : http://www.freenet.org.nz/python/pyweb/docs/index.html
   • WSGI : Python Web Server Gateway Interface
     • specifications : http://www.python.org/dev/peps/pep-0333/
     • a very good article from Guido van Rossum : http://www.artima.com/weblogs/viewpost.jsp?thread=146503
   • Django : A high-level Python Web framework
     • homepage : http://www.djangoproject.com/
     • DjangoStuff? : https://simon.bofh.ms/cgi-bin/trac-django-projects.cgi/wiki/DjangoStuff

2. DB interface
   • python-mysqldb : Python module for MySQL
   • python-psycopg2 : Python module for PostgreSQL
   • python-forgetsql : Python module for easy SQL-database access

3. Documentation
   • Dive into Python : http://diveintopython.org/toc/index.html
   • Description of the internal Trac Component Architecture (and original proposal) designed and written by Christopher Lenz. We could get inspiration from it, in order to make Telemeta component-based, so it can cleanly be extended with new features (you might call this plugins). We could even reuse much code...
   • Interesting paragraph about modeling Dos and Don'ts in this UML Class Diagram tutorial
   • PEP 8 (Style Guide for Python Code) : following these coding standards will bring consistency to Telemeta
   • PEP 257 (Docstring Conventions) : to properly use docstrings