Jeff, RequestedDeletion and all,
The How-to Classification is only the start point for Documentation (= weblinks, manuals, how-tos). I will split the Central Repository problem in two for better understanding:
- Central Repository for Documentation => The How-to Classification is the start point and you are right about “the manpower and effort it takes to test, classify and write up all of the info”. I will study the structure and see what I can do to help.
- Central Repository for Contribs and Updates => The main topic of this post.
About the last one I like pretty much the Drupal solution (see link above). We could do something like that:
- A http front-end organized by SME Server version (6.5, 6.0.x, 5.6) for better user navigation and descriptions of each contrib/module.
- In terms of file hierarchy it could be something like:
/smeserver-5.6
/smeserver-6.x
/smeserver-6.x/core
/smeserver-6.x/core/developer
/smeserver-6.x/core/fedoralegacy
/smeserver-6.x/core/incoming
/smeserver-6.x/core/iso
/smeserver-6.x/core/updates
/smeserver-6.x/core/rpms_current
/smeserver-6.x/core/rpms_old
/smeserver-6.x/core/sources_current
/smeserver-6.x/core/sources_old
/smeserver-6.x/contribs-tested
/smeserver-6.x/contribs-tested/backupcc
/smeserver-6.x/contribs-tested/backupcc/1.0.0
/smeserver-6.x/contribs-tested/backupcc/1.1.0
/smeserver-6.x/contribs-tested/clamav
/smeserver-6.x/contribs-tested/spamassassin
/smeserver-6.x/contribs-tested/nameofcontrib
/smeserver-6.x/contribs-untested
/smeserver-6.x/contribs-untested/nameofcontrib
/smeserver-6.5
/smeserver-7.0
What are your opinions?
-Nuno