1. Participating in SAKAI 3
MICHAEL KORCUSKA
Executive Director, Sakai Foundation

2. Participate
Four ways:
Join
Create
Document
Donate

3. Dilemma
• Detailed planning depends on resources
• Resource commitments depend on plan
• So
• We have a high-level plan
• And a series of defined release milestones
• The particular features/functions available in
a milestone are dependent on you

4. Timelines
2009 2010 2011 2012 2013
Sakai 2.5
Sakai 2.6
Sakai 2.7
Hybrid
Mode
Sakai 3.0
Previews Official Releases
Sakai 2.8?
4

5. Sakai 3 Pre-releases
• See “Sakai 3 Projects”
• http://spreadsheets.google.com/pub?key=pEMA9wYYLbeuEPe7RD3vncg&hl=
• Milestone 1
• Simple project sites and basic networking
• Milestone 2
• Basic courses
• Milestone 3
• Full Sakai functionality, not all “native” Sakai 3
• Data migration tools
• Milestone 4
• Full functional replacement for Sakai 2.x
5

6. Join an existing Project
• K2: The kernel for Sakai 3
• Leadership from Cambridge
• Contributions from
• Georgia Tech, UC Davis, UC Berkeley, Sakai Foundation, Charles Sturt
• http://groups.google.com/group/sakai-kernel
• 3akai: The foundational UX
• Participation from Sakai Foundation, Georgia Tech &
Cambridge
• http://confluence.sakaiproject.org/confluence/display/3AK
6

7. Join an existing Project
• Group Management
• Coherent, flexible user and group management
• UC Davis and UC Berkeley (and you?)
• http://confluence.sakaiproject.org/confluence/x/FIJDAw
• Library Integration
• Requirements discussion
• http://confluence.sakaiproject.org/confluence/x/04EvA

8. Create a new project
Many areas of functionality need to be addressed,
starting with requirements and design
• Discussion forums & chat • System integration (including
rooms IMS LIS and LTI)
• Assignment, feedback and • User Help and
reporting Documentation
• Tests & Quizzes • Internationalization and
• Portfolios Localization
• Administration & reporting • Data Migration – from 2.x to
3.0
• Site Archive, Delete, Import,
Export (including Common • Widget development – small
Cartridge & SCORM) bit of functionality, suitable for
individual contributor

9. Document
• Requirements-driven development
• Depends on requirements
• Document your campus needs for an
existing project
• Or even for one that hasn’t started yet
• Can be institutional or individual
• User Stories/Use Cases are the best way to
start

10. Donate
• Sakai Foundation starting a fund for
Sakai 3
• Funds will go to:
• Direct design and development
• Developer documentation & training
• Working meeting expenses

11. Getting Started
• Communicate on Sakai-dev or Sakai-ux
• Q4 Working meetings
• Dates & locations depending on participants
• Unsure what to do?
• Email Clay Fenlason (clay.fenlason@et.gatech.edu) or myself
(mkorcuska@sakaifoundation.org)

12. Reminder
• This is a community project
• It won’t happen without you
• Enlightened self-interest
• Your participation now will pay huge dividends
• A system that meets your needs with less
customization
http://confluence.sakaiproject.org/confluence/display/MGT/Sakai+3+Participation

13. THANK YOU!
13