Team Meeting March 9, 2011

TODO list

• clean up TODOs in code.
• choose which ones we want to fix for release
• use the Wiki feature on github to create a dev wiki where we can organize todo lists and release junk
• anderson will migrate over stuff from the mons wiki.

Issue tracking on github

• yes let's use this but only for bugs and as a way for other folks to report bugs and request changes?

manual organization/rewrite

• would be nice to have a better web version that is easy to update and can also be easily exported to PDF for inclusion with the release.
• more discussion is probably in order to talk about what form the cleanup and rewrite needs to take.

examples

• move minim-examples into the Minim repo itself in a directory called examples. this lets the repo double as both an eclipse project and a minim library folder

build/release process

• pull build.xml and have a look at it. possibly modify to put the jar files where we want them.
• anderson can write a script to build the release zip file from the things we want to include in the repo (ie, not .classpath, .project, bin directory, etc.)

forum/wiki for minim

• use the Processing forum
• possibly use doci-wiki for the manual and faq

timeline

• e-mail ben to find out about what they are shooting for as a 2.0 release. plan to hit that date for minim release.