The TMC proposal was drafted during the December 2007 Newport Beach Project Planning Meeting and later debated during the course of a series of follow up technical BOF sessions during the Sakai Newport Beach Conference. The proposal was laid aside during these discussions in favor of a less centralized approach to Sakai technical leadership. See the draft Sakai Developer Practices document for more details. A. Whyte.


The team will be known as the Sakai Technical Management Committee (TMC).


The TMC will oversee the technical evolution of Sakai software, providing leadership, guidance, processes and priorities for the Sakai developer community.


The TMC will be composed of up to seven (7) members, nominated and elected by members of the Sakai Community who are members of the Sakai Developer Discussion Group. Candidates for the TMC will each secure and state publicly the amount of time they can commit to TMC activities. The expected time commitment of individual TMC members is one calendar year and will represent between 10 to 40 hour a week time commitment.

Elections will occur by the end of January 2008.


Internal TMC governance will be determined by the members of the TMC. TMC processes and priorities will reflect the values of the Sakai Community.

General Priorities

The TMC will work to improve the reliability, maintainability, performance and utility of Sakai software.

As a first milestone the TMC will review the set of technical goals outlined in the Sakai Technical Goals (towards a roadmap) document and derive a set of related tasks to work on in support of those goals.

Possible Tasks

In discussions to date, there seems full agreement that a short-term goal will be creation and maintenance of automated regression and load tests. Without tests in place to ensure stability, other changes may be too risky to pursure.

Other goals targeted over the year are likely to include:

Reliable and supports High Availability

Reduce support costs

Easy to install and get up and running in a day

Able to handle many users per app server (with relatively modern specs)

Easy to develop new tools and apps to run in Sakai

URLs that make sense to users (also called "clean" URLs)