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 93 Next »

Help Keep the Roadmap Up-To-Date!

If you have updated planning information to share, you can either comment on this page or email the Project Coordinator (Peter A. Knoop). Thanks.

Sakai Roadmap

The Sakai Roadmap is a timeline of estimated completion dates for various development efforts in Sakai. The next major release, Sakai 2.6, is anticipated to include the functionality listed below that is expected to be completed by Code Freeze on or around 29 September 2008. A Feature Freeze to help solidify the list of functionality and focus final development efforts will occur two months prior to Code Freeze, on or around 4 August 2008. (For a more detailed timeline of 2.6 development freezes and release availability, please see the Sakai 2.6.0 Release Schedule.)

Feature Timeline

Sakai 2.5 Roadmap

The Sakai 2.5 roadmap is now complete, and provides a good overview of what is in the Sakai 2.5 release.

  • January 2008
    • Tools
      • (Contrib) Assignments2 (Indiana/Georgia Tech)
        • An initial iteration of new RSF-based "Assignments2".
        • Not intended as a replacement for existing Assignments tool, but similar to it, may turn into a replacement in the long-run.
      • (tick) Messages
        • Ability to reply all ( SAK-12073 - Getting issue details... STATUS ) (Indiana)
        • Option to turn off 'send to email' option in message composition for a site ( SAK-12176 - Getting issue details... STATUS ) (Indiana)
      • (tick) WYSIWYG Widget (FCKeditor)
        • FCKeditor upgrade to version 2.5.1, which brings in bug fixes and better Safari support.
  • February 2008
    • Tools
      • (Provisional) Mailtool
        • (tick) (Contrib) An alternative version of Mailtool (Georgia Tech, Carl Hall)
          • Switch presentation technology to RSF from JSF.
          • Improvements in recipient selection, email validation, and group awareness.
      • (Contrib) SCORM Player (UC Davis, James Renfro; CRIM, Sacha Leprêtre)
        • Supports SCORM 2004 3rd Edition
  • March 2008
    • Tools
      • (Contrib) Assignments2 (Indiana/Georgia Tech)
        • Second iteration completed.
      • (Contrib) Checklist (University of Michigan, Dick Ellis)
        • An initial 1.0 release for use with Sakai.
      • (Contrib) Mneme - Test Center (ETUDES, Vivie Sinou; University of Michigan, Glenn Golden)
        • 1.1 Release
        • Add Oracle support.
      • (Contrib) Term Manager
        • A simple application for managing academic terms in Sakai's Course Management Service, which allows
          academic terms to be listed, edited, created, and deleted. (Mark Norton)
  • April 2008
    • Cross-Project Activities
      • Testing (University of California - Davis, Jon Gorrono; University of Cambridge, Aaron Zeckoski)
        • Consolidation of Sakai integration test frameworks ( SAK-12334 - Getting issue details... STATUS )
        • Migration of existing tests to new consolidated framework.
        • Support for addition of new tests to code using new framework.
    • Tools
      • Email Archive
        • Performance improvements for handling a large number of messages in the archive ( SAK-11544 - Getting issue details... STATUS ) (University of Michigan, Charles Severance)
    • Framework Services
      • Message
        • Improve performance and capabilities of the Message API and storage mechanisms ( SAK-12837 - Getting issue details... STATUS ) (University of Michigan, Charles Severance)
  • May 2008
    • Framework Services
      • Cluster
        • Improve performance by switching to a JMS-based implementation ( SAK-12797 - Getting issue details... STATUS ) (University of California - Davis, Thomas Amsler)
  • June 2008
    • Cross-Project Activities
      • Performance WG
        • Implementation of a working, proof-of-concept generic Sakai performance testing environment, including data. (University of Michigan)
    • Tools
      • Assignments
        • Improved integration with Schedule and Announcement; when an assignment opens, expose link to the assignment from schedule and announcement items (Indiana)
      • Gradebook
        • Ability to add multiple items at the same time ( SAK-12114 - Getting issue details... STATUS ) (Indiana)
        • Non-graded, non-calculating gradebook items ( SAK-10427 - Getting issue details... STATUS ) (Indiana)
      • (Contrib) JForum
        • Release of JForum 2.5.
      • Worksite Setup/Site Info
        • Add option to import and replace content from another site ( SAK-12433 - Getting issue details... STATUS ) (Indiana)
    • Framework Services
      • Authz
        • View site as if in a different role ( SAK-7924 - Getting issue details... STATUS ) (Indiana)
      • Portal
        • Timeout alert, a popup warning to users before session ends ( SAK-8152 - Getting issue details... STATUS ) (Indiana)
  • July 2008
    • Framework Services
      • Message
        • Re-implementation that is JMS-based using ActiveMQ and improves performance ( SAK-11021 - Getting issue details... STATUS ). (University of Cambridge, Aaron Zeckoski)
  • 04 August 2008 Sakai 2.6 Feature Freeze
    • Cross-Project Activities
      • Performance WG
        • Establish baseline tests for tools and build a test results library for comparisons among releases; initial focus will be on the subset of tools in use at the University of Michigan. (University of Michigan)
    • Tools
      • (Contrib) Assignments2 (Indiana/Georgia Tech)
        • Third iteration completed.
        • Expect this one to be ready for production; Indiana plans to only offer Assignments2 and not the original Assignments in their Fall 2008 semester.
        • Assignments and Assignments2 will not share the db schema; migration path will be through site-to-site export/import.
        • User interface and overall workflow revamped, relative to Assignments' workflow.
        • Migration of grading functionality from Assignments2 into Gradebook, however, seamless workflow maintained by using Gradebook helpers in context inAssignments2; may result in loosing some grading schemes that Assignments supported but Gradebook at this point does not.
        • Increased unit test coverage.
      • Gradebook (Indiana/Georgia Tech)
        • Add helpers to support Assignment2's grading needs.
  • 29 September 2008 Sakai 2.6 Code Freeze
    • Cross-Project Activities
      • Internationalization
        • Update translations (Beth Kirschner, Internationalization Working Group)
      • User Experience
        • UX Improvement Project - Re-designed home page/landing page effort (Sakai Foundation, Fluid Project)
    • Tools
      • Assignments
        • Refactoring of db to improve performance; involves moving selected meta data from XML blob into table columns and supporting migration code. (University of Michigan, Zhen Qian)
        • Support for multiple submissions of an assignment on an assignment-wide basis. (University of Michigan, Zhen Qian)
        • Support of custom fields for assignments, with the ability to control who can see the field and when they can set it on a field-by-field basis. This addresses several common requirements, including model or example answers, notes to other instructors when collaboratively creating an assignment, a rubric for those grading the assignment, etc. (University of Michigan, Zhen Qian)
      • Gateway
        • Improve performance when there is a significant number of sites. (University of Michigan, Zhen Qian)
      • OSP
        • Enhancements in the areas of Goal Management, Reports, and Matrices.
        • (Other areas to address currently under discussion; maybe decided on by later March, early April?)
      • Page Order Helper
        • Support for page grouping.
      • Preferences
        • Provide additional functionality in Tab Management to support moving sites to the absolute top or bottom of the list (i.e., double-arrows) and accommodate multi-item selection and manipulation (i.e., shift- and control- click). (University of Michigan, Zhen Qian)
      • Resources
        • Initial Fluid redesign of as-yet-undetermined components associated with Resources UX. (Fluid Project; University of Michigan, Jim Eng)
      • (Contrib) Resource Viewer/Content Viewer
        • Initial version for early adopters to try out. (Arizona State University, Joshua Ryan; Whitman College, Mike Osterman)
        • Add helper, based on entity broker, to help in sequencing content for viewer. (Arizona State University, Joshua Ryan)
      • Samigo
        • Allow editing a published assessment. (Stanford)
        • Ability to release assessments to groups. (UCT)
      • (Contrib) SiteStats
        • Implement a Quartz job for collecting data. (UFP, Nuno Fernandes)
        • General SQL performance improvements. (UFP, Nuno Fernandes)
      • (Contrib) Textbook
        • Initial release of a tool to allow instructors to supply a required book list for a course. Students see Textbook in their My Workspace, so they can see all their courses' lists aggregated in one place. Supports a simple student to student book exchange. (University of Michigan, Zhen Qian)
      • (Provisional) User Membership
        • Include the created and last modified date on the screen and in the CSV export. (UFP, Nuno Fernandes)
        • Filtering the searching and viewing of users to only those users with the same named usertype(s). (UFP, Nuno Fernandes)
      • Worksite Setup/Site Info
        • Support for creating sites from a template site. The selection of templates presented is based on the site type selected. If a template is selected, then the tool selection and configuration steps for site setup are skipped. The template site would contain tools and possibly content for the tools (e.g., folders, discussion topics, events, announcements) that would be replicated in the new site. Once the site is created, a user can still adjust the tools available via Site Info. (Australian National University, Denny Alliance; University of Michigan, Zhen Qian)
        • Support for optional survey questions, defined per site type, that would be presented when that site type is selected during site creation. Data would be stored as site properties, only accessible via SQL. Examples questions might include asking the site creator who they are (e.g., faculty, staff, student) and for what purpose they are creating the site. (University of Michigan, Zhen Qian)
        • Ability to add multiple chat rooms when adding the Chat Room tool to a site. (University of Michigan, Zhen Qian)
      • WYSIWYG Widget (FCKeditor)
        • FCKeditor plug-in to allow users to embed entities. (Joshua Ryan)
    • Framework Services
      • Component
        • Support for more flexible configuration of components, SAK-8315. (Berkeley, Ray Davis)
      • Content Hosting Service
        • JCR implementation, testing and migration. (Cambridge)
        • Hooks for a virus-scanner service to support optional, add-on virus scanning capabilities ( SAK-12985 - Getting issue details... STATUS ). (RSmart, John Bush)
      • Portal
        • Develop an iFrame portlet that will completely replace the tool iFrame; this will eliminate one frame for web content tools. (University of Michigan, Charles Severance)
        • Add a new view which allows a tool to request that it be shown maximized and in a frame set rather than an iFrame; helpful for things like publisher content, SCORM players, etc. that already have left-hand buttons and in preventing double scroll-bars. (University of Michigan, Charles Severance)
  • Mid-2009
    • (Contrib) Gallery (Berkeley, Fluid)
      • Improvements and generalizations to make it easier for other institutions to adopt.
  • early August 2009 Sakai 2.7 Feature Freeze
  • late September 2009 Sakai 2.7 Code Freeze

Key: (tick) Completed Work

Future Work

These are features and functionality that folks are working on (or plan to start work on) for which they do not have a good estimate for completion at this time.

    • Cross-Project Activities
      • Accessibility Working Group
        • Recommend whether to replace FCK Editor with TinyMCE or give users the option. (TinyMCE is accessible and supports accessible content creation, while FCK Editor fails on both counts; however, significant investment on adding options to FCK Editor, such as citations, has already been made. Neither at present supports MathML, but should.)
        • Help test a frame-less version of Sakai.
        • Explore problem with Content iFrames becoming unusable when CSS is disabled.
        • Suggest improvements for keyboard-only use of Page Order tool.
        • Suggest fixes for unresolved "Accessibility" Jiras.
        • Expand accessibility testing to include Tests & Quizzes (Samigo) and OSP (Portfolio) tools.
      • User Experience Working Group
        • Determine where consistency of wording across tools is needed and address it (e.g., SAK-9410 - Getting issue details... STATUS : Add and New, SAK-9678 - Getting issue details... STATUS Remove and Delete)
    • Tools
      • Calendar Widget
        • Update the calendar widget for Velocity-based tools (e.g., Assignments, Announcements, Schedule) to address internationalization and localization issues and for consistency with calendar widgets used by other presentation technologies elsewhere in Sakai. (University of Michigan, Zhen Qian)
      • (Contrib) IMS Tool Interoperability
        • Improve IMS Tool Interoperability portlet in concert with the Open University of Catelonia's Open Campus project. (University of Michigan, Charles Severance)
      • (Contrib) OpenCast (Berkeley)
        • A podcast capture, post-processing, and distribution system that will integrate current technological advancements, such as Apple's Podcast Producer, with existing academic community source frameworks, such as Sakai.
      • Worksite Setup/Site Info (University of Michigan, Zhen Qian)
        • Support for generic ability to add and configure multiple instances of a tool when adding the tool to a site.
        • A tool for generating statistics based on survey questions presented during site creation.
    • Framework and Services
      • Cluster Service
        • An alternative implementation based on JMS ( SAK-12797 - Getting issue details... STATUS ) (University of California - Davis, Thomas Amsler)
      • Portal
        • When the 2.5 portal solidifies, create post-2.3 and post-2.4 branches to offer its functionality to those running Sakai 2.3 and 2.4. (University of Michigan, Charles Severance)
      • Site Hierarchy (Oxford)
        • A service that allows sites to be arranged into a hierarchy (sites can exist at multiple nodes in a hierarchy or be their own single-point hierarchy) and manages the permissions on creation/updating the hierarchy.
        • A set of tools that allow you to manage a hierarchy of sites.
        • Development of a helper tool versions of SiteSetup (Site Info, Worksite Setup) and the site browser so that they can easily be embedded in a workflow.
        • A custom portal handler to support the /hierarchy namespace.

Possible Future Work

These are features and functionality that folks are interested in collaborating on, but which they have not yet committed to working on. If you are interested in collaborating on one of these topics, please let me know, Peter A. Knoop.

    • Cross-Project Activities
      • Internationalization WG
        • Actively looking for volunteers to help address the issue with dynamically localizing page and tool titles. (University of Michigan, Beth Kirschner)
    • Tools
      • Potential New Tools
        • "Dashboard" views cutting across all sites; probably start with Assignments. (Georgia Tech)
      • Calendar
        • Zimbra calendar integration with Schedule tool. (Georgia Tech)
      • Mailtool
        • Absorbing Mailtool into a new Email Archive tool (as a composition screen). (Georgia Tech)
    • Framework and Services
      • Off-line Sakai (group of South African organizations?)
        • Ability to work with a local copy of Sakai (i.e., on your laptop, disconnected from the network) and sync between the local copy and your Sakai installation.

Associated Projects' Roadmaps

Adopter Timelines

Please add you adoption timeline information by commenting on this page, and we'll incorporate it into the table below. Thanks.

Adoption of Sakai 2.5


Tentative Timeline

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="84b7607c-f26b-48f9-b5ec-6a6c98fdea0c"><ac:plain-text-body><![CDATA[

University of Cape Town

2.4 to 2.5 December 2007 [Done!]


Sakai Foundation (Collab)

2.4 to 2.5 March 2008

Rutgers University

2.3 to 2.5 May 2008

Georgia Tech

2.4 to 2.5 May 2008

Stockholm University

2.3 to 2.5 May 2008

University of Cambridge

2.4 to 2.5 June 2008

University of Michigan

2.4 to 2.5 August 2008

Rice University

2.4 to 2.5 August 2008

University of California, Davis

2.4 to 2.5 September 2008

Australian National University

2.4 to 2.5 mid- to late- 2008

Adoption of Sakai 2.6


Tentative Timeline

Sakai Foundation (Collab)

2.5 to 2.6 February 2009

  • No labels