1. Sakai Overview http://www.sakaiproject.orghttp://www.sakaiproject.org/ Sakai Conference: June 12-14, 2007 Amsterdam, NL

2. Sakai in one Slide.... Collaboration, Teaching, and Learning FOSS - 100% free to use, modify and contribute Sakai is 3 years old Non-profit Sakai Foundation January 2006 Financial support from 100+ Higher Education, 15 companies Six paid staff members 100+ people developing and testing Sakai releases Nifty Web site www.sakaiproject.org ■ Sakai Community Google Map Mashup ■ Very cool “Sakai Overview” (10 minutes) Overview Video: http://www.dr-chuck.com/media.php?id=64http://www.dr-chuck.com/media.php?id=64

3. The Sakai Foundation Supporting and coordinating the work of the Sakai Community.

4. Mission Statement 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.

5. Sakai Foundation Structure Executive Director Community Communication Requirements Process Software Coordination Conference Training Finance Membership Legal/License Marketing Connecting End Users with Developers Board of Directors Bug Tracking Release Mgt Documentation QA Architecture

6. U of X J, Inc U of C U of B U of Y U of Z Development Structure Sakai Foundation Sakai staff Sakai Paid Staff Sakai Volunteers All of the Sakai developers, designers, and QA are working for Sakai as volunteers. K, Inc

7. Sakai (product) Project Coordination to Produce a Release Framework Release Schedule Web Services Samigo rWiki Committer Project Provisional Project O.S.P. Release Blog Release Foundation Staff Contributed Project

8. Sakai Release Timeline - Two Releases per Year Release 0 -2QA Begins Coordination Meeting -5 -10 Requirements Prioritization Maintenance “ends” +12 Community Maintenance ?? Kicking off 2.5 2.4 December 2006 2.4 March 2007 2.4 May 2007 2-2-x, 2-3-x 2-1-x Months

9. Requirements Process Requirements is how the user needs are communicated across the community Mark Norton is Requirements Coordinator Continuous Requirements Gathering - JIRA ■ Gathering and entering feature requests ■ Users, Developers, Technical Supoprt Staff Formal requirements process runs once for each major release Open requirements “roll over” from one phase to the next Guided process to review, understand, document and prioritize requests into “requirements” High level “directions” document produced to give community summary information.

10. Sakai Requirements (Sample) REQ-282 Users should have more information and control over site import REQ-26 Emails 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 Email 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

11. Community Requirement Summary for 2.4 1. Assessment 2. Migration 3. Portfolio 4. Course Management 5. Statistics and Collection 6. Grade book and Grading Service 7. User Interaction 8. Support SQL Server 9. Resource Tool Improvements 10. Mail Tool Improvements 11. SCORM

12. http://issues.sakaiproject.org/confluence/x/f3

13. 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 Project Management Meetings ■ June 9, 2007 - Amsterdam Coordination Video: http://www.dr-chuck.com/media.php?id=76http://www.dr-chuck.com/media.php?id=76

15. Quality Assurance Megan May is QA Director ■ Coordinates 60+ QA Volunteers - often technical support staff at adopting institutions ■ Full QA of major (2/yr) and minor releases (4/yr) Reports to the Sakai Community and Board for each release 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 Integration Video: http://www.dr-chuck.com/media.php?id=57http://www.dr-chuck.com/media.php?id=57

16. Community Communication Anthony Whyte is Community Liason ■ Foundation questions ■ RFQ Help ■ Security Officer Mary Miles - Membership Coordination Web / Communication Team ■ Susan Hardin ■ Margaret Wagner Commnuity Video: http://www.dr-chuck.com/media.php?id=74http://www.dr-chuck.com/media.php?id=74

17. Security Procedures Security bugs reported directly to security officer Non-public Process (usually six weeks) ■ Threat/priority assessed ■ Security JIRA filed ■ Patch developed and QA ■ Patch distributed to known sites Public Process ■ Announcement of the *existence* of a bug ■ Distribute patch to newly discovered sites ■ Informal polling of patch deployment ■ Check into source tree ■ Maintenance release

18. Membership in Sakai Foundation Costs ■ $10K per year for Companies ■ $10K per year for large Universities ($5K for small Universities) Benefits ■ Support and increase the Foundation provided services ■ Training Director ■ Internationalization Coordinator ■ Support the Sakai Foundation Fellows selected from volunteers ■ Vote for the Sakai Foundation Board of Directors ■ Prioritize Requirements ■ Member-private commnuication channel for sensitive information and Security issues

19. Sakai: More Information Main site: www.sakaiproject.org ■ Bugs: bugs.sakaiproject.org Sakai-wide collaboration area ■ collab.sakaiproject.org ■ sakai-dev@sakaiproject.org ■ sakai-user@sakaiproject.org sakai-user@sakaiproject.org Sakai Conference: June 12-14, 2007 Amsterdam, NL Sakai Workshop: Educause Australia April 29 - May 2 Melbourne, AU Sakai Track at JA-Sig Conference June 24-27, Denver Text http://www.flickr.com/photos/tags/whereIsSakai/