A good general overview presentation for Sakai. The last presentation I have as Sakai Executive Director, given at University of Murcia in Spain.

1. March 4, 2010 Universidad de Murcia Michael Korcuska, Executive Director, Sakai Foundation

2. About Sakai

3. Sakai History Courseware Management System Started in 2004 Michigan, Indiana, Stanford, MIT (and Berkeley) Mellon Foundation Grant 2.7 release in QA

4. Why Start Sakai? 5 Schools with Homegrown CMS Inefficient to build 5 systems Wanted to maintain control Experts in teaching and learning Desire to work together and share knowledge

5. Why Sakai? Stanford wrote about 20% of the original code in Sakai. What we have received in return is five times what we have put in, a tremendous return on investment. The value of community source is very real to us. Lois Brooks Director of Academic Computing Stanford University Coursework, Stanford University

6. Course Management Research & Collaboration Sakaibrary Portfolios Defining Sakai: Product Scope COURSE MANAGEMENT — all the tools of a modern course management system. RESEARCH & COLLABORATION — project sites for research and work group collaboration. SAKAIBRARY — Library-led component to add citations directly into Sakai. PORTFOLIOS — Open Source Portfolio (OSP) is a core part of Sakai.

7. Defining Sakai: Community COMPOSITION — educational institutions & commercial enterprises working in partnership with standards bodies & other open-source initiatives. GOALS — work collaboratively to develop innovative software applications designed to enhance teaching, learning, research & collaboration in education. VALUES — knowledge sharing, information transparency, meritocracy. Educational Institutions Standards Bodies Open Source Commercial Affiliates

8. Sakai on the ground 200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users

9. Some Sakai Names Oxford Cambridge Stockholm University Limerick Umea University UniversidadPolitécnica de Valencia UniversidadPública de Navarra UniversidadeFernando Pessoa Paris 6 (UPMC) Universite de Poitiers University of Amsterdam Universitat de Lleida Roskilde Universitetscenter Yale Stanford UC Berkeley University of Michigan Indiana University Johns Hopkins Rutgers Virginia Tech University of Virginia University of Delaware University of Florida Etudes Consortium (22 colleges) University of Montreal

10. Sakai on the ground CTOOLS, University of Michigan First production Sakai deployment, 2004

11. Defining Sakai: Code OPEN LICENSING — Sakai’s software is made available under the terms of the ECL, a variant of the Apache license. The ECL encourages a wide range of use, including commercial use. NO FEES OR ROYALTIES — Sakai is free to acquire, use, copy, modify, merge, publish, redistribute & sublicense for any purpose provided our copyright notice & disclaimer are included. NO “COPYLEFT” RESTRICTIONS — unlike GPL redistributed derivative works are neither required to adopt the Sakai license nor publish the source code as open-source. EDUCATIONAL COMMUNITY LICENSE (ECL)

12. Open Source Value Vendor Software Customization Local Version New Version Customization Again Local Version New Version Proprietary Software Brick Wall

13. Defining Sakai: Foundation MISSION — manage & protect intellectual property; provide basic infrastructure & small staff; help coordinate design, development, testing & distribution of software; champion open source & open standards. GOVERNANCE — ten board members elected by member reps to serve three-year terms; Executive Director manages day-to-day operations. PARTNERS — ~100member organizations contribute $5k - $10k BUDGET — funds 4-6 staffers, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.

14. Why Sakai? UCT decided to move to open source in 2004, migrating from WebCT & a home-grown system. Open source offers the advantages of flexibility & avoids the risks of vendor lock-in & escalating license costs. We were attracted to Sakai by the size & expertise of the community around it. Stephen Marquard, Learning Technologies Coordinator, University of Cape Town

15. What will the future bring? Integrated, enterprise software? Configurable personal learning environments? Loose aggregations of web 2.0 applications (mashups)? Google Wave replaces VLE? Mobile devices take over? The 5 minute university?

16. More Words of Wisdom

17. What does the future hold? Integrated, enterprise software? Configurable personal learning environments? Diverse aggregations of web applications (mashups)? Mobile devices take over? Google Wave replaces augments VLE? The 5 minute university? YES!

18. Why Sakai? The people at this conference are the best qualified to define the future of the LMS. You don’t need to be alone: Sakai community shares ideas and risks Design the Future with the Best Academic Partners Around the World

19. Past and future Sakai Foundation

20. Focus on Quality August 2007: My first month at Sakai Sakai release 2.4 going in production Large institutions spending too much time on troubleshooting & maintenance Fewer resources for new feature development Immediate Foundation Goal Quality, Quality, Quality Other Issues Desire to rebuild Sakai UX (Perception of a) developer-dominated community Roadmap

21. Challenges Predictable Roadmap Good things are happening When will they emerge into the release? Action: Hiring Sakai Product Manager to help address Communication Who is working on what? Who is interested in the same things I am? Action: Hiring Sakai Communication Manager Managing New Feature Development What should be in the release? What should be removed? Action: New Product Development Process

22. Product Life Cycle

24. Try new technologies

25. Prove desirability

26. Create dev team/plan

28. Test

31. Noah Botimer (Michigan)

32. Eli Cochran (Berkeley)

33. Michael Feldstein (Oracle)

34. Clay Fenlason (Georgia Tech & Sakai)

35. David Goodrum (Indiana)

36. John Lewis (Unicon)

37. Stephen Marquard (Cape Town)

38. John Norman (Cambridge)

41. Google docs/apps, Social Networking, Web 2.0

42. Success of project sites = Sakai beyond courses

43. New technologies

44. Standards-based, open source projects

45. JCR (Jackrabbit)

46. Open Social (Shindig)

47. Client-side programming

49. Content Organization, Searching & Tagging Sakai 3 Themes 29 Learning Space Construction Breaking the Site Boundary Customizable Workflows (No Tool Silos) Academic Networking The unSakai Open Teaching

50. http://3akai.sakaifoundation.org Sakai 3 Demo 30

51. Thank You!