Sakai Charles Sturt Keynote

1,301 views

Published on

My keynote at AuSakai09

Published in: Education, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,301
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sakai Charles Sturt Keynote

  1. 1. Sakai Perspectives<br />Michael Korcuska<br />Executive Director<br />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.6 current release<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. Defining Sakai: Product Scope<br />Course Management<br />Research & Collaboration<br />Sakaibrary<br />Portfolios<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 />
  6. 6. Defining Sakai: Community<br />200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users<br />
  7. 7. Sakai today<br />5 of 10 top Universities use Sakai<br />Stanford<br />Berkeley<br />Cambridge<br />Columbia<br />Oxford<br />#11 (Yale) does too!<br />
  8. 8. 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 />
  9. 9. 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 />
  10. 10. Sakai Foundation<br />MISSION — help coordinate design, development, testing & distribution of software; manage & protect intellectual property; provide basic infrastructure & small staff; champion open source & open standards.<br />PARTNERS — approximately 100 member organizations contribute $10K per year ($5K for smaller institutions, sliding scale for commercial affiliates).<br />GOVERNANCE — ten board members elected by member reps to serve three-year terms; Executive Director manages day-to-day operations.<br />BUDGET — funds 4-6 staffers, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.<br />We are not “in charge” of the Sakai Product. <br />We do develop community practices.<br />
  11. 11. 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 />
  12. 12. Sakai foundation Priorities<br />
  13. 13. Sakai Goals<br />Adoption<br />Broad & Diverse (significant adoption by different types of organizations)<br />The top choice for innovators (perhaps not most popular overall)<br />Product Experience<br />Cohesive, effective and engaging (end users)<br />Platform for local innovation (developers)<br />Easy to deploy/manage (production)<br />Community<br />Easy to contribute (for new & experienced members)<br />Diverse (roles & institutions)<br />Excellence (recognized as desirable to belong to)<br />
  14. 14. 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 />
  15. 15. Changes & Results<br />Increased Foundation staff focused on QA<br />Extended QA Cycle for 2.5 & 2.6<br />Formal Beta and Release Candidates<br />Introduction of Maintenance Releases<br />Currently on Sakai 2.5.5<br />About to release 2.6.1<br />Challenge: Managing 2.5, 2.6 & 2.7 releases simultaneously<br />Not to mention Sakai 3<br />
  16. 16. User Experience Improvement<br />Project launched in 2008<br />Did not make 2.6 release<br />Not enough work completed in time for code freeze<br />Many felt design needed happen on tools before they would deploy on campus<br />2.7 or 3?<br />All energy towards Sakai 3<br />
  17. 17. 2009 Challenges<br />Predictable Roadmap<br />Good things are happening<br />When will they emerge into the release?<br />Action: Sakai Product Manager, Clay Fenlason<br />Communication<br />Who is working on what?<br />Who is interested in the same things I am?<br />Action: Sakai Communication Manager, Pieter Hartsook<br />Creating large changes<br />User Interface Improvement: UX Improvement Project<br />Major Tool Rewrites<br />A Completely New Version<br />Action: New Product Development Process<br />
  18. 18. Product Life Cycle<br />
  19. 19. Community<br />Major Product Changes<br /><ul><li> Generate new ideas
  20. 20. Try new technologies
  21. 21. Prove desirability
  22. 22. Create dev team/plan
  23. 23. Reduce dev risks</li></ul>Product Council<br /><ul><li> Finish building
  24. 24. Test
  25. 25. 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 />
  26. 26. Product Council<br /><ul><li>Nate Angell (rSmart)
  27. 27. Noah Botimer (Michigan)
  28. 28. Eli Cochran (Berkeley)
  29. 29. Michael Feldstein (Oracle)
  30. 30. Clay Fenlason (Georgia Tech & Sakai)
  31. 31. David Goodrum (Indiana)
  32. 32. John Lewis (Unicon)
  33. 33. Stephen Marquard (Cape Town)
  34. 34. John Norman (Cambridge)
  35. 35. Max Whitney (NYU)</li></li></ul><li>Sakai 3: Why?<br />Changing expectations<br />Google docs/apps, Social Networking, Web 2.0<br />Success of project sites = Sakai beyond courses<br />Years of hard-won knowledge<br />New technologies<br />Standards-based, open source projects<br />JCR (Jackrabbit)<br />Open Social (Shindig)<br />Client-side programming<br />JavaScript/AJAX<br />Fluid Project<br />22<br />
  36. 36. Why Now? <br />Proto by Hubert Stoffels<br />The time to repair the roof is when the sun is shining.<br />John F. Kennedy<br />
  37. 37. What?<br />Photos by Hobvias Sudoneighm, Massimo Valiani, and Mathieu Plourde<br />Functionality & User Experience<br />Technology and Developer Experience<br />Community Practices and Culture<br />
  38. 38. End User perspective<br />Sakai 3<br />
  39. 39. Everything is Content<br />Sakai 3 Themes<br />26<br />Learning Space Construction<br />Breaking the Site Boundary<br />Academic Workflows, not (just) Tools<br />Academic Networking<br />The unSakai<br />
  40. 40. Learning Space Construction<br />Really “Academic Space” Construction<br />Teaching & Learning plus….<br />Research, collaboration and portfolios<br />Principles<br />Overall control in hands of space owner(s)<br />Embrace participant content creation<br />Simple integration of common academic functions<br />1<br />Photos by Cyprien Lomas<br />
  41. 41. Academic Spaces: Building Blocks<br />Simple Content Authoring:<br />Easy page creation (wiki-like)<br />WYSIWYG Editing<br />Versioning<br />Templates<br />Page and Site templates<br />Structure, tools and content<br />Enhanced with Academic Functionality<br />Interactive Widgets (e.g. assignments & feedback)<br />28<br />
  42. 42. Everything is Content<br /> Not just files to share<br />Classic “resources” tool in Sakai (of course)<br />Discussion post, user profile, test questions<br />Taggable, searchable, linkable, portable, shareable<br />Addressable by URL<br />Unified content repository<br />Content not tied to site<br />Everything in one storage area<br />29<br />2<br />
  43. 43. Content Management<br />Sakai2<br />Photo by Desirée Delgado<br />Site A<br />Site B<br />Users find things by remembering what site they were in when they saw it.<br />30<br />
  44. 44. Content Management<br />Sakai3<br />Photo by Amy Veeninga<br />Tags: System, Organizational & User<br />Permissions: Who has access, under what conditions<br />Smart Folders<br />Search<br />31<br />
  45. 45. Academic Networking<br />Academic Networking<br />People are important, but “friends” aren’t enough<br />Related content is also relevant, but not the whole story<br />Activity based <br />Who has taken the same classes?<br />Who is reading the same articles? Participating in similar discussions?<br />32<br />3<br />Content<br />People<br />
  46. 46. Academic Networking<br />A platform for exploration<br />We aren’t competing with Facebook<br />We do believe we need to drive R&D in this area<br />Linking networks together<br />Sakai to Sakai<br />Sakai, Moodle, Blackboard, D2L<br />Leveraging existing networks<br />Particularly LinkedIn and Facebook<br />Sharing profile and activity information<br />Creating apps on those platforms<br />Photo by Joël-Evelyñ-FrançoisDézafit-Keltz<br />
  47. 47. The Site Boundary<br />34<br />4<br />All Art Students<br />Studio Art 101<br />User 100<br />User 2<br />User 3<br />User 4<br />User 500<br />.<br />.<br />.<br />User 1<br />User 2<br />User 3<br />User 4<br />User 5<br />.<br />.<br />.<br />Year 1 Art Students<br />Year 1 Art Students<br />Users and groups exist within the context of a site.<br />
  48. 48. Sakai 3 Groups & Sites<br />Groups & Sites managed separately<br />Member of a group – People with something in common<br />Access to a site– Collection of content & functionality<br />Support for hierarchy<br />Art Dept.<br />Art Majors<br />Art Majors<br />Studio 101 Students<br />Studio 101<br />Guest Judges<br />Student Work<br />35<br />
  49. 49. Workflow & Architecture<br />36<br />5<br />Kernel<br />Tool<br />Kernel<br />Service<br />Tool<br />Tool<br />Service<br />Service<br />Kernel<br />Service<br />Service<br />Tool<br />Tool<br />Service<br />Tool<br /><ul><li>Facilitates independent tool development
  50. 50. Resists intuitive workflows
  51. 51. Contributes to inconsistent user experience</li></li></ul><li>Workflow & Architecture<br />37<br />Kernel<br />Workflow<br />Kernel<br />Service<br />Workflow<br />Workflow<br />Service<br />Service<br />Kernel<br />Service<br />Service<br />Workflow<br />Workflow<br />Service<br /><ul><li>Services need to respond to more customers
  52. 52. UX oversight is more complicated
  53. 53. Workflows built across services
  54. 54. Encourages presentation & service separation</li></ul>Workflow<br />
  55. 55. Academic Workflow<br />Beyond Tool Silos<br />Academic work flows often cross tool boundaries<br />Anything can be graded!<br />Anything can be discussed!<br />This exists in Sakai 2<br />But it is too difficult and more needs to be done<br />Example: Instructor puts into syllabus an assignment to create a discussionpost that will be graded.<br />4 tools for both instructors and students!<br />38<br />Photo by Zoom Zoom<br />
  56. 56. Workflow Example<br />39<br />Select text & click “Create Assignment”<br />All<br />Media<br />Images<br /> Videos<br /> Audio<br />Forums<br />Tests<br />Site Pages<br />Polls<br />Jackson Response Forum (3 posts)<br />Create Assignment…<br />Name: Jackson Reading Response<br />Due Date: September 10, 2009<br />Points: 10 (of 150)<br />Type: Individual<br />Description: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum.<br />Link To: Select...<br />Class Intro Forum (27 posts)<br />Forums<br /> Edit Assignment Information<br />Some Other Forum (0 posts)<br />Create<br />Cancel<br />Advanced Options…<br />Link to Something<br />Choose<br />New…<br />
  57. 57. Student View<br />40<br />Assignment: Jackson Reading Response<br />Due Date: September 10, 2009 ( due tomorrow)<br />Status: Not submitted<br />Points: 10 possible (of 150).<br />Description: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Read more…<br />Link(s): Jackson Response Discussion Forum (Create Post…)<br />
  58. 58. Student View, Graded<br />41<br />Assignment: Jackson Reading Response<br />Due Date: September 10, 2009 (due date passed)<br />Status: Submitted and Graded<br />Points: 9/10 (of 150). View feedback<br />Description: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Read more…<br />Link(s): Jackson Response Discussion Forum (go to Forum now)<br />
  59. 59. The unSakai<br />42<br />Kernel<br />Service<br />Service<br />Service<br />iGoogle<br />Facebook<br />Kernel<br />Service<br />Service<br />Service<br />Documented data feeds allow Sakai to appear anywhere<br />Mobile Apps<br />Windows/Mac Widgets<br />
  60. 60. Sakai 3 Technology<br />Why Sakai 3?<br />
  61. 61. Sakai 3 Technology Goals<br />Scalability<br />Millions of users<br />Developer Productivity<br />Faster builds<br />UX & back-end development separated<br />Code Quality & Maintenance<br />Reliance on other open source efforts<br />Increase unit testing<br />Easier to install/build<br />To improve initial experience for new developers<br />44<br />Photo by Luiz Castro<br />
  62. 62. JCR as Content Store<br />Standards-based<br />JSR 170<br />Ships with Apache Jackrabbit, but can be changed<br />Everything as content<br />Discussion post, User profile information, etc.<br />Components put Content into JCR Content store<br />Sakai Kernel creates relational indices in DB<br />Component doesn’t need to do anything<br />Automatic tracking of most events by kernel<br />45<br />
  63. 63. The Point<br />Don’t write our own code<br />Apache Sling is foundation for Sakai 3<br />Sling incorporates Jackrabbit & Felix<br />Criteria:<br />Functionality<br />License-compatible open source<br />Open standard<br />Approachable community<br />Ian Boston is committer on Sling and Shindig<br />
  64. 64. JSON<br />Sakai Kernel supports JSON microformat<br />Components use REST calls to interact with Kernel<br />Benefits<br />Back-end services stay Java-based<br />UX programmers more often skilled in JavaScript<br />Easier UX developers can work on Sakai<br />Tools like GWT can be used for Java-based UI<br />Components can be written using other languages<br />47<br />
  65. 65. Community Practices<br />
  66. 66. Community Practices<br />Functional Leadership<br />Design First<br />Minimize Technology Frameworks<br />Quality Focused<br />Unit (and other) Tests<br />
  67. 67. Timelines and adoption<br />
  68. 68. Timelines<br />51<br />2009<br />2010<br />2011<br />2012<br />2013<br />Sakai 2.5<br />Sakai 2.6<br />Sakai 2.7<br />Hybrid<br />Mode<br />Sakai 3.0<br />Official Releases<br />Previews<br />Sakai 2.8?<br />

×