2009 02 26 Upv V02

589 views
528 views

Published on

Update on Sakai, including plans for Sakai 3, from Sakai Foundation Executive Director Michael Korcuska

Published in: Education

2009 02 26 Upv V02

  1. 1. OVERVIEW & UPDATE February 2009, Valencia, Spain
  2. 2. Agenda <ul><li>Sakai in 2008 </li></ul><ul><ul><li>Focus on Quality </li></ul></ul><ul><ul><li>Challenges </li></ul></ul><ul><li>Sakai 3.0 </li></ul><ul><ul><li>Approach </li></ul></ul><ul><ul><li>Demo </li></ul></ul><ul><ul><li>Getting involved </li></ul></ul><ul><li>Community Survey & Board Retreat </li></ul><ul><ul><li>Survey Results </li></ul></ul><ul><ul><li>New Development Structure? </li></ul></ul>
  3. 3. Focus on Quality <ul><li>August 2007: My first month at Sakai </li></ul><ul><ul><li>Sakai release 2.4 going in production </li></ul></ul><ul><ul><li>Large institutions spending too much time on troubleshooting & maintenance </li></ul></ul><ul><ul><li>Fewer resources for new feature development </li></ul></ul><ul><li>Immediate Foundation Goal </li></ul><ul><ul><li>Quality, Quality, Quality </li></ul></ul><ul><li>Other Issues </li></ul><ul><ul><ul><li>Dissatisfaction with Sakai UX </li></ul></ul></ul><ul><ul><ul><li>Upcoming Newport Beach Conference </li></ul></ul></ul><ul><ul><ul><li>No location selected for Summer 2008 conference </li></ul></ul></ul><ul><ul><ul><li>Too much time/money spent on organizing conferences </li></ul></ul></ul>
  4. 4. Changes & Results <ul><li>Increased Foundation staff focused on QA </li></ul><ul><li>Extended QA Cycle for 2.5 </li></ul><ul><ul><li>Formal Beta and Release Candidates </li></ul></ul><ul><ul><li>University of Cape Town running Beta in production </li></ul></ul><ul><ul><li>Final 2.5.0 release in March instead of November </li></ul></ul><ul><li>Introduction of Maintenance Releases </li></ul><ul><ul><li>Currently on Sakai 2.5.4, the most reliable version of Sakai to date </li></ul></ul><ul><li>Challenge: Managing 2.5 and 2.6 releases simultaneously </li></ul>
  5. 5. UX Improvement <ul><li>Did not make 2.6 release </li></ul><ul><ul><li>Not enough work completed in time for code freeze </li></ul></ul><ul><ul><li>Many felt design needed happen on tools before they would deploy on campus </li></ul></ul><ul><li>2.7 or 3.0? </li></ul><ul><ul><li>Currently the Foundation is working towards 3.0 </li></ul></ul><ul><ul><li>Design work can be implemented for 2.7, but we need resources willing to do this </li></ul></ul><ul><li>Overall Result </li></ul><ul><ul><li>Positive change in direction </li></ul></ul><ul><ul><li>Won’t be satisfied until changes reach release </li></ul></ul>
  6. 6. Foundation Spending January - September Slowly Moving in Right Direction
  7. 7. Current Challenges <ul><li>Predictable Roadmap </li></ul><ul><ul><li>Good things are happening </li></ul></ul><ul><ul><li>When will they emerge into the release? </li></ul></ul><ul><li>Creating large changes </li></ul><ul><ul><li>User Interface Improvement </li></ul></ul><ul><ul><li>Major Tool Rewrites </li></ul></ul><ul><ul><li>A Completely New Version? </li></ul></ul>
  8. 8. <ul><li>Why and What and When </li></ul>Sakai 3
  9. 9. Sakai 3 Needs <ul><li>Changes in user expectations </li></ul><ul><ul><li>Web 2.0 </li></ul></ul><ul><ul><li>Beyond course support </li></ul></ul><ul><li>New technology </li></ul><ul><ul><li>More standards open source projects to leverage </li></ul></ul><ul><ul><ul><li>JCR (Jackrabbit) </li></ul></ul></ul><ul><ul><ul><li>O p en Social (Shindig) </li></ul></ul></ul><ul><ul><li>Client-side programming </li></ul></ul><ul><ul><ul><li>JavaScript/AJAX </li></ul></ul></ul>
  10. 10. Sakai 3 for Users <ul><li>Academic Networking </li></ul><ul><ul><li>Connections are important </li></ul></ul><ul><ul><li>Not friends, per se, but connections </li></ul></ul><ul><ul><li>Includes research and people </li></ul></ul><ul><li>Content authoring and organization </li></ul><ul><ul><li>Flexible page creation </li></ul></ul><ul><ul><li>Template-based authoring </li></ul></ul><ul><ul><li>Everything is content </li></ul></ul><ul><ul><ul><li>Searchable, linkable, portable </li></ul></ul></ul>
  11. 11. Sakai 3 for Users cont. <ul><li>Groups & Sites (call them spaces?) </li></ul><ul><ul><ul><li>Join a group </li></ul></ul></ul><ul><ul><ul><ul><li>A collection of people with something in common </li></ul></ul></ul></ul><ul><ul><ul><li>Have access to a site/space </li></ul></ul></ul><ul><ul><ul><ul><li>A collection of content and functionality </li></ul></ul></ul></ul><ul><ul><ul><li>Multiple groups can have access to the same space </li></ul></ul></ul><ul><li>Treatment of content </li></ul><ul><ul><ul><li>Stored in a general repository </li></ul></ul></ul><ul><ul><ul><li>Available in a variety of sites/spaces </li></ul></ul></ul><ul><ul><ul><li>“ Everything” is content </li></ul></ul></ul>
  12. 12. Content in Sakai 3
  13. 13. Sakai 3 for Users (cont.) <ul><li>Beyond Tool Silos </li></ul><ul><ul><li>Academic work flows often cross tool boundaries </li></ul></ul><ul><ul><ul><li>Anything can be graded! </li></ul></ul></ul><ul><ul><ul><li>Anything can be discussed! </li></ul></ul></ul><ul><ul><li>This is beginning to appear in Sakai 2 </li></ul></ul><ul><ul><ul><li>But more needs to be done </li></ul></ul></ul><ul><li>Example: Assignments Tool </li></ul><ul><ul><li>Yes, students need a list of all assignments </li></ul></ul><ul><ul><li>But should they need to go to the assignments tool in each class to find them? </li></ul></ul>
  14. 14. <ul><li>http://3akai.sakaifoundation.org </li></ul>Sakai 3 Demo
  15. 15. Sakai 3 Technology <ul><li>Scalability </li></ul><ul><ul><li>Remove bottlenecks from Sakai 2. </li></ul></ul><ul><ul><li>Initial tests show large improvements; need more proof. </li></ul></ul><ul><li>Developer Productivity </li></ul><ul><ul><li>Faster builds </li></ul></ul><ul><ul><li>UX & back-end development separated </li></ul></ul><ul><li>Code Quality & Maintenance </li></ul><ul><ul><li>Reliance on other open source efforts </li></ul></ul><ul><ul><li>Increase unit testing </li></ul></ul><ul><li>Easier to install/build </li></ul><ul><ul><li>To improve initial experience for new developers </li></ul></ul>
  16. 16. JCR as Content Store <ul><li>Standards-based </li></ul><ul><ul><li>JSR 170 </li></ul></ul><ul><ul><li>Ships with Apache Jackrabbit, but can be changed </li></ul></ul><ul><li>Everything as content </li></ul><ul><ul><li>Discussion post, User profile information, etc. </li></ul></ul><ul><ul><li>Components put Content into JCR Content store </li></ul></ul><ul><ul><li>Sakai Kernel creates relational indices in DB </li></ul></ul><ul><ul><ul><li>Component doesn’t need to do anything </li></ul></ul></ul><ul><ul><ul><li>Automatic tracking of most events by kernel </li></ul></ul></ul>
  17. 17. JSON <ul><li>Sakai Kernel provides JSON microformat </li></ul><ul><li>Components use REST calls to interact with Kernel </li></ul><ul><li>Again, standards based </li></ul><ul><ul><li>JAX-RS currently in Kernel (JSR 311) </li></ul></ul><ul><li>Benefits </li></ul><ul><ul><li>Back-end services stay Java-based </li></ul></ul><ul><ul><li>UX programmers more often skilled in JavaScript </li></ul></ul><ul><ul><ul><li>Easier UX developers can work on Sakai </li></ul></ul></ul><ul><ul><li>Tools like GWT can be used for Java-based UI </li></ul></ul><ul><ul><li>Components can be written using other languages </li></ul></ul>
  18. 18. Sakai 3 Participation <ul><li>K2 Working Group </li></ul><ul><ul><li>http://groups.google.com/group/sakai-kernel </li></ul></ul><ul><li>UX Design Work </li></ul><ul><ul><li>UX list </li></ul></ul><ul><ul><li>http://groups.google.com/group/3akai </li></ul></ul><ul><li>How would you like to be involved? </li></ul><ul><ul><li>Development </li></ul></ul><ul><ul><ul><li>Java & JavaScript </li></ul></ul></ul><ul><ul><li>Design </li></ul></ul><ul><ul><ul><li>Conceptual, interaction and visual </li></ul></ul></ul>
  19. 19. When <ul><li>Q1 2009: Sakai 2.6 </li></ul><ul><li>Q3 2009: Sakai 2.6.# </li></ul><ul><ul><li>A maintenance release for fall production </li></ul></ul><ul><li>2010 </li></ul><ul><ul><li>Q1: Sakai 2.7 (New assignments tool and gradebook?) </li></ul></ul><ul><ul><li>Later: First versions of Sakai 3 </li></ul></ul><ul><ul><ul><li>Not functionally equivalent to 2.7 </li></ul></ul></ul><ul><ul><ul><li>Suitable for new adoptions </li></ul></ul></ul><ul><ul><ul><li>“ Hybrid” version for existing Sakai schools </li></ul></ul></ul><ul><li>2011 </li></ul><ul><ul><li>Sakai 3 as full replacement </li></ul></ul><ul><ul><li>Maintenance releases for Sakai 2.7 through 2013 </li></ul></ul><ul><ul><li>No version 2.8 </li></ul></ul>
  20. 20. <ul><li>Community Survey & Board Retreat </li></ul>Changing Practices?
  21. 21. Survey <ul><li>50+ Organizational Responses </li></ul><ul><li>150+ Individual Responses </li></ul><ul><li>Overall </li></ul><ul><ul><li>Sense of overall stability </li></ul></ul><ul><ul><li>Trust in Sakai board </li></ul></ul><ul><ul><li>Want to spend more time on community Sakai </li></ul></ul><ul><ul><li>Believe that Sakai will be the best platform </li></ul></ul>
  22. 22. Community Wants <ul><li>Clear product vision & direction </li></ul><ul><li>More communication from Foundation </li></ul><ul><li>Roadmap that allows campus advocates to effectively communicate with stakeholders </li></ul><ul><li>Project structure that attracts sufficient resources and uses them effectively </li></ul><ul><li>More input from functional experts & designers </li></ul><ul><li>Allow diverse types participation </li></ul><ul><ul><li>Large and small, Formal and informal, Institutional and individual </li></ul></ul>
  23. 23. Ways of Getting Work Done <ul><li>Organic – Contributors participate in the community based on personal/local interests and priorities. It is the responsibility of the individual to communicate and request broader contribution. </li></ul><ul><li>Coordinated – Community structures actively seek to identify and align common contributions. Unmet needs are identified to leaders to encourage investment. </li></ul><ul><li>Managed – Resources are committed to achieve a defined set of deliverables. Central authority determines priorities. </li></ul>
  24. 24. Product Life Cycle
  25. 25. Major Product Changes <ul><li>Generate new ideas </li></ul><ul><li>Try new technologies </li></ul><ul><li>Prove desirability </li></ul><ul><li>Create dev team/plan </li></ul><ul><li>Reduce dev risks </li></ul><ul><li>Finish building </li></ul><ul><li>Test </li></ul><ul><li>Document </li></ul>Community Product Council Product Council Product Council
  26. 26. Changes <ul><li>What’s the same? </li></ul><ul><ul><li>Open development process </li></ul></ul><ul><ul><li>Low barrier to entry for R&D projects </li></ul></ul><ul><ul><li>Independent projects possible/encouraged </li></ul></ul><ul><ul><li>Small feature development remains the same </li></ul></ul><ul><ul><li>Structural Similarities, possible misperception </li></ul></ul><ul><ul><ul><li>R&D ≠ Contrib, Incubation ≠ Provisional, Project ≠ Core </li></ul></ul></ul><ul><li>What is different? </li></ul><ul><ul><li>Adherence to criteria from Incubation to Project </li></ul></ul><ul><ul><li>Managed process for development team(s) </li></ul></ul><ul><ul><li>Product Council to enforce criteria for making release </li></ul></ul><ul><ul><li>The notion of a maintenance group </li></ul></ul>
  27. 27. Remaining Questions <ul><li>Will the community accept the model? </li></ul><ul><ul><li>Foundation recommends, but community decides </li></ul></ul><ul><li>Who is the Product Council? </li></ul><ul><ul><li>A small group led by Sakai Foundation? </li></ul></ul><ul><ul><li>A larger panel of community representatives? </li></ul></ul><ul><li>A Maintenance Team? </li></ul><ul><ul><li>A group of developers (part time), directed by the Foundation to fix bugs </li></ul></ul><ul><ul><li>Incentive for products to be in official release </li></ul></ul><ul><ul><ul><li>And meet standards for inclusion </li></ul></ul></ul>

×