Help Keep the Roadmap Up-To-Date!
If you have updated planning information to share, comment on this page. Thanks.
The most current release is Sakai 2.6.0, which was released on July 23, 2009. See the announcement at the announcements maillist archive. The first maintenance release for 2.6 (which will be 2.6.1, natch) should be available in the second half of September
Release management planning for 2.7 is underway. The set of new features expected to be in 2.7 are now being reviewed in Release Team meetings: Proposed Sakai 2.7 Changes
Research and Development work for a new generation of the product, Sakai 3, is fairly well along. This work so far includes a new kernel (called K2) based on Apache Sling and a new UX framework that grew out of the UX initiative. Cambridge and Georgia Tech expect to be able to deploy the earliest milestone of this work to their campuses near the end of 2009, though it will not at that point be ready for a full Sakai release.
See below for more details.
The broader goals for 2.7 are:
1) A simple, measured introduction to a new set of product development processes
- Provide the new Product Council space and time to work with development teams around significant new functionality
- Avoid unnecessary disruption to the momentum of development work to date
2) A reliable, published release roadmap
- A clear plan before QA begins
- A plan designed around meeting the broadest user needs with the highest quality code while minimizing risk to target timelines
Sakai 2.7 is expected to be released in April 2010.
Sakai 2.6 separated out key back-end services into an independent kernel, termed 'K1.' The aim was to provide a more stable, better organized framework against which to build tools, and to allow the framework and tools to evolve on separate time-scales from functional releases.
The goals for the Kernel 1.0.x series are:
- Bug-fixing in support of Sakai 2.6.x through early 2011.
- Kernel 1.0.0 Jira Roadmap
- Kernel 1.0.x Jira Roadmap
- Kernel 1.0.1 Jira Roadmap
The goals for the Kernel 1.1.x series are:
- Bug-fixing and minor improvements in support of the Sakai 2.7 series through early 2012.
- Ability to cluster-enable Sakai to support session fail-over using Terracotta ( - SAK-13324Getting issue details... STATUS )
- Kernel 1.1.0 Jira Roadmap
This area (below) needs revision
Sakai 3 represents a rewrite of the Sakai framework, both technically and as a matter of design. Its first set of designs came out of the UX initiative, its early development is being led by Cambridge with support from Georgia Tech. Early deliverables are focused on simple support of the most generic collaboration needs, as informed by production needs at Cambridge and Georgia Tech, but the scope is expected to expand as other institutions become more deeply involved.
There are currently three distinct projects going toward Sakai 3:
- K2: a new set of core services at the back end (K2 stands for "Kernel 2").
- 3akai: a new UX framework; an HTML and JS front-end which implements the new designs in an accessible way.
- Groups: a design-led effort focused on the full variety of ways in which groups are used in academic settings and how Sakai can be used to organize one's experience of them.
Cambridge and Georgia Tech expect to have the first Sakai 3 code available for production by the end of 2009. In this early instance it will not offer a full replacement of Sakai course functionality, but will instead aim to provide a UX framework which will wrap around a legacy Sakai installation.
Production Milestone 1 (end of 2009)
The goal of this first production milestone is to establish a new UX framework for Sakai, and begin to offer new capabilities for sharing content, authoring pages with embedded functionality, and setting up simple networks of contacts on the system. The latest state of the development work can be experienced directly at [ ](a development server, so you'll have to pardon us if stability is less than perfect). A breakdown of the various capabilities is laid out below:
A personalizable landing point for the entire system, showing the individual comprehensive views of the content, people and activities that matter to them. Widgets can be added, removed, and rearranged. Since K2 will include Shindig, an OpenSocial Container, other OpenSocial gadgets may be included, but the following Sakai widgets will be available by default:
- My Courses/Sites
- File Management
- My Profile
- My Contacts
- Poll Tracker
- Private Messaging
- Online Connections (w/ synchronous chat)
A flexible profile will be available for the user to communicate important information about themselves to others. In addition to basic information, other details may be optionally offered: degrees, publications, academic interests, talks, professional experience, etc.
Contacts (Social Networking)
Users may invite others on the system to join their list of "contacts," a circle of acquaintances with facilitated communication, profile viewing, and content sharing.
File Sharing and Management
The ability to view and share files outside the course or workspace context. All the files one has access to on the system, including private files and those uploaded into particular workspaces, will be available from a single location.
Workspaces (or "sites") may be created with ad hoc membership, assigned a simple and readable URL, and easily made publicly available where desired. Workspace navigation, appearance, toolset, and page organization may also be freely customized.
Page Authoring and Assembly
Pages may be authored in a WYSIWYG environment with full versioning, history, and edit permissions: like wiki pages, but without the markup. This will include embeddable widgets which may be placed in the page and interacted with there in context.
The initial list of embeddable widgets will include:
- Discussion Threads
- Dropbox (submitting files for feedback)
- RSS feed
Pages may also be saved as templates, for future reuse and sharing.
Production Milestone 2 (July 2010)
A second production milestone will bring in more robust support for courses, building on the generic capabilities of Milestone 1, though again the focus will be on the more simple and versatile capabilities and not the most sophisticated and specialized course functionality.
Milestone 1 functionality should be extended in the following ways:
- The ability to post tasks for completion, and provide feedback for submitted work (i.e. simple homework use cases)
- The ability to divide students into groups for team-based projects
- The ability for an instructor to view appropriate profile information about the students in their course
- A structured course site model which affords:
- site templating for reuse
- course presentation and organization to be scaffolded on interleaved templates provided by the institution, department or templates saved from prior courses or colleagues
- syllabus presentation of site structure
- import/export following common cartridge standards
- a browsable course catalog
Most of the information on Kernel 2.x can currently be found here.
The goals for the Kernel 2.x series are:
The Sakai 3.x series will eventually switch from being based on Kernel 1 to Kernel 2 in early- to mid- 2009. Sakai 2.x will not make use of Kernel 2 services, and will remain base on Kernel 1 services; however, much of the functionality of Sakai 2.x will initially be made available in Sakai 3.x through a compatibility approach.