Sakai Overview

1
Sakai Overview
Sakai Conference June 12-14, 2007 Amsterdam, NL

• http//www.sakaiproject.org/

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?
id64
3
The Sakai ProductA Collaboration and Learning
Environment
4
Whats 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.

5
Whats 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.
6
Placing the Sakai Product

• A Collaboration and Learning Environment

Teaching and Learning
Collaboration / Groupware
Portfolio Video http//www.dr-chuck.com/media.php
?id73
7
Sakai can be used for many applications

• (at the same time on the same servers)

Distance Education
Small group Collaboration
Teaching and Learning
Community systems
Portfolios
eScience
eScience
Sakai has a very flexible role system so that
Sakai looks right for each of the uses.
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
Sakai 2.4 Generic Tools
News/RSS Podcasting Poll () Portlets Preferences
Presentation Profile / Roster SakaiBrary Schedule
Search Transformable WebDAV Wiki
Announcements Blog () Calendar Drop Box Email
Archive Resources Chat Room Forums Threaded
Discussion Link Tool MailTool Message
Center iTunesU
() indicates tool is provisional for release 2.4
12
Sakai 2.4 Teaching and Portfolio
Teaching Tools Assignments Gradebook IMS Common
Cartridge Module Editor QTI Authoring () QTI
Assessment () Section Management Syllabus Post
em
Portfolio Tools Forms () Evaluations
() Glossary () Matrices () Layouts
() Templates () Reports () Wizards ()
() indicates tool is provisional for release 2.4
13
Contributed Area

• Collaboration
• JForum
• Image Gallery
• Image Quiz
• Site Statistics Tracking
• Agora Real-Time Conferencing
• Open Courseware Export
• JSR-170 Repository
• Evaluation System
• GuanXi / Shibboleth
• Teaching and Learning
• SCORM Support

Contributed -gt Provisional -gt Full Release
14
Comparing Features - www.edutools.org
Teaching Video http//www.dr-chuck.com/media.php?
id65
15
Sakai in Production
Text
20 Full scale installations
16
(No Transcript)
17
http//www.sakaiproject.org/sakai-map/
18
Sakai in Production
Text
19
Sakai in Production
Text
20
Sakai in Production
Text
 3014 - Winter 07 class sites 16145 - Total class
sites to date 11155 - Total project sites  1232 -
GradTools student sites 86972 - My Workspaces to
date
21
The Sakai CommunityA group of people around the
world working to build and share a common
Collaboration and Learning Environment using a
Community Source approach.
22
Why Join Sakai? - I can write it myself
Uploading Files Flexible Roles Chat Discussion Gra
debook Testing
23
Why Pick Sakai? - Actually not so simple
iTunes U Publisher Data Import Lecture
Recording Students E-Portfolio Students attending
multiple schools Shibboleth Guan Xi Outsourcing
hosting WebDav RSS Feeds
iCal Export CalDav Support Collaborative
Writing SMS integration Data Mining Knowledge
Management NetVibes / Pageflakes Open CourseWare
Integration Off Line data access PDA
Integration Web Services
Uploading Files Flexible Roles Chat Discussion Gra
debook Testing Federated Authentication Google
Scholar SCORM 1.2 SCORM 2004
24
Sakai Foundation non-Profit Members
25
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
?id53
26
Sakai Commercial Affiliates
27
(No Transcript)
28
The Sakai FoundationSupporting and coordinating
the work of the Sakai Community.
29
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.

30
SakaiFoundation Structure
Executive Director
Board of Directors
Community Communication
Software Coordination
Requirements Process
Conference Training Finance Membership Legal/Licen
se Marketing
Connecting End Users with Developers
Bug Tracking Release Mgt Documentation QA Architec
ture
31
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.
32
Project Coordination to Produce a Release
Sakai (product)
Framework
Samigo
Web Services
Release
Schedule
rWiki
Committer
O.S.P.
Blog
Foundation Staff
Release
Release
Project
Provisional Project
Contributed Project
33
Sakai Release Timeline - Two Releases per Year
Months
Requirements Prioritization
Kicking off 2.5
-10
2.4 December 2006
Coordination Meeting
-5
2.4 March 2007
-2
QA Begins
0
2.4 May 2007
Release
Maintenance ends
2-2-x, 2-3-x
12
2-1-x
Community Maintenance
??
34
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.

35
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/bookm
  arkable
• 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

36
Community Requirement 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

37
http//issues.sakaiproject.org/confluence/x/f3
38
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?id76
39
(No Transcript)
40
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.p
hp?id57
41
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
?id74
42
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

43
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

44
Sakai More Information

• Main site www.sakaiproject.org
• Bugs bugs.sakaiproject.org
• Sakai-wide collaboration area
• collab.sakaiproject.org
• sakai-dev_at_sakaiproject.org
• sakai-user_at_sakaiproject.org

Sakai Conference June 12-14, 2007 Amsterdam, NL
Sakai Workshop Educause Australia April 29 -
May 2 Melbourne, AU
Text
Sakai Track at JA-Sig Conference June 27-27,
Denver
http//www.flickr.com/photos/tags/whereIsSakai/