Proposed Sakai 2.7 Changes
List still being compiled and revised - a work in progress. If you have corrections or additions, feel free to edit or leave a comment.
I've become frustrated with Confluence's limitations for displaying, slicing and dicing these issues. So for the moment work is ongoing in a google spreadsheet. See link below.
New Feature Documentation
Google Spreadsheet
User Impact: High
User Impact: Medium
User Impact: Low
New Tools or Significant New Capabilities (i.e. what appears below would be considered for 2.8)
Profile 2 (Rewritten Tool: http://confluence.sakaiproject.org/display/PROFILE/Profile2)
- new tool, uses same storage as old profile, DB conversion for new features
- uses same service as profile, service separated from tools
- roster integration? roster has dependency on old profile tool (some more work)
- Steve Swinsburg supporting, others from lancaster working on it as well
- Lancaster running in production
Gradebook2 (Rewritten Tool)
- UI level-work, GWT, existing GB services with extensions, DB conversion
- New features
- UCDavis and Georgia Tech have done some testing, in pilot at UCDavis
- full gap analysis? Increased burden to QA if have to test both.
Assignments2 (Re-written Tool)
- ground-up rewrite, RSF, site-by-site conversion of posted assignments (not submissions)
- new features - basically a new tool. Also includes new gradebook helpers as part of its core UX.
- In limited pilot at IU
- Needs to be coordinated with gradebook service plans
SiteStats (http://confluence.sakaiproject.org/display/STAT/Home)
- Nuno sole developer; some patching from others (4 committers)
- Independent tool, new tool, no equivalent functionality elsewhere
- Fairly widespread production experience with various versions
- Performance issues with earlier releases, improvements have been made
Portal Hierarchy (http://confluence.sakaiproject.org/x/noD3) -
- SAK-12350Getting issue details... STATUS- Oxford supporting work (Matthew Buckett)
- Arrange sites in a hierarchy (like "more" dropdown)
- Changes behavior of site tabs and some site navigation
- technically moderate change to portal code (skinnable Charon, might add as new portal)
- can be turned on or off on institutional basis
OpenSyllabus (http://confluence.sakaiproject.org/display/OSYL/OpenSyllabus+Home)
- new tool, HEC supporting, not in production anywhere
- functionality cuts across several Sakai tools
Sakora / Simple SIS Integration (http://confluence.sakaiproject.org/display/IMSES/Sakora+Project)
- dependencies on scheduling service, messaging service (contrib)
- one school working toward production
- little risk if not using it
- dependent on CM
Blog (Rewritten tool)
- Adrian Fish can no longer support earlier Blog tool, but will support the post-2.5 branch.
- The post-2.5 branch is a complete rewrite, similar functionality, but far superior UI and DB layer, and much less buggy.
- It has been in production for over 12 months at Lancaster University.
- It uses new db tables, so Adrian and Steve Swinsburg are working either to roll that into a method that runs when the tool starts up, or on migration scripts.
- The post 2.5 blog can be installed and replace the current without risk to the current blog tables as the table names are different, but the old blog data would still need to be migrated.
Basic LTI portlet
- Chuck supporting for two years
- code at: https://source.sakaiproject.org/contrib/csev/trunk/basiclti/
- documentation at: https://source.sakaiproject.org/contrib/csev/trunk/basiclti/docs/sakai_basiclti_portlet.doc
- running in production at Michigan, supporting two discipline-specific apps
Wishful thinking (i.e. no development team has actually proposed taking these on)
Content (Page) Authoring? (http://confluence.sakaiproject.org/display/SAKDEV/Content+Authoring)
- talk to Nate (simple course?)
- needs to attract resource
Conditional Release (http://confluence.sakaiproject.org/display/CR/Home)
- K1 issue, Zach doing work?