Sakai Foundation Update 2009


Published on

An update on the activities of the Sakai Foundation. Presented at the 10th Sakai Conference in Boston.

Published in: Education
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 Foundation Update 2009

  1. 1. Sakai Foundation Update<br />Michael Korcuska<br />July 8, 2009<br />
  2. 2. Agenda<br />Sakai Foundation in 2008<br />Sakai Foundation in 2009<br />Membership<br />Finances<br />Conferences<br />Proposed by-law changes<br />
  3. 3. 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 />
  4. 4. Sakai foundation 2008<br />
  5. 5. 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 />
  6. 6. Changes & Results<br />Increased Foundation staff focused on QA<br />Extended QA Cycle for 2.5<br />Formal Beta and Release Candidates<br />Final 2.5.0 release in March instead of November<br />Introduction of Maintenance Releases<br />Currently on Sakai 2.5.4, the most reliable version of Sakai to date<br />Challenge: Managing 2.5 and 2.6 releases simultaneously<br />Not to mention 3.0<br />
  7. 7. UX Improvement<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 />Currently the Foundation is working towards 3.0<br />Some design work can be implemented for 2.7, but we need resources willing to do this<br />Overall Result<br />Positive change in direction<br />Won’t be satisfied until changes reach release<br />
  8. 8. Sakai 3<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 />8<br />
  9. 9. Design Result<br />
  10. 10. Sakai 3: What<br />A set of R&D projects that will form the foundation of Sakai 3<br />A series of preview releases starting later this year<br />No defined date for Sakai 3.0<br />
  11. 11. Sakai foundation 2009<br />
  12. 12. Current 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 />
  13. 13. Sakai Goals<br />Adoption<br />Broad & Diverse (significant adoption by different types of organizations)<br />The top choice for innovators<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. Community Wants<br />Clear product vision & direction<br />More communication from Foundation<br />Roadmap that allows campus advocates to effectively communicate with stakeholders<br />Project structure that attracts sufficient resources and uses them effectively<br />More input from functional experts & designers<br />Allow diverse types participation<br />Large and small, Formal and informal, Institutional and individual<br />
  15. 15. Product Life Cycle<br />
  16. 16. Community<br />Major Product Changes<br /><ul><li> Generate new ideas
  17. 17. Try new technologies
  18. 18. Prove desirability
  19. 19. Create dev team/plan
  20. 20. Reduce dev risks</li></ul>Product Council<br /><ul><li> Finish building
  21. 21. Test
  22. 22. Document</li></li></ul><li>Product Development<br />Structuring of work in this phase is key<br />Projects probably need<br />Project management<br />Project schedule and plan<br />Functional leadership<br />UX (including accessibility and i18n)<br />Multiple organizations involved<br />Exceptions possible<br />K2 using Apache-style management successfully<br />Key: Ability to predictably deliver quality product<br />
  23. 23. 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 />
  24. 24. Product Council<br /><ul><li>Nate Angell (rSmart)
  25. 25. Noah Botimer (Michigan)
  26. 26. Eli Cochran (Berkeley)
  27. 27. Michael Feldstein (Oracle)
  28. 28. Clay Fenlason (Georgia Tech & Sakai)
  29. 29. David Goodrum (Indiana)
  30. 30. John Lewis (Unicon)
  31. 31. Stephen Marquard (Cape Town)
  32. 32. John Norman (Cambridge)
  33. 33. Max Whitney (NYU)</li></li></ul><li>Membership and adoption<br />
  34. 34. July 2009<br />10th Sakai Conference - Boston, MA, U.S.A.<br />21<br />New Foundation Members<br />
  35. 35. Membership<br />Steady overall<br />Expiration of original 3-year SEPP commitment<br />Some institutions are not renewing<br />Introduction of 3-year discounted membership<br />20% for a 3 year commitment with up front payment<br />Membership will be driven by adoption<br />And effectiveness in coordinating community<br />
  36. 36. 23<br />What Adoption Numbers?<br />Moodle statistics are often referenced<br />These aren’t right for us. <br />Number of Courses/Installation, ~ 40<br />Number of Users/Installation, ~ 400<br />33% Higher Education, 12% Commercial<br />23<br />
  37. 37. 24<br />Sakai Adoption Metrics<br />Total enrollment of Higher Ed institutions that have adopted Sakai as their primary CLE<br />24<br />
  38. 38. US Adoption<br /><ul><li>Large research institutions who have (or will have) Sakai as their primary CMS account for ~22% of total enrollments (up from 16% as of Paris)</li></li></ul><li>Overall US Adoption<br />Overall, US institutions who have adopted Sakai have total enrollment of 949,000.<br />Up from 832,000 at Paris (12% increase)<br />In Thousands<br />
  39. 39. Adopting 2 or 3?<br />Generally, the answer is 2.6 or 2.7<br />It works well today<br />3 doesn’t exist yet<br />The best path to 3 will be through 2<br />Bb/WebCT migration to 3 is undefined<br />Bb/WebCT migration to 2 is well known<br />Many will be migrating from Sakai 2 to 3<br />Exceptions<br />You don’t have a CMS or you are using something like Sharepoint<br />Your adoption timeline is 2012 or later<br />
  40. 40. Finances and budget<br />
  41. 41. Finances<br />Healthy: $890K of current assets<br />Current Cash Balance of almost $500K<br />A/R of almost $400K<br />But<br />Conference expenses haven’t come in yet<br />Much of this reserved for future years (3-year memberships)<br />Expect to collect/spend approximately $900k this year<br />
  42. 42. Spending Goals<br />Less spending on conferences<br />Net of $300k two years ago<br />Net of $60k (estimated) this year<br />More spending on product development<br />QA, UX, Release management<br />More spending on communications<br />Internal and external (outreach)<br />
  43. 43. Other Topics<br />
  44. 44. Conferences<br />Single Global Conference<br />Late June, Early July every year<br />Regional Conferences (since Paris)<br />Stockholm, Virginia Tech, Australia, Japan<br />Development Meetings<br />Next one?<br />
  45. 45. By-Law Changes<br />Remove requirement to have board approve conference chair and committee<br />If they want to they can do so. But it shouldn’t be required in the by-laws.<br />Allow up to 2 external board members<br />To bring perspective we might not get via elections process (financial, legal)<br />Approved by 2/3 of elected board<br />Members must approve this change<br />