Nate Angellraised by wolves, accidental open-source evangelist

I've been wondering how Sakai fares among professional schools in the USA, so as a first experiment, I grabbed the top 25 business schools in 2009 as per US News & World Report and did some research.

Given how business schools have the reputation of hewing to proprietary systems and going their own way, I was surprised by Sakai's strong showing. 3 of the the top 10 business schools use Sakai as their primary online learning system. At least 6 out of the top 25 schools either already use Sakai as their primary system or soon will. I also know that at least 9 other schools in this list are either actively investigating Sakai or have some impetus to adopt Sakai.

I'm still collecting information from a couple of campuses and I welcome your comments. If you know the priamry online learning system for any of the schools not accounted for yet here, leave a comment below or contact me and I'll update the list.

The Sakai Foundation is a member-based, non-profit 501(c)(3) corporation engaged in the collaborative design, development and distribution of open-source software for education, research and related scholarly activities. It encourages community-building between academic institutions, non-profits and commercial organizations and provides its members and others with an institutional framework within which Sakai projects can flourish. The Foundation also works to promote the wider adoption of community-source and open standards approaches to software solutions within higher education.

I've recently been enjoying some (possibly) healthy, irreverent debate with colleagues at Blackboard and beyond about some of the differences between such proprietary regimes and the open-source community of Sakai. While the Twitter channel we've been using generates plenty of pithy ripostes, at times a tweet calls out for more sustained thought and response.

A recent tweet from @georgekroner—one of my favorite Blackboarders—set me thinking and led to some longer—if not deeper—reflections, likely to be far less entertaining than the short salvos in our ongoing snarkument on Twitter.

The tweet that set me off was George sharing his concern that Sakai 3's planned capabilities might be "commonplace" by the time it is ready for widespread use.

I'm not entirely convinced George's concern is for real, given that Sakai is one of the most significant challenges to Blackboard's market dominance in learning technologies and it would seem any failure on Sakai's part would be cause for celebration rather concern over at Blackboard. But maybe George is just the kind of guy who wishes the best for everyone. Or maybe it's part of Blackboard's continued posture that having a near monopoly in the proprietary market is fine as long as there is at least one viable open-source alternative like Sakai, even while Blackboard itself acts like open source can't really compete.

But I'm not inspired here just to wipe away Blackboard's crocodile tears. George's tweet started me thinking: if he is right, and the kind of experience Sakai 3 will offer becomes commonplace, we should all celebrate rather than wring our hands.

If Sakai 3 ends up fitting within the broader scope of contemporary online experience, that means Sakai 3's open, social, user-centered, integrative paradigm shares in broader understandings of what online experience should be—both within education and beyond. It wouldn't just mean Sakai 3 "guessed right," it would also mean a very healthy, widespread vision of what the web can and should be has won out. Far from a concern, I would count Sakai 3's capabilities becoming "commonplace" as a major success, not only for Sakai, but for the web in general.

Josh Baron, Director of Academic Technology and eLearning at Marist College and now the new Sakai Foundation Board Chair, recently posted a great article in Campus Technology detailing Marist's nuanced evaluation of Sakai and its community source provenance: Community Source Evaluation Strategies: Is Sakai Right for Your Institution? The article is a must-read for anyone at an institution considering the adoption of a learning environment—open/community source or proprietary—as all of Josh's lessons pertain to both options.

I'm especially glad to see Josh include "Functionality Requirements" as only one of Marist's five important evaluation criteria categories, putting it alongside Support Requirements, Community Health, Reliability/Scalability, and Innovation Drivers. All too often I've see institutions focus primarily on functional requirements in their technology choices, often at the expense of wise, strategic decisions that Marist's other categories take into account. Every system will leave you with functional gaps...it's the other stuff that will matter most in the end.

Reading through Josh's piece, I was also struck by how the structures of commercial support for open/community source underlie each of Marist's evaluation categories, and how well Sakai's robust commercial ecosystem helps buttress Marist's case for choosing Sakai. I'll briefly cover each category below.