These are my raw notes for my Vancouver talk. Not everything made it in. This has no meaning - just wanted to put this in before I cleaned up my desktop.
Deploy one release back - Pilots or strong sites can stick with the release
Should we move from June December to April/October?
Performance tuning - instead of expansion.
The rule for 2.2 release is that code must compile run reliably on both 1.4 and 1.5 - we encourage sites to use 1.5 for Sakai 2.2 for testing over the summer and then in use 1.5 production in the Fall. Sometime in the Fall (like October 1), based on production experience, we may open the gates on 1.5-only code - but when that happens there will be a dev list discussion about it.
iTunesU
Maintenance branches - need to form communities for 2.2 2.1 2.0
Java 1.5? For Sakai 2.3?
Groups in tools
Caching in a cluster - how it works how to do it
Genetic Diversity in QA - See the startup problem
Samigo
IMS TI
OSP Portal
Mini TI Rutgers
JSF, RSF and Presentation
Go through tomcat directory structure
Vision Going Forward
RDF Overview
What we have done
Promises from Baltimore
Promises from Austin
Sakai Mini
Null Portal
Forming OSP Community
Forming Samigo Community
No Magic Faries
Sakai IT Org Chart
User Interface
User Documentation
What are our challenges?
Sakai 2.2 Notes
OSP Code freeze wants to happen February 17. This could crimp our style quite a bit. Because OSP needs to take trunk at that time because it needs changes in Sakai that are not present in 2.1. The problem is that if we allow the Sakai trunk to move forward wildly towards a 2.2 release (as you see below) significant non-upwards compatible work needs to happen including things that are database changes.
For OSP to release its 2.1, we will have to develop conversion scripts for any of the Sakai elements which have changed and it will effectively *be* Sakai 2.2 - we will have to QA all of Sakai at some level because people will instlall *that* release, expecting Sakai parts to work.
Gradebook Improvements
Samigo Improvements
Provisional: MailTool
- Section Aware
Provisional: Lancaster Blog, Video, Audio, Whiteboard, screen share
Improve Accessibility
--Merging the title and content frames from Portal
--Identifying how we can make JSF widgets 508/Priority One and Two compliant
Web Services IP Filter borrowed from WSRP
Versioning for resources
Internal DR Search by building internal DR OSID
Unit Test Framework
Provisional: JSR-168 portlet - build portlet.war files as part of the Sakai build.
Finish up IMS Enterprise Provider
Provisional: Integrate Melete
Provisional: Integrate JFrorum
Provisional: Add the LAMS Integration tool to the Sakai Release
Provisional: IMS Tool Interoperability
JSR-168/WSRP CSS Alignment
SCORM - Figure things out
Rutgers Access Mods
User alias
Site alias (perhaps even add to Charon)
EntityType Registry
Resources Tool
- Refactor into helpers
- Make popup for
Make DuplicatableTool a general capability (see OSP)
Hierarchy
Framework / Portal / Site Info
Clean up section management and groups - try to come up with wholistic approach - at least try to see if helpers make sense.
Section aware tools
- Decide which
- Design
- Implement
WSYWIG Pluggable
Import/Export - Make work at minimum - perfer to switch to IMS Content Packaging
WSRP - Portal View in addition to tool view.
Provsional: WSRP Consumer from Daresbury
JAR Version Advance
- Hibernate 3
- Spring 1.2
- Others
Clever URLs for tools (use the tool ID not the GUID)
Integrate Lucene - Sakai Search