Sakai Overview http www sakaiproject org Sakai Conference

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

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=64

The Sakai Product A Collaboration and Learning Environment

What’s in a name? Sakai is named after Hiroyuki Sakai of the Food Channel Television program “Iron Chef”. Hiroyuki is renowned for his fusion of French and Japanese cuisine.

What’s in a name? Perhaps a better name for this open source project would be Sikai, making use of the Chinese characters “Think Open” Sakai was born in 2004 - the year of the Monkey.

Placing the Sakai Product A Collaboration and Learning Environment Teaching and Learning Collaboration / Groupware Portfolio Video: http: //www. dr-chuck. com/media. php? id=73

Sakai can be used for many applications (at the same time on the same servers) Teaching and Learning Distance Education Community systems Small group Collaboration Portfolios e. Science Sakai has a very flexible role system so that Sakai “looks” right for each of the uses.

Announcements News/RSS Blog (*) Podcasting Calendar Poll (*) Drop Box Portlets Email Archive Preferences Resources Presentation Chat Room Profile / Roster Forums Sakai. Brary Threaded Discussion Schedule Link Tool Search Mail. Tool Transformable Message Center Web. DAV i. Tunes. U Wiki (*) indicates tool is provisional for release 2. 4 Sakai 2. 4 Generic Tools

Sakai 2. 4 Teaching and Portfolio Teaching Tools Portfolio Tools Assignments Forms (*) Gradebook Evaluations (*) IMS Common Cartridge Glossary (*) Module Editor Matrices (*) QTI Authoring (*) Layouts (*) QTI Assessment (*) Templates (*) Section Management Reports (*) Syllabus Wizards (*) Postem (*) indicates tool is provisional for release 2. 4

Contributed Area • Collaboration ■ JForum ■ Image Gallery ■ Image Quiz ■ Site Statistics Tracking ■ Agora Real-Time Conferencing ■ Open Courseware Export ■ JSR-170 Repository ■ Evaluation System ■ Guan. Xi / Shibboleth • Teaching and Learning ■ SCORM Support Contributed -> Provisional -> Full Release

Comparing Features - www. edutools. org Teaching Video: http: //www. dr-chuck. com/media. php? id=65

Sakai in Production Text 20+ Full scale installations

http: //www. sakaiproject. org/sakai-map/

Sakai in Production Text

Sakai in Production Text

Sakai in Production Text 3014 - Winter 07 class sites 16145 - Total class sites to date 11155 - Total project sites 1232 - Grad. Tools student sites 86972 - My Workspaces to date

The Sakai Community A group of people around the world working to build and share a common Collaboration and Learning Environment using a Community Source approach.

Why Join Sakai? - I can write it myself Uploading Files Flexible Roles Chat Discussion Gradebook Testing

Why Pick Sakai? - Actually not so simple Uploading Files i. Tunes U i. Cal Export Flexible Roles Publisher Data Import Cal. Dav Support Chat Lecture Recording Collaborative Writing Discussion Students SMS integration Gradebook E-Portfolio Data Mining Testing Students attending multiple Knowledge Management schools Net. Vibes / Pageflakes Federated Authentication Google Scholar SCORM 1. 2 SCORM 2004 Shibboleth Guan Xi Open Course. Ware Integration Outsourcing hosting Off Line data access Web. Dav PDA Integration RSS Feeds Web Services

Sakai Foundation non-Profit Members Albany Medical College Monash University of California, Los Angeles Arizona State University Nagoya University of California, Merced Australian National University New York University of California, Santa Barbara Boston University School of Management Northeastern University of Cambridge, CARET Brown University North-West University (SA) University of Cape Town, SA Carleton College Northwestern University of Colorado at Boulder Carnegie Foundation for Advancement of Teaching Ohio Learning Network University of Delaware Carnegie Mellon University Ohio State University of Hawaii Ceritos Community College Princeton University of Hull Coast Community College District Rice University of Illinois at Urbana-Champaign Columbia University Ringling School of Art and Design University of Melbourne Cornell University Roskilde University (Denmark) University of Michigan Dartmouth College Rutgers University of Minnesota Florida Community College at Jacksonville Simon Fraser University of Missouri Foothill-De Anza Community College Stanford University of Nebraska Franklin University State University of New York University of North Texas Georgetown University Stockholm University of Oklahoma Harvard University SURF/University of Amsterdam University of South Africa (UNISA) Hosei University IT Research Center Syracuse University of Texas at Austin Indiana University Texas State University - San Marcos University of Toronto, KMDI Johns Hopkins University Tufts University of Virginia Lancaster University Universidad Politecnica de Valencia (Spain) University of Washington Loyola University, Chicago Universitat de Lleida (Spain) University of Wisconsin, Madison Lubeck University of Applied Sciences University College Dublin Virginia Polytechnic Institute/University Maricopa County Community College University of Auckland Whitman College Marist College University of California, Office of the Chancellor Yale University MIT University of California Berkeley University of California, Davis

Sakai Community Metrics from ohloh. net • 800, 00 Lines of Code • Core Sakai ■ $11 million dolars of investment ■ 42 Volunteer Developers • Contrib ■ ■ 38 Volunteer Developers $7. 7 million dollars of investment Developer Video: http: //www. dr-chuck. com/media. php? id=53

Sakai Commercial Affiliates

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

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.

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

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

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

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

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.

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-159 Graphical content in rich text editor • REQ-375 Timed Release of documents/files in Resources tool • • • REQ-109 Search across site and sites REQ-173 Chat should allow users to search for messages from a particular user REQ-65 Email Archive should be deeplinkable/bookmarkable REQ-124 Add SCORM Player to Sakai REQ-129 Support for Learning Design and other Work Flow Engines

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 1. Resource Tool Improvements 2. Mail Tool Improvements 3. SCORM

http: //issues. sakaiproject. org/confluence/x/f 3

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=76

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=57

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=74

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 ■

Membership in Sakai Foundation • Costs ■ $10 K per year for Companies ■ $10 K per year for large Universities ($5 K 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

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