Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 270 Next »

Help Keep the Roadmap Up-To-Date!

If you have updated planning information to share, comment on this page. Thanks.

Sakai Roadmap

The most current release is Sakai 2.6.0, which was released on July 23, 2009. See the announcement at the announcements maillist archive.

Release management planning for 2.7 is underway, and there will be a code freeze date at some point in September. 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.

Sakai 2.7

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

 The specific targets are:

1)  High-quality release by the end of 2009

2)  Refinements and bugfixes for existing core tools (i.e. those already in 2.6), especially where they offer an improved User Experience. No major new tools or significant new sets of capabilities unless they have gone through the Product Council process and the Release Team believes there is sufficient time to include them without jeopardizing deadlines.

Proposed Sakai 2.7 Changes are being collected and will be reviewed by a process that includes a release management team, the product manager, and the Product Council

Sakai 2.8

The broader goals and specific aims for 2.8 will be:

1) Significant new functionality vetted by emerging Product Council processes, including the formulation of criteria in coordination with development teams and community discussion

2) High-quality release by May of 2010

The significant new functionality being considered is presently also being collected among Proposed Sakai 2.7 Changes.

Kernel 1.x

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:

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-13324 - Getting issue details... STATUS )
  • Kernel 1.1.0 Jira Roadmap

This area (below) needs revision

Sakai 3

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:

  1. K2: a new set of core services at the back end (K2 stands for "Kernel 2").
  2. 3akai: a new UX framework; an HTML and JS front-end which implements the new designs in an accessible way.
  3. 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. A breakdown of the various capabilities is laid out below:

Personal Dashboard

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
  • Online Connections (w/ synchronous chat)

A flexible profile will be available for the user to communicate important information about themselves to others.

Social Networking

Users may invite others on the system to join their list of "contacts," an circle of associations with facilitated communication and content sharing.

File Sharing and Management
Workspace creation
Page Authoring and Assembly

Kernel 2.x

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.

  • No labels