Notes on Sakai Project Coordination
-----------------------------------

Upgrades

	Java 1.5 - 1.6
		- JVM changes
		- Language changes
		- Builds under Java 1.6 for Sakai 1.5 (goal)
		- Experience 1.5 for production

	Maven 1.0 to 2.0
		Ray:  I don't understand the advantages for using 2.0.
		Glenn:  we could go to Ant.
		Chuck:  Inheritance of dependencies is one big feature
		Lance:  Ian has put a lot of work into this.  Let's decide it.
		Ian:  there are problems with the way 1.0 builds.  There are bugs that we just haven't hit yet.  Maven 2.0
		highlights these problems and fixes them (in some cases).
	
	DBCP (Database Connection Pooling)
		Just update it.
	
	Xerces/XML Parsing, etc.
		This has been replaced.
		javax.xml.*
	
	Spring
		Ray:  I've doing a bunch of work already.
		Comp Mgr moved over easily.
		Glenn:  we should move it out of shared.
		General support for doing it.
	
	Hibernate
		Lance:  mostly bug fixes.
		Discussion around tracking small point releases vs. waiting.
		3.1.2 to 3.2.1 (under consideration)
	
	Tomcat 6
		Runs on Java 1.5
		Updates to JSP
		Pluto would like 2.5
		Ian will do a general test.
		Glenn:  we could afford to wait on this.  It will get more mature.
	
Communications and Governance
	Broad Concerns
		In the interest of the community to encourage consensus and collaboration
		Some group of elective representation of technical people to promote that consensus and collab
		Purpose should not be to make arbitrary decisions, but with consensus instead.
		Some polling may be necessary, voting should be used sparingly in favor of consensus.
		When is it appropriate to make decisions?
		
		Lance spoke about the value of project groups.  Decoupling the tools from the product release cycle.
		Build consensus within the tool groups.
		
		Steven McQuard - Sakai is not agile.  We need to separate out framework and tools.  Different parts get different
		attention at different times.
		
		Ian Boston - a mechanism to allow someone to do a branch of a piece of Sakai.  Short term.  When done, then you put this
		branch out to the team or community and get consensus to merge it into the mainline.
	

	
Architecture
	Authorization
	
	JUnit / Entity Borker / Sites and their data / Tool and Service Status


Working Groups / BoFs

	Group to make a proposal on technical governance. Lance will Chair