When I speak to people from schools that are currently involved in an LMS selection process, I very often hear the following assumptions and line of reasoning:
- Sakai 2 hasn’t set the world on fire, and anyway, it’s going to be replaced by Sakai 3 soon.
- But Sakai 3 isn’t ready yet, and we aren’t sure exactly when it will be ready or how to go about evaluating it now.
- Since we have to make a decision soon, we are going to have to forget Sakai as a candidate.
This is a reasonable and understandable train of thought, but it is built upon mistaken beliefs about Sakai 2, Sakai 3, and the relationship between the two projects. The Sakai community has a vision and a plan that ensures both Sakai 2 and Sakai 3 will remain healthy and under active development for some time to come. In fact, far from being merely an awkwardly timed product transition, the two-product approach the community is taking actually provides what I believe is a unique strategy in the LMS space for supporting schools’ present needs, fulfilling their vision for their future, and providing a path from one to the other. Rather than being a reason to dismiss Sakai from consideration, the Sakai 2/Sakai 3 dichotomy is actually reason to look at the Sakai community and family of software especially closely.

