Murcia Sakai 2010 03
Download as PPTX, PDF0 likes724 views
The document outlines the history and development of Sakai, an open-source course management system initiated in 2004 by a consortium of universities seeking to enhance collaboration and flexibility while avoiding vendor lock-in. Key features include community-driven development, various educational tools, and a commitment to open-source values, supported by a foundation that manages governance and funding. The future of Sakai involves adapting to evolving educational technology trends such as integrated software solutions and user-friendly learning environments.
Murcia Sakai 2010 03
- 1. March 4, 2010Universidad de MurciaMichael Korcuska, Executive Director, Sakai Foundation
- 2. About Sakai
- 3. Sakai HistoryCourseware Management SystemStarted in 2004 Michigan, Indiana, Stanford, MIT (and Berkeley)Mellon Foundation Grant2.7 release in QA
- 4. Why Start Sakai?5 Schools with Homegrown CMSInefficient to build 5 systemsWanted to maintain controlExperts in teaching and learningDesire 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 BrooksDirector of Academic Computing Stanford UniversityCoursework, Stanford University
- 6. Course ManagementResearch & CollaborationSakaibraryPortfoliosDefining Sakai: Product ScopeCOURSE 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: CommunityCOMPOSITION — 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 InstitutionsStandards BodiesOpen SourceCommercial Affiliates
- 8. Sakai on the ground200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users
- 9. Some Sakai NamesOxfordCambridgeStockholm UniversityLimerickUmea UniversityUniversidadPolitécnica de Valencia UniversidadPública de NavarraUniversidadeFernando PessoaParis 6 (UPMC)Universite de PoitiersUniversity of AmsterdamUniversitat de LleidaRoskilde UniversitetscenterYaleStanfordUC BerkeleyUniversity of MichiganIndiana UniversityJohns HopkinsRutgersVirginia TechUniversity of VirginiaUniversity of DelawareUniversity of FloridaEtudes Consortium (22 colleges)University of Montreal
- 10. Sakai on the groundCTOOLS, University of MichiganFirst production Sakai deployment, 2004
- 11. Defining Sakai: CodeOPEN 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 ValueVendor SoftwareCustomizationLocal VersionNew VersionCustomization AgainLocal VersionNew VersionProprietary Software Brick Wall
- 13. Defining Sakai: FoundationMISSION — 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 - $10kBUDGET — 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 risksDesign the Future with the Best Academic Partners Around the World
- 19. Past and futureSakai Foundation
- 20. Focus on QualityAugust 2007: My first month at SakaiSakai release 2.4 going in productionLarge institutions spending too much time on troubleshooting & maintenanceFewer resources for new feature developmentImmediate Foundation GoalQuality, Quality, QualityOther IssuesDesire to rebuild Sakai UX(Perception of a) developer-dominated communityRoadmap
- 21. ChallengesPredictable RoadmapGood things are happeningWhen will they emerge into the release?Action: Hiring Sakai Product Manager to help addressCommunicationWho is working on what?Who is interested in the same things I am?Action: Hiring Sakai Communication ManagerManaging New Feature DevelopmentWhat should be in the release?What should be removed?Action: New Product Development Process
- 23. CommunityMajor Product Changes Generate new ideas
- 24. Try new technologies
- 26. Create dev team/plan
- 27. Reduce dev risksProduct Council Finish building
- 28. Test
- 29. DocumentProduct CouncilAuthority:Decide what is in the official releaseHow:Based on objective criteria as much as possibleOpen process and document decision-makingAlso:Provide guidance to incubation projects who are wondering what they need to do to make the release
- 30. Product CouncilNate Angell (rSmart)
- 34. Clay Fenlason (Georgia Tech & Sakai)
- 37. Stephen Marquard (Cape Town)
- 39. Max Whitney (NYU)Why and What and WhenSakai 3
- 40. Why Build Sakai 3?27Changing expectations
- 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)
- 48. JavaScript/AJAXBenefitsIncreased end-user satisfactionFlexibility for site ownersBest of class user experienceStability, quality & scalabilitySmaller code base, shared with other OS projectsTransaction-level clusteringFewer local customizationsMore knowledge of existing uses casesSimpler development environmentJava and JavaScript
- 49. Content Organization, Searching & TaggingSakai 3 Themes29Learning Space ConstructionBreaking the Site BoundaryCustomizable Workflows (No Tool Silos)Academic NetworkingThe unSakaiOpen Teaching
- 51. Thank You!