Sakai

Very quiet in the office this week... Almost all the developers, and a good chunk of everybody else, are away at the 7th Sakai Conference in the Netherlands.

From the conference homepage, I found a nice use of Sakai Confluence, to help conference attendees do travel planning and find out where to spend their free time (when they're not attending BOF sessions :-) )

 

I've been following the debate on the Sakai Pedagogy list, about personas and their shortcomings.

For the benefit of those unfamiliar with this term, 'personas' are generic user profiles, similar in many respects to the consumer profiles used by marketing organisations. They are employed as a tool for systems analysis, the aim being to design and build more usable systems, by understanding the needs and intentions of the people who will use them. The process of creating a set of personas normally involves an iterative process of research / evaluation, whereby individuals' unique 'needs and intentions' are grouped into normative sets.

The problem is, they don't work. Their chief benefit is also their greatest shortcoming: personas are inherently generic. They are not tools for personalisation.

The other issue is that personas encourage systems analysts / software designers to build systems around institutional roles, instead of activities. Why!? Organisations change. Organisational and institutional roles have a tendency to mutate, shift, and/or vanish, and people may change roles within an institution - once, or several times. Changing a customised system once it's built is expensive and time-consuming.

To update my post on the Blackboard patent, here is some more detail on the requested reexamination of the patent claim and the Sakai Foundation's response.

As Paul Erickson notes (thanks, Paul!), the news initially started bubbling up when the Software Freedom Law Center (SFLC) announced that it has formally asked the Patent Office to reexamine and ultimately cancel all 44 claims of Blackboard's patent on e-learning systems.

The request has demonstrated the very real sense of unity and common purpose among the educational open source software community. It was filed on behalf of the Sakai Foundation (sakaiproject.org), the Moodle Community (moodle.org), and the ATutor Community (atutor.ca).

In their press release, the Sakai Foundation refers to the "the surrounding fear, uncertainty and doubt (FUD) being spread by Blackboard", and states: "We, the Sakai Foundation, consider the Blackboard patent to be a prime example of a bad patent in the area of educational software.  It is a threat to open source developers, providers and users of educational software."

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.