CMS systems:

http://www.cmsmatrix.org/
http://www.steptwo.com.au/papers/kmc_evaluate/index.html

Mambo - PHP & MySQL

Pros

• product is focused on content
• easy to set up and use

Cons

• poor user profile and permissions management: difficult to give out user-roles and permissions to different parts of the site
• no wiki feature?
• Lacking comment system
• Uses a lot of resources on the server when scaling to a larger site 

Drupal - PHP & MySql / Postgres

http://drupal.org/handbook/is-drupal-right-for-you
http://drupal.org/handbook/drupal/gallery

Pros

• multi-site features - can set up several sites with one installation
• friendly URLs - easier to bookmark and search engine friendly
• powerful templating system
• product is focused on communities
• dashboard / portal page for users can be added with a free add-on
• wiki functionality can be added with a free add-on
• scalable

Cons

• possibly a steep initial learning curve to get used to the system
• no easy WYSIWYG text editing features like in Confluence (might be able to be added as a module)

COMMENTS:

 "I love using Drupal! The community is huge and there are so many pluggin modules to use. I have Two installs running a total of 10 sites. The multi-site func is a real winner. The learning curve is a little step at first, but only because Drupal is such a powerful CMS. Once setup the site is easy to adjust. Knowing how to do it I can now set up a new install in about 15 minutes."
http://www.opensourcecms.com/index.php?option=content&task=view&id=132&Itemid=159&show=1&start=4 

sounds like it is possible to do the multi-sites!

TYPO3 - PHP & MySQL / Postgres

http://typo3.com/Feature_list.1243.0.html

Pros

• very flexible system
• complete with WYSIWYG text editing features

Cons

• steep learning curve

Wiki systems:

http://www.wikimatrix.org/

Confluence

http://www.wikimatrix.org/screenshots/screen_16_3.gif

Pros

• easy to use
• ability to attach files to a wiki entry
• versioning history control - both content pages and attachments
• different users can edit a single entry àversion history
• commenting system on each wiki entry
• spaces - can use spaces to organize projects

Cons

• limited user management system - no tiered role user system
• site design not so flexible ?
• community aspect: events management

MediaWiki

Pros

Cons

• no real user profiles

TikiWiki

Perl based

Pros

Cons

MoinMoin

Python based

http://moinmoin.wikiwikiweb.de/

Trac

Project management software

http://trac.edgewall.org/

Google Mini

Currently some segp's have or are developing their own 'database' of projects. Many of these databases are already accessible via a webpage. It would be useful if their was a centralized index of these webpages that could be searched. A 'Google Mini' or similar search application could be leveraged to aggregate multiple websites and create a central data store of pages.

Pros

• Allows for decentralized publication of projects and reduces data duplication
• Does not place any restrictions on how project data is published

Cons

• Data is unstructured

RSS Aggregator

Many products like "Drupal" or "Wordpress" offer the ability to export RSS feeds. It would be interesting if there was a "Google News" like site that would pull together various RSS feeds being produced by various segp's.

Pros

• Allows for easy aggregation of structured data

Cons

• Requires more complex software for project presentation
• Limited to RSS data fields

Homegrown

If a standard "Project Schema" could be defined (i.e. title, description, url, status, publish_date, last_update). Each segp could be responsible for creating their own database that could be exported via a standard format (comma separated file, XML, etc...). This would offer benefits similar to an RSS aggregator and offer very structured data fields specific to a project.

Pros

• Get precision of data entered

Cons

• Requires completely custom coding