Towards the end of this thread started by Randy Ferrer there were questions about the obsoleteness of various packages. This reminded me that we need to examine the packages that we have for the upcoming OpenACS 5.0 release and I have therefore drafted a package inventory document.
You will note that the tables on the page are glaringly empty, and this is where I was hoping to be able to draw on the help of the community. Above all I am interested in knowing which packages people are interested in maintaining. Let me know if you need permission to edit the document (it is an Edit-This-Page). In addition to adding yourself as maintainer or clarifying what a package does, also feel free to make corrections, i.e. some package may be missing, or a package may be listed as service that is an application etc.
You might notice that I am referring to an OpenACS core team in the document eventhough formally no such team exists yet (informally one could argue it has existed all along). On the day after the Copenhagen OpenACS social there was a meeting to discuss OpenACS governance where Don Baccus and Jeff Davis presented three different examples of governance, those of the Apache, W3C, and Tcl/Tk projects. The recommendation was that what we need something similar to the Tcl/Tk core team and their process for managing patches and feature changes using maintainers and supervisors. I think OpenACS governance will probably be discussed in its own thread. I just wanted to mention it here and now as it is quite relevant to my package inventory list and the OpenACS 5 release.
For anybody who wants to be involved in shaping the governance rules for OpenACS I highly recommend reading TIP #0: Tcl Core Team Basic Rules. The document is written by John Ousterhout, it is quite terse and well thought through, and the OpenACS governance document will probably borrow many ideas, and also wordings, from it.