Forum .LRN Q&A: Re: Report: An Evaluation of Open Source CMS Stressing Adaptation Issues.

Let's try giving each package it's own wiki project page, and have a summary table that gets automatically updated for the most part. Here's an example of what it could include.

https://openacs.org/storage/view/proposals/packages-report.html

Maybe move the manually editable columns of that table into the package wiki page for convenience.

Each package's wiki page would act as a project page, having the usual information:

description, news/status, notes, strengths, weaknesses, plans, project participants, links to package info in other places, such as cvs browser, package docs, forum threads, demo(s) etc.

side note: It seems to me that at some point the maturity tag was an index of deployment (x number of known deployments). Yet, now it seems to summarize some of the data points, suggesting that those manual data points should definitely move to the package wiki pages.