<ul>
<li>Go through the mailing list archives:  Read each thread, note its 
topic, and list the main points brought up, and any conclusions that were 
arrived at. (yeah, I know this is a big project, but anyone agree it should be done?)
<ul>
<li>tunes
<li>tunes-lll [almost done -tcn]
</ul>
<li>Read IRC logs and summarize decisions and important unresolved issues
<ul>
<li>Read all these papers and summarize their application to 
the tunes project:
<li>http://www-ppg.dcs.st-and.ac.uk/Publications/
<li>http://www.math.tau.ac.il/~laden/COP/
</ul>
<li>Prototyping & experimentation: Try putting Tunes ideas into practice. Don't worry about perfecting it the first time, it'll be rewritten plenty of times. [core, tcn]
<li>Automated subproject web interface (tril is working on this)
<li>Fix the front page: Interesting, informing, inviting, functional
<li>New FAQ (Draft: http://bespin.cx/~bineng/faq.html) [tcn]
<li>Rewrite the brief introduction from the Root subproject page (http://www2.tunes.org/tunes.html), which is not so brief, use tone for new users
<li>Changes to the page will be verified by retroactive moderation of CVS updates.
<li>Look at http://members.xoom.com/unios/tunessite.html for up-to-date information on the new site. [Newer: http://www2.tunes.org/~bineng/]
<li>Write a script to pipe LaTeX documents 8k at a time into BabelFish to convert documents Fare wrote quickly
</ul>

