In the interests of getting everyone on the same page.... as I will, with Chris's blessing, attempt to bring order from (minor) chaos. For the sake of clarity and forward progress: In the wiki... (which is truly one of the best collab. doc. tools I've seen): So at least I know where to look Major features and notes about how to implement them live on the http://www.saas.nsw.edu.au/wiki/index.php?page=KohaFeatureRequests page. Who is actually writing a feature them lives in the RoadMap (http://www.saas.nsw.edu.au/wiki/index.php?page=KohaRoadmap). Also -- As you write it, please document what you are doing in the code, as well. Which version a new feature appears in goes into the RoadMap. When a bug is fixed, a note about it goes into the Roadmap. Try to keep a running note in the roadmap as to where you are with stuff -- nothing complex, on the order of "need to fix a few more things, then I'm done". When a version is released (ie, ceases to be listed as DEVEL), that versions chunk of the Roadmap becomes the Changelog. Things needed answers (from Chris, in particular) should probably go in the ToDo list. I'd suggest you put recent questions on top. You might also email them to Chris with a header like 'Koha Need Answer' in the subject line at the same time. If you have a brilliant feature idea... put it in FeatureRequest and I [Nick] will try to be sure that that it moves into the RoadMap list in some sort of semilogical fashion -- we're all trying to get too many things in at once. 'Nick Place This' in the subj. line of an email to me (nrosasco@acm.org) might be a good idea to make sure I see it. I suggest we all try to hold to this way of tracking things so that we don't step on each other, and to use CVS as much as logically possible so everyone can see where the code is. If you have a "personal version" of Koha please either upload with a label as to what it is, or (maybe better) send it to Chris and have him look at it -- I count 2 to 4 derivative or personal versions out there. Nick