Sakai and CMS

Recent blog entries tagged with Sakai and CMS.

The quest for sustainability in open courseware

Created by Paul Trafford (University of Oxford) on July 15, 2007

I've been reflecting recently on the subject of open courseware and, more specifically, OpenCourseWare following the keynote for the Sakai conference in Amsterdam delivered confidently and enthusiastically by Hal Abelson (a podcast is available). In this post I'll briefly recap some of the core aspects as I understand them and then go on to explore this area, based on personal experiences and ideas I've been formulating at Oxford.

An Interview with Rob Abel

Created by Matt Pasiewicz (EDUCAUSE) on October 26, 2006
In this 26 minute recording, we'll hear from Rob Abel, CEO of the IMS Global Learning Consortium. Listen in as Marliu Goodyear hosts a discussion about standards, course packs and more.

Downes on Sakai

Created by Catherine Howell (University of Cambridge) on February 02, 2006
The Sakai Project is a major open-source development, which aims to produce a robust, scalable collaborative learning environment for higher education.

An article by Stephen Downes in the latest issue of Innovate! provides a good overview of the Sakai project website and helpfully steers newcomers towards the best content and resources.

This is one of those Really Useful articles that the open-source community needs to do more - a lot more - of. Downes is right: the Sakai site is confusing to navigate and, in many sections, is dominated by technical language. This can be highly off-putting to non-developer stakeholders who choose to visit.

And this is precisely where many open source projects fall down: in terms of communications and outreach towards those who are located "outside" the developer community. The problem is that an open-source project website is (normally) both the public and the private face of the community. The website has to serve a dual purpose, looking "outward" towards casual visitors and end users, and "inward" towards its own members. You can't solve this problem by shutting the developers' mud-wrestling, sorry, complex and interesting discussions, off into password-protected areas of the site; because that usually means that the information left  within the "visitor/user" sections of the site is far too thin to be useful.