Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Murcia Sakai 2010 03


Published on

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

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

Murcia Sakai 2010 03

  1. 1. March 4, 2010<br />Universidad de Murcia<br />Michael Korcuska, Executive Director, Sakai Foundation<br />
  2. 2. About Sakai<br />
  3. 3. Sakai History<br />Courseware Management System<br />Started in 2004 <br />Michigan, Indiana, Stanford, MIT (and Berkeley)<br />Mellon Foundation Grant<br />2.7 release in QA<br />
  4. 4. Why Start Sakai?<br />5 Schools with Homegrown CMS<br />Inefficient to build 5 systems<br />Wanted to maintain control<br />Experts in teaching and learning<br />Desire to work together and share knowledge<br />
  5. 5. Why Sakai?<br />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.<br />Lois Brooks<br />Director of Academic Computing <br />Stanford University<br />Coursework, Stanford University<br />
  6. 6. Course Management<br />Research & Collaboration<br />Sakaibrary<br />Portfolios<br />Defining Sakai: Product Scope<br />COURSE MANAGEMENT — all the tools of a modern course management system.<br />RESEARCH & COLLABORATION — project sites for research and work group collaboration.<br />SAKAIBRARY — Library-led component to add citations directly into Sakai.<br />PORTFOLIOS — Open Source Portfolio (OSP) is a core part of Sakai.<br />
  7. 7. Defining Sakai: Community<br />COMPOSITION — educational institutions & commercial enterprises working in partnership with standards bodies & other open-source initiatives.<br />GOALS — work collaboratively to develop innovative software applications designed to enhance teaching, learning, research & collaboration in education.<br />VALUES — knowledge sharing, information transparency, meritocracy.<br />Educational Institutions<br />Standards <br />Bodies<br />Open Source<br />Commercial Affiliates<br />
  8. 8. Sakai on the ground<br />200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users<br />
  9. 9. Some Sakai Names<br />Oxford<br />Cambridge<br />Stockholm University<br />Limerick<br />Umea University<br />UniversidadPolitécnica de Valencia <br />UniversidadPública de Navarra<br />UniversidadeFernando Pessoa<br />Paris 6 (UPMC)<br />Universite de Poitiers<br />University of Amsterdam<br />Universitat de Lleida<br />Roskilde Universitetscenter<br />Yale<br />Stanford<br />UC Berkeley<br />University of Michigan<br />Indiana University<br />Johns Hopkins<br />Rutgers<br />Virginia Tech<br />University of Virginia<br />University of Delaware<br />University of Florida<br />Etudes Consortium (22 colleges)<br />University of Montreal<br />
  10. 10. Sakai on the ground<br />CTOOLS, University of Michigan<br />First production Sakai deployment, 2004<br />
  11. 11. Defining Sakai: Code<br />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. <br />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.<br />NO “COPYLEFT” RESTRICTIONS — unlike GPL redistributed derivative works are neither required to adopt the Sakai license nor publish the source code as open-source.<br />EDUCATIONAL COMMUNITY LICENSE (ECL)<br />
  12. 12. Open Source Value<br />Vendor Software<br />Customization<br />Local Version<br />New Version<br />Customization Again<br />Local Version<br />New Version<br />Proprietary Software Brick Wall<br />
  13. 13. Defining Sakai: Foundation<br />MISSION — manage & protect intellectual property; provide basic infrastructure & small staff; help coordinate design, development, testing & distribution of software; champion open source & open standards.<br />GOVERNANCE — ten board members elected by member reps to serve three-year terms; Executive Director manages day-to-day operations.<br />PARTNERS — ~100member organizations contribute $5k - $10k<br />BUDGET — funds 4-6 staffers, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.<br />
  14. 14. Why Sakai?<br />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.<br />Stephen Marquard, Learning Technologies Coordinator, <br />University of Cape Town <br />
  15. 15. What will the future bring? <br />Integrated, enterprise software?<br />Configurable personal learning environments?<br />Loose aggregations of web 2.0 applications (mashups)?<br />Google Wave replaces VLE?<br />Mobile devices take over?<br />The 5 minute university?<br />
  16. 16. More Words of Wisdom<br />
  17. 17. What does the future hold? <br />Integrated, enterprise software?<br />Configurable personal learning environments?<br />Diverse aggregations of web applications (mashups)?<br />Mobile devices take over?<br />Google Wave replaces augments VLE?<br />The 5 minute university?<br />YES!<br />
  18. 18. Why Sakai?<br />The people at this conference are the best qualified to define the future of the LMS.<br />You don’t need to be alone: Sakai community shares ideas and risks<br />Design the Future with the Best Academic Partners Around the World<br />
  19. 19. Past and future<br />Sakai Foundation<br />
  20. 20. Focus on Quality<br />August 2007: My first month at Sakai<br />Sakai release 2.4 going in production<br />Large institutions spending too much time on troubleshooting & maintenance<br />Fewer resources for new feature development<br />Immediate Foundation Goal<br />Quality, Quality, Quality<br />Other Issues<br />Desire to rebuild Sakai UX<br />(Perception of a) developer-dominated community<br />Roadmap<br />
  21. 21. Challenges<br />Predictable Roadmap<br />Good things are happening<br />When will they emerge into the release?<br />Action: Hiring Sakai Product Manager to help address<br />Communication<br />Who is working on what?<br />Who is interested in the same things I am?<br />Action: Hiring Sakai Communication Manager<br />Managing New Feature Development<br />What should be in the release?<br />What should be removed?<br />Action: New Product Development Process<br />
  22. 22. Product Life Cycle<br />
  23. 23. Community<br />Major Product Changes<br /><ul><li> Generate new ideas
  24. 24. Try new technologies
  25. 25. Prove desirability
  26. 26. Create dev team/plan
  27. 27. Reduce dev risks</li></ul>Product Council<br /><ul><li> Finish building
  28. 28. Test
  29. 29. Document</li></li></ul><li>Product Council<br />Authority:<br />Decide what is in the official release<br />How:<br />Based on objective criteria as much as possible<br />Open process and document decision-making<br />Also:<br />Provide guidance to incubation projects who are wondering what they need to do to make the release<br />
  30. 30. Product Council<br /><ul><li>Nate Angell (rSmart)
  31. 31. Noah Botimer (Michigan)
  32. 32. Eli Cochran (Berkeley)
  33. 33. Michael Feldstein (Oracle)
  34. 34. Clay Fenlason (Georgia Tech & Sakai)
  35. 35. David Goodrum (Indiana)
  36. 36. John Lewis (Unicon)
  37. 37. Stephen Marquard (Cape Town)
  38. 38. John Norman (Cambridge)
  39. 39. Max Whitney (NYU)</li></li></ul><li>Why and What and When<br />Sakai 3<br />
  40. 40. Why Build Sakai 3?<br />27<br /><ul><li>Changing expectations
  41. 41. Google docs/apps, Social Networking, Web 2.0
  42. 42. Success of project sites = Sakai beyond courses
  43. 43. New technologies
  44. 44. Standards-based, open source projects
  45. 45. JCR (Jackrabbit)
  46. 46. Open Social (Shindig)
  47. 47. Client-side programming
  48. 48. JavaScript/AJAX</li></li></ul><li>Benefits<br />Increased end-user satisfaction<br />Flexibility for site owners<br />Best of class user experience<br />Stability, quality & scalability<br />Smaller code base, shared with other OS projects<br />Transaction-level clustering<br />Fewer local customizations<br />More knowledge of existing uses cases<br />Simpler development environment<br />Java and JavaScript <br />
  49. 49. Content Organization, Searching & Tagging<br />Sakai 3 Themes<br />29<br />Learning Space Construction<br />Breaking the Site Boundary<br />Customizable Workflows (No Tool Silos)<br />Academic Networking<br />The unSakai<br />Open Teaching<br />
  50. 50.<br />Sakai 3 Demo<br />30<br />
  51. 51. Thank You!<br />