...
- Using Spring Web Flow 2 for Administrative UIs
- Portal and portlet health monitoring (is a specific portlet rendering correctly, is the portal rendering correctly, etc)
- Web Analytics: specifically usage data for the portal and individual portlets
- Portal & Portlet life-cycle management, including: versioning, deployment strategies, environments, registry information (e.g. functional and technical ownership, support information)
- Infrastructure architecture: such as high-availability configurations, application servers deployed (e.g. JBoss), middleware being used (e.g. ESB, SOA)
- Integration with Microsoft Exchange and SharePoint. Specifically interested in bringing a RIA (Rich Internet App) email portlet into the Portal
- Continuous Integration
- Load testing portlets, portal framework
- CAS 4 Roadmap & Vision
- CAS Future Protocol Analysis (create a new one, use or extend OpenId, etc.)
- General Identity Management
- IdM Registry - Rutgers Open Registry Initiative
- Fluid component integration
- CAS as an optional OpenID client (relying party)
- Collaborating on a shared code base for portal+SIS integration (maybe start with existing Banner portlet work).