DEC 6, 2006 Sakai Foundation Status Report Charles Severance December 6, 2006

DEC 6, 2006 Sakai Foundation Non profit formed October 2005 Open election for three seats December 2005 Executive Director Chosen June 2005 Open election for three seats December 2006 Two worldwide conferences / year regional conferences per year Slow, steady membership growth new members per month

DEC 6, 2006 Membership Levels Over Time

DEC 6, 2006 Transition Progress

DEC 6, 2006 Commits

DEC 6, 2006 ED Activities Since June Overview Video Two Pager Sakai-Map Visit with peers organization SIFA, IMS, Kuali, JA Sig

DEC 6, 2006

The Ecology of Sakai

DEC 6, 2006 Mission Statement (straw) The mission of the Sakai Foundation is to hold ownership of the Sakai software and to guide and nurture the community of activity around the Sakai software. The Sakai Foundation seeks to as to maximize the positive impact of the Sakai software, technology, and community on teaching and research.

DEC 6, 2006 Objectives (straw) Release High Quality Software Clearly communicate with the public and members about Sakai. Work to maintain a healthy, committed, and diverse community around Sakai Improve the global adoption of Sakai across teaching, research, and other collaborative applications. Work with other organizations to improve the overall state of collaboration and teaching and learning. Work to bring the different stake-holders of Sakai

DEC 6, 2006 Guiding Principles Meritocracy Coalition of the Willing Distributed Decision Making Local Priorities lead to Global Efficiency - "scratching an itch" Public Discourse - E- Mail preferred Community Involvement Flat Hierarchy - Peers - mutual respect The lack of Power Structures in Sakai - Rough Consensus - then move forward Destiny determined by those most affected Essential Core - The engine that drives the Sakai Foundation and the Sakai Software is the organizations. Validate direction through the adopters

DEC 6, 2006 Stakeholder Adopting organizations CIOs Developers - IT professional and independent Teaching and Learning Professionals Teachers Students Collaborative users Companies who utilize Sakai Technology Companies with "competitive products"

DEC 6, 2006 Overall Structure Foundation Community Communication Requirements Process Software Coordination Conference Training Finance Membership Legal/License Marketing End users Community Board Bug Tracking Release Mgt Documentation QA Architecture

DEC 6, 2006 Timeline Release 0 -2Code Freeze Coordination Meeting Requirements Prioritization Maintenance “ends” +12 Community Maintenance ?? Kicking off Meeting here in Atlanta 2.4 March May x, 2-3-x 2-1-x

DEC 6, 2006 Requirements Process Mark Norton is Requirements Coordinator Used to collect requirements across the community Process runs once for each major release Requirements “roll over” from one phase to the next Continuous gathering of feature requests Guided process to review, understand, document and prioritize requests into “requirements” High level “directions” document produced to give community summary information.

DEC 6, 2006 Sakai Requirements (Sample) REQ-282 Users should have more information and control over site import REQ-26 s Should Contain Site URL and Item URL REQ-173 Chat should allow users to search for messages from a particular user REQ-159 Graphical content in rich text editor REQ-65 Archive should be deep-linkable/bookmarkable REQ-375 Timed Release of documents/files in Resources tool REQ-109 Search across site and sites REQ-124 Add SCORM Player to Sakai REQ-129 Support for Learning Design and other Work Flow Engines

DEC 6, 2006 Initial Community Priorities Summary for 2.4 Assessment Migration Portfolio Course Management Statistics and Collection Grade book and Grading Service User Interaction Support SQL Server Resource Tool Improvements Mail Tool Improvements SCORM This is input for a requirements planning session in Atlanta. We decided that we wanted a succinct requirements report in addition to a long list of requirements.

Requirements Page

DEC 6, 2006 Project Coordination Peter Knoop is Project Coordinator –Charged with communicating and tracking progress on bugs and requirements Tracking and communicating amongst volunteer developers –29 Discussion and Working Groups –89 Teams - Full Release –10 Teams - Provisional –18 Teams - Contrib First ever - Project Management Meeting - December 8, 9 - Atlanta

DEC 6, 2006 Quality Assurance Megan May is QA Director Facilitates community resources around Sakai’s QA Significant transition in Sakai QA approach since 2.0 –QA drives release process and makes the final call –Significantly broadens community involvement in release in general

DEC 6, 2006

Community Communication Anthony Whyte is Community Liason –Foundation questions –RFQ Help –Security Officer Mary Miles - Membership Coordination Web / Communication Team –Susan Hardin –Margaret Wagner

DEC 6, 2006 Security Procedures Completely non-transparent process Security bugs reported directly to security officer Threat/priority assessed Security JIRA filed Patch developed and QA Patch distributed to known sites Public announcement of the *existence* of a bug Informal polling of patch deployment Check into source tree Maintenance release

DEC 6, 2006 Sakai Web Site Kicking off redesign effort –Information Architecture Approach –Who visits our site and what are they looking for –Getting them to the information they need as directly as possible Make sources of information more seamlessly integrated –www / collab / bugs / confluence –Document library BOF

DEC 6, 2006 Sakai Roadmap Document Recent discussions with members identify communication as a problem –Too much communication :) –Need high level summary periodically that “cuts through the clutter” A series of high level documents will be produced to make Sakai more accessible –Sessions need to become documents BOF

DEC 6, 2006 Who is Sakai?

DEC 6, 2006 At a Glance 6343 accounts in collab.sakaiproject.org 1491 accounts in bugs.sakaiproject.org 116 developers 43 Users involved in QA (2.3.0) 25 volunteers in project-wide roles 9 paid staff - 4 full time

DEC 6, 2006 Sakai Developers DISTRIBUTED DEVELOPMENT TEAM AFFILIATION Higher Ed = 102 (87.93%) Commercial = 13 (11.21%) Non-profit = 1 (0.86%) LOCATION USA = 93 UK = 10 South Africa = 6 Netherlands = 4 Spain = 1 Portugal = 1 Canada = 1 TOTAL = 116

DEC 6, 2006 Sakai QA Team INSTITUTIONAL SUPPORT FOR SAKAI TYPE Academic = 16 Commercial = 1 LOCATION USA = 12 UK = 2 South Africa = 1 Netherlands = 1 Portugal = 1 TOTAL = 17 VOLUNTEERS = 43

DEC 6, 2006 Coordination Provided Staff Lon Raley - Finance - Michigan - 50% Megan May - QA - Indiana - 50% Pam Dietz - Finance/Support - Michigan - 50% Kathy Riester - Conference/Support - Michigan - 30% Aaron Zeckowski - Training - VA Tech - 40% Tony Atkins - Server Support - VA Tech - 20% Duffy Gilman - Server Support - Univ. Arizona - 20% Margaret Wagner - Newsletter/Web - Michigan - 20%

DEC 6, 2006 Coordination Paid Staff Charles Severance - Executive Director - 100% Mary Miles - Membership Coordinator - 100% Anthony Whyte - Community Liaison - 100% Peter Knoop - Project Coordinator - 80% Megan May - QA Director - 50% Brigid Cassidy - Conference Coordinator - 40 % Mark Norton - Requirements Coordinator - 15% Susan Hardin - Web Master - 25%

DEC 6, 2006 Board Member Volunteers Chris Coppola - rSmart - Licensing - 15% Joseph Hardin - Michigan - Conference/Patent/Legal - 35% Brad Wheeler - Indiana - Licensing/Legal - 10% Mara Hancock - Berkeley - Requirements - 15%

DEC 6, 2006 Sakai Foundation Core Dev Glenn Golden - Michigan - 80% Ian Boston - Cambridge - 80% Antranig Basman - Cambridge - 80% Lance Speelmon - Release Manger - Indiana - 30% Andrew Poland - Server Support - Indiana - 40% Jim Eng - Michigan - 50% Beth Kirschner - Michigan - 30% Gonzalo Silverio - Michigan - 30% Josh Holzman - Berkeley - 30% Clay Fenleson - Boston University - 20% Zach Thomas - Texas State - 20% Joshua Ryan - Arizona State - 10%

DEC 6, 2006 Foundation Finances

DEC 6, 2006 Short Form Foundation has money in the bank from the project phase - 500K Cash flow is neutral to slight negative with the addition of ED Salary and travel Critical element - renewal rate - modeling 95/90/80

DEC 6, 2006 Revenue and Expense Project Phase: results partial through September

DEC 6, YTD Revenue Breakdown

DEC 6, YTD Expense Breakdown

DEC 6, 2006 Monthly Breakdown

DEC 6, 2006 Conference Attendance

DEC 6, 2006 Conference Revenue and Expenses

DEC 6, 2006 Per Attendee Conference Costs

DEC 6, 2006 Vancouver Expense Breakdown $235,952.18

DEC 6, 2006 Austin Expense Breakdown $ 92,388.01

DEC 6, 2006 Institutional Attendees

DEC 6, 2006 Institutional Attendees Should we Limit Registrations? Limit = 3 -> $39,105 / conf Limit = 5 -> $24,095 / conf 35

DEC 6, 2006 Rough Projections We are moving forward with purpose –Hired ED / Fellows Program / Cleaning up MOUs for services –We expect moderate continued growth in revenue We have 500K in the bank to backstop short- term ebbs and flows “Worst” case for 2007 $150K Going to work on doing better than the worst case

DEC 6, 2006 Summary Financially solid - thanks to project funding carryover Need to get used to “steady state” and maintain reserve Major structures and processes are in place and functioning - need iterative improvement Transition to a nice, clean well-defined foundation is well underway - firefighting slows the transition down