Sakai Europe 2010 V02


Published on

My closing presentation to Sakai Europe Conference in Valencia, Spain. Also my last public presentation as Executive Director of Sakai.

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

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Sakai Europe 2010 V02

  1. 1. Sakai Europe<br />Michael Korcuska<br />Executive Director<br />Sakai Foundation<br />(for a bit longer)<br />(Still)<br />
  2. 2. Outline<br />Looking forward<br />Sakai 3<br />My advice to<br />Sakai<br />Sakai in Europe<br />
  3. 3. The Future: Sakai 3<br />
  4. 4. Sakai 3: Why?<br />Changing expectations<br />Google docs/apps, Social Networking, Web 2.0<br />Success of project sites = Sakai beyond courses<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 />Years of hard-won knowledge<br />4<br />
  5. 5. And so…<br />Proto by Hubert Stoffels<br />The time to repair the roof is when the sun is shining.<br />John F. Kennedy<br />
  6. 6. 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 />
  7. 7. End User perspective<br />Sakai 3<br />
  8. 8. Content Organization, Searching & Tagging<br />Sakai 3 Themes<br />8<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 />
  9. 9. Learning Space Construction<br />1<br />Photos by Cyprien Lomas<br />Really “Scholarly Space”<br />Teaching & Learning plus….<br />Research, collaboration and portfolios<br />Principles<br />Everyone creates content<br />Simple integration of interactive options<br />Author(s) control presentation and workflow<br />
  10. 10. Academic Spaces: Building Blocks<br />Simple Content Authoring:<br />Easy page creation (wiki-like)<br />WYSIWYG Editing<br />Templates (page and site)<br />Versioning<br />Enhanced with Academic Functionality<br />Interactive Widgets (e.g. assignments & feedback)<br />Allows integration of content and activities<br />10<br />
  11. 11. Templates<br />Templates provide scaffolding for majority of users<br />But can be bypassed for advanced needs<br />Page Templates<br />Sections with (editable) content<br />Site Templates<br />Predefined pages and dashboards<br />
  12. 12. 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 />Unified content repository<br />Content not tied to site<br />Everything in one storage area<br />BUT: Sakai is not a full Content Management System<br />No complex approval workflows<br />No fancy layout capabilities<br />Everyone is an author in Sakai<br />12<br />2<br />
  13. 13. 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 />13<br />
  14. 14. 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 />14<br />
  15. 15. Workflow & Architecture<br />15<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
  16. 16. Resists intuitive workflows
  17. 17. Contributes to inconsistent user experience</li></li></ul><li>Workflow & Architecture<br />16<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
  18. 18. UX oversight is more complicated
  19. 19. Workflows built across services
  20. 20. Encourages presentation & service separation</li></ul>Workflow<br />
  21. 21. 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 />17<br />Photo by Zoom Zoom<br />
  22. 22. The unSakai<br />18<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 />
  23. 23. Sakai 3 Functional Architecture<br />Public<br />Users<br />Groups<br />Collaboration Spaces<br />Personal Spaces<br />PLE<br />Learning<br />Research<br />Project<br />Portfolio<br />Profile<br />Meaningful Arrangements<br />Dynamic, Collaborative Pages<br />Dashboards<br />Defined & Custom Workflows<br />Fundamental Capabilities<br />Wiki-like Content Editing<br />Page Templates<br />Interactive Widgets<br />Unified Content Repository<br />Authored Pages<br />Media<br />Uploaded Files<br />Contextual Content<br />
  24. 24. Sakai 3 Technology<br />Why Sakai 3?<br />
  25. 25. Using Open Source<br />Don’t write our own code<br />If we can help it<br />Criteria:<br />Functionality<br />License-compatible open source<br />Open standard<br />Approachable community<br />
  26. 26. Sakai and Apache<br />Sakai 3 Kernel built on Apache Sling<br />RESTful web development framework for content management<br />Sling incorporates Jackrabbit and Felix<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 />22<br />
  27. 27. Community Practices<br />
  28. 28. Community Practices<br />Functional Leadership<br />Design First<br />Minimize Technology Frameworks<br />Quality Focused<br />Unit (and other) Tests<br />Internationalization & Accessibility<br />
  29. 29. Timelines<br />
  30. 30. What I hear<br />Sakai 3 needs to go faster. Why aren’t more people working on it?<br />We’re getting pressure to switch to Moodle<br />It’s too hard to maintain/develop<br />We’re in no hurry but are looking forward to Sakai 3<br />Too much emphasis is being placed on Sakai 3. We need to work harder on Sakai 2<br />
  31. 31. Why Sakai 3 is Critical<br />Sooner or later your users will want more<br />Substantial growth in the community will require something different<br />The vision of a platform for local innovation requires different technology<br />Sakai 3: It is not a question “if”, but “when?” and “how?”<br />
  32. 32. Balance of Resources<br />Maintenance of Sakai 2?<br />Minor features for Sakai 2?<br />Major new features for Sakai 2?<br />Sakai 3?<br />The difficult question is feature development. Maintenance of Sakai 2 must continue. But the majority of new feature effort must move to Sakai 3 “soon”<br />
  33. 33. My View<br />2.8 is likely and important<br />Google integration<br />Gradebook 2<br />Assignments 2<br />No 2.9!<br />New tools/features built on Sakai 3<br />Evolution of Sakai 2 tools as “independent release” on top of 2.8 core services<br />
  34. 34. Timelines<br />30<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 />
  35. 35. Plan<br />Several institutions are begging to assemble a coordinated team<br />Includes existing Sakai users and new Universities<br />Centralized project management<br />Goal:<br />Basic hybrid version by July<br />A usable release by March 2011<br />Perhaps this is Sakai 3.0?<br />Specialized tools still come from Sakai 2<br />
  36. 36. Sakai 3 and Sakai Europe<br />Get involved<br />Immediate: Localizing Sakai<br />Sakai 3 team needs feedback on I18n<br />You know what happens if you leave this to the Anglo-Saxons.<br />For Denver: Get organized<br />Find a way to provide resources to the project<br />Requirements, design, development, testing<br />
  37. 37. Parting Words<br />Advice for the Sakai Community<br />
  38. 38. What the community needs to do<br />Don’t wait for the Sakai Foundation<br />Leadership needs to come from the community<br />The Board does not control the product<br />Invest in Sakai 3<br />Sakai 2 works well<br />But will not deliver the long-term vision<br />
  39. 39. What Europe needs to do<br />Work together more effectively<br />Despite the various barriers<br />Promote Sakai throughout Europe<br />Conference presentations (e.g. Online Educa)<br />Boca a boca<br />Speak up on list!<br />
  40. 40. What the Foundation needs to do<br />I’m not going to answer this question…<br />That will be up to the community and the next Executive Director<br />
  41. 41. Thank You<br />The most interesting (and challenging) assignment I’ve every had.<br />I was often surprised<br />At how hard some things are<br />At how easy others are<br />At how difficult it is to tell whether I had anything do with either of those outcomes<br />
  42. 42. Anthony Whyte<br />For his stalwart support of Sakai developers everywhere<br />For his willingness to do what it takes to make Sakai succeed<br />For his positive attitude in the face of challenges<br />For his help making my tenure both successful and enjoyable<br />