Here we just list a couple of additional ideas which can make your life easier when configuring your particular Kosmos portal instance:
Combining Kosmos portlets with other portlets is a good practice to maximize the information effectively aggregated on your portal page.
Other than the standard Kosmos portlets, you should consider using: Forums portlet, RSS portlet, Blog portlet, Poll portlet, CMS portlet and Wiki portlet. All these (provided you use them in the right way) should improve the communication both inside your community and with the external world.
If CruiseControl runs on a remote machine (not the same machine like the container which hosts Kosmos container), you can map the remote CruiseControl log directory to the local filesystem and monitor it.
All portlets support multiple monitored resources, group those as you wish.
For example, you can have a separate portlet for monitoring Spring, and another for monitoring ACEGI, but it might make sense to group those as related packages together to a single portlet, plus keep all the Struts-related packages in another portlet and Tomcat-related packages in a third one.