Child pages
  • List of Planned 2.8.0 Changes
Skip to end of metadata
Go to start of metadata

Document in Progress

This page is in progress. The anticipated Additions, Deprecations and enhancements should be solidified by Sept 8th.

Timeline

A timeline for 2.8 has been adopted.

Key dates:

Action

Date

Major changes

25 August 2010

Code Freeze

21 September 2010 (23:59 UTC)

Alpha tag

21 September 2010

Beta tag

2 November 2010

String freeze

2 November 2010

Release Candidate Tag

11 January 2011

Decision Point for Release

15 February 2011

Software Release

1 March 2011

Additions

What

JIRA 

Description of addition proposal

Notes

Status

CK Editor

 

Upgrade to CK Editor

Default behavior is for this to be disabled for 2.8.0. 

Included in 2.8.0.

BasicLTI Simple Outcomes

BLTI-68 - Getting issue details... STATUS

 

It has been put into trunk, the test plan has been updated and it is good to go for 2.8

Included in 2.8.0. 

ShortenedUrlService

 

A simple URL shortening service that is pluggable with different implementations. Institutions can configure which implementation they want to use via sakai.properties. Ships with a no-op, randomized (e.g. a1bk8C) and bit.ly API implementations.
http://collab.sakaiproject.org/pipermail/sakai2-tcc/2010-August/000238.html

Any one using?  Is there a test plan

Included in 2.8.0.

Dynamic localization using database back-end

SAK-18678 - Getting issue details... STATUS

Admin tool that would store all property key/value pairs to the database. It is fully described in the Jira.  This work requires Kernel changes; see
KNL-563 - Getting issue details... STATUS The tool is in contrib now and ready for testing.  If the tool for some reason is considered  un-ready, we may consider including the KNL changes without the corresponding tool to ease future adoption
SAK-18984 - Getting issue details... STATUS

 

Included in 2.8.0.

Job Scheduler

 

SAK-18864 - Getting issue details... STATUS Create Persistent Event Logs For Job Scheduler
SAK-14293 - Getting issue details... STATUS Add properties to job scheduling
SAK-13696 - Getting issue details... STATUS Provide interface to JobDataMap to set Quartz job properties

 

Included in 2.8.0.

Hybrid

 

Inclusion of the Hybrid module from Nakamura as well as patches for login and providers. Merge SAK-17222 and SAK-17223, bind to a release artifact for hybrid module.
login
SAK-17223 - Getting issue details... STATUS
- Create a new container authN filter which authenticates against K2.*Need someone more familiar with login module to review. It is unclear to me that this container login will be useful in production environments as most with want both S2 and S3 pointed to CAS or other SSO. A patch is attached to the JIRA for easy review.
Two new sakai.properties and other properties to enable new login filter:

# enable SAK-17223 K2AuthenticationFilter
top.login=false
container.login=true
org.sakaiproject.login.filter.NakamuraAuthenticationFilter.enabled=true
org.sakaiproject.login.filter.NakamuraAuthenticationFilter.validateUrl=http://localhost/var/cluster/user.cookie.json?c=



providers
SAK-17222 - Getting issue details... STATUS
- Develop new UserDirectoryProvider that will authenticate against K2.
Other than some xml config changes, this one should be ready to merge in cleanly. A patch is attached to the JIRA for easy review.
Adds the following sakai.properties:

# configure SAK-17222 NakamuraUserDirectoryProvider
org.sakaiproject.provider.user.NakamuraUserDirectoryProvider.validateUrl=http://localhost/var/cluster/user.cookie.json?c=
x.sakai.token.localhost.sharedSecret=default-setting-change-before-use


Hybrid
This module provides a couple of REST endpoints for the Sakai 3 portal (i.e. list of sites for current user, and list of tools for a given site). We probably need 2.8.x to bind to an indie release of this module. I will likely need to defer to the maven mavens on this issue.

Integration test can be found at: https://source.sakaiproject.org/svn/hybrid/trunk/testscripts/SlingRuby/tests/hybrid-test.rbhttp://github.com/sakaiproject/nakamura/blob/master/hybrid/testscripts/SlingRuby/tests/hybrid-test.rb Enable sakai.properties for integration test:

# declare shared secret for trusted login from nakamura
org.sakaiproject.util.TrustedLoginFilter.sharedSecret=e2KS54H35j6vS5Z38nK40
org.sakaiproject.util.TrustedLoginFilter.safeHosts=localhost;127.0.0.1

 

Login and Providers patch inlcuded in 2.8.0.   The Hybrid module was removed for 2.8.0. See
SAK-19326 - Getting issue details... STATUS

MessageService

 

Move the messageservice into core. The Sakai MessageService integrates JMS with Sakai and exposes the JMS API as a service. ActiveMQ is used as the JMS implementation.

 

 

Email Notification Preferences

SAK-18559 - Getting issue details... STATUS

Adds the ability for a tool to register itself as having notification preferences.
See here for the design.

In production at IU

Included in 2.8.0.

Account Validation

RES-2 - Getting issue details... STATUS

Move account validation code from contrib to be included in Reset-password will be switched of by defualt

in production at uct

Included in 2.8.0. 

Shared i18n

SAK-15037 - Getting issue details... STATUS

Provide stable i18n default strings and translations that can be called from every tool and use it to avoid string duplication in Sakai (Save, Cancel ...) to ease translation effort.

SAK-16738 - Getting issue details... STATUS

is a sample use of it.

Supported by J-F L and D RM

Included in 2.80

Deprecations

What

JIRA 

Description

Notes

Status

Mercury Portal

SAK-19001 - Getting issue details... STATUS

See the discussion and

SAK-19001 - Getting issue details... STATUS

for more information.

 

Done

Axis2

SAK-19006 - Getting issue details... STATUS

Remove Axis2 from 2.8 build proposed

 

Done 

Blogger

 

Complete removal from 2.8.0 release distribution.   Tool was deprecated in 2.7 via "stealthing".  For 2.8.0 it will be removed from externals and not built, but the code will remain remain in the same location in /svn (not moved).

See

SAK-19171 - Getting issue details... STATUS

Done

Reports

 

Complete removal from 2.8.0 release distribution.   Tool was deprecated in 2.7 via "stealthing".  For 2.8.0 it will be removed from externals and not built, but the code will remain remain in the same location in /svn (not moved).

See

SAK-19171 - Getting issue details... STATUS

Done

Profile

 

Deprecation of the "original" Profile tool (This was stealthed in 2.7.0).  

There was 1 remaining dependency to an API.   Status of this is unknown

 

Sakai Monolithic

Project

Lead

Bug Fixes

Enhancements List (w/ SAK)

API Changes?

Notes 

Announcements

Savitha Prakash

Yes

Added EntityProvider (SAK-18764 )
Fluid re-orderer implemented (SAK-8005 )

 

Around 24 fixes and improvements

Assignments

Zhen Qian

Yes

Provide a way to customize letter grades in the Assignments tool (SAK-18752)
email manifest of archive to site owner of submission of assignment (SAK-19119)
Allow instructor to specify options for Assignment tool default page, e.g. show no assignment, but do search or other filters first (SAK-18076)

 

 

BasicLTI

Charles Severance

 

 

 

 

Chat 

Maintenance Team

 

 

 

 

Calendar Summary

Nuno Fernandes

No

 

 

Nuno: "There are no changes for calendar summary."

Citations

Jon Dunn

Yes

No enhancements

No


Email Archive

Matthew Jones

 

Allowing user to specify a different "from" address. (by code freeze)

 

 

Email template service

David Horwitz

 

 

 

No expected development (as of late July)  

Gradebook

Kirk Alexander, Jonathan Cook

Yes

Bug fixes, internationalization enhancements

No

 

I18n

Beth Kirschner

 

Turkish, Vietnamese

 

 

Linktool

Charles Hedrick

No

N/A

No

No expected development

OSP

Chris Maurer, Noah Botimer

 

  •  Automate Portfolio Site Roster Management via Synchronization with Associated Course Sites SAK-16693 - Getting issue details... STATUS
  • Adds a new CM implementation and a Group Provider.  Also has a site event listener to keep groups updated.  Also added a new Authz method for performance.  See this doc in confluence.  
    Addition of OSP email notifications- Please see 
    SAK-18559 - Getting issue details... STATUS

 

 

Podcasts

Tan Nguyen

Yes

N/A

No


Portal

Matthew Buckett, Charles Severance

Yes

Minimize Navigation
Greatly improve PDA portal

 

56 Fixes and Improvements and Counting (JIRA)

Post'Em

Ying Wang

Yes 

SAK-18482 fr_FR L10n for 2.6 or later of Post'Em
SAK-9441 Upgrade Post'em to use myfaces core-1.1.5
SAK-19016 Postem deploys commons-math to shared

No 

 

Preferences 

Maintenance Team 

 

 

 

 

Quartz Scheduler 

Maintenance Team  

 

Configurable Quartz Jobs (SAK-

 

Duffy is looking for feedback on this.

Roster 

Maintenance Team  

 

 

 

 

Resources, Drop Box

 

 

Would like to have SAK-14625 in (J-F)

 

 

rWiki

Savitha Prakash

Yes

premacro added (SAK-18802 )

 

Around 25 fixes and improvements

Syllabus

[~gjthomas]

Yes

N/A

No

 

Schedule

Beth Kirschner

 

 

 

 

Site Info

Zhen Qian

 

 

 

 

WebDAV

Charles Hedrick

 

 

 

No expected development

Worksite Setup

Zhen Qian

 

 

 

 

WYSIWYG Editor

Noah Botimer

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Independent Releases for inclusion in 2.8.0 Distribution

Project

Lead

Bug Fixes

Enhancements List (w/ SAK)

API Changes?

Version

Notes 

content-review

David Horwitz

No


No

 

This project is now an indie.

EDU-services

David Horwitz

No

http://jira.sakaiproject.org/browse/SAK-19080 - Change for GB2 data model

No


 

Entity Broker

Aaron Zeckoski

Yes

N/A

?

 

 

hybrid

~lance

Yes



 

This project is now an indie.

Kernel

[~dhorwitz]]

 

KNL-582 - Getting issue details... STATUS Really usable DEBUG locale (use en_US_DEBUG)

 

Plans still developing, but for the moment there is talk about pulling more of entity broker into the kernel. Will be ready by code freeze.
1.2.0

Message Center

Bryan Holladay (old account)

Yes

  • Extend EntityBroker for MSGCNTR
    MSGCNTR-319 - Getting issue details... STATUS * Update Portuguese (pt_PT) message bundles MSGCNTR-358 - Getting issue details... STATUS
  • Allow sorting of forum threads MSGCNTR-307 - Getting issue details... STATUS
  • Start and End dates on Forums and Topics
    MSGCNTR-309 - Getting issue details... STATUS
  • Preview message before sending MSGCNTR-310 - Getting issue details... STATUS
  • Feature Request: Please allow an institution to set a default preference for the "Watch" notification email functionality in Forums 2.7 MSGCNTR-354 - Getting issue details... STATUS
  • Option to save a draft of the message MSGCNTR-355 - Getting issue details... STATUS

Yes

 

Sakai Properties:
mc.notificationDefault=1  (default)
0=EMAIL_NONE
1=EMAIL_REPLY_TO_MY_MESSAGE
2=EMAIL_REPLY_TO_ANY_MESSAGE

Samigo

Lydia Li

Yes

  • Respondus integration: SAM-633
  • Record Average Score for multiple submissions: SAM-862
  • Allow students to use Rich-Text Editor for Short Answer/Essay question type: SAM-801
  • Remove 4000 character limit for student response in Short Answer/Essay question type: SAM-756
  • Allow instructors to enter zero score for unsubmitted assessments: SAM-772
  • Allow instructors to select a feedback option that would show students their overall score only : SAM-666
  • Make Linear Access Logic Consistent : SAM-971
  • When sharing pool with more than 1 level of sub-pools, Samgio only shows two levels - the question pool level, and the first sub pool level: SAM-869

 

 

Samigo 2.8 Plans

Profile2

Steve Swinsburg

Yes

  • Galleries
  • Private messaging (needs a few tweaks but mostly done)
  • More profile fields
  • A set of profile fields for business use, default off but can be activated in sakai.properties.
  • Kudos rating system
  • Official image support
  • Backend almost entirely reworked and vastly improved

Yes

1.4.x

197 (and counting) fixes and features (JIRA)

Polls

David Horwitz

No

N/A

No


 

Reset Password 

David Horwitz

No

includes the account validation functionality (off by default)

Yes

 

 

purepoms

 

 

 

 

 

 

Search

David Horwitz

No

 

No


 

Site Stats

Nuno Fernandes
(Possibly now MT)

Yes

  • Tracking of time spent in site: STAT-241 - Getting issue details... STATUS

Yes (additions)

2.2-SNAPSHOT

 

Web services

Steve Swinsburg

Yes

New web services

No

This is available as an indie release so could be included as such

 

Architectural and library changes

What

JIRA

Description

Notes

Status

Tomcat 6 and JDK 1.6

 

Defer move to Tomcat 6 and JDK 1.6 until after 2.8 release

The move to Tomcat 6 and Java 1.6 was discussed at length on 18 August 2010. It seems that trying to make the required changes to move to Tomcat 6 and use Java 1.6 without any -D workarounds is too aggressive for 2.8.

Under discussion

support for Oracle 9i

 

Deprecate support for Oracle 9i

We could deprecate SPECIFIC Oracle9 support after, for example, the 2.8 release. In this case, the deprecation means that we don't guarantee that stuff - mostly conversions I expect - will work in Oracle9 past that time and that we are free to use Oracle10+-isms at any moment. We would need to communicate this early, often, and as widely as possible. In addition, we would probably need to offer solid advice on moving from LONGs to LOBs and making sure that OOTB Sakai doesn't create LONGS or other older/deprecated data types like DATE (use TIMESTAMP)."

Will occur after 2.8 release

 

 

 

 

 


 2.x Planning Discussion Points from Denver and beyond

The following "scenarios" should also be considered for future 2.x releases (posted by  Anthony Whyte after Denver Project Coordination Discussions):

1. Refactor JSF tools that fail to compile in Java 1.6 so that we can eliminate the need the specify the workaround system property
-Dsun.lang.ClassLoader.allowArraySyntax=true.

  • TCC Discussion:  The move to Tomcat 6 and Java 1.6 was discussed at length on 18 August 2010. It seems that trying to make the required changes to move to Tomcat 6 and use Java 1.6 without any -D workarounds is too aggressive for 2.8.
  • Comment on 8/31/10 from Charles Hedrick:  Why do we object to using -D? Mightn't we be better off to use Tomcat 6 with -D than continue with Tomcat 5.5? 
    • +1 Mustansar Mehmood
  • Charles Severance:  I think the Tomcat 5 / 6 Discussion centered less around the -D and more around the worry that there would be little issues that would pop up that would be hard to find, reproduce, track and fix. It seemed like the first attempts at T6 failed and folks decided to focus elsewhere. So we don't have any data that gives us confidence that T6 is an "easy switch".If no one chooses to run T6 and then report that T6 works solidly with no strange glitches - we will find ourselves in the same place for 2.9.

2. Refactor Portfolio and other tools in order to eliminate the need to specify the workaround system property
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false required
since Tomcat 5.5.27.

3. Rework Sakai deployment patterns (e.g., target=/lib) so that we can upgrade to Tomcat 6.0.

4. Add mailsender as a possible replacement for the retired mailtool.

  • Comment from Clay Fenlason: Re: mailtool. It should be removed, but it's less clear that mailsender should replace it. Mailsender has no maintainer either, it just happens to be in better shape codewise. Would the maintenance team be prepared to support it?

5. Deprecate linktool (replaced by basiclti)

  • Comment from Stephen Marquard: On #6, basiclti is not equivalent or better than LinkTool. They have different security models, and in some respects that of LinkTool is stronger than basiclti's. There is also some functionality for getting Sakai sessions through webservices that's not in basiclti. So I don't think it will be possible to deprecate LinkTool anytime soon, especially as basiclti's capabilities may be limited to what the standard supports.
    Comment from Charles Severance: I see no reason to deprecate LinkTool as it is not a maintenance concern and man... I see no reason to deprecate LinkTool as it is not a maintenance concern and many folks are using it in production and while Basic LTI provides equivalent information to LinkTool, BasicLTI is not a direct replacement for LinkTool. We can have the debate as to which is more secure over beers But again, the upshot is I recommend against deprecating LinkTool in 2.8.
  • Comment from Anthony Whyte: The question of deprecation (e.g., stealthing a tool in the next release (2.8) and then removing it from the release that follows (2.9)) is a question separate from whether or not it's a maintenance concern (currently Stephen maintains it). I posed the scenario in order to surface discussion regarding whether or not basiclti (or LTI) can provide equivalent functionality in 2012 that renders it redundant.

6. Review tools that do not implement fine-grained permissions and correct as necessary.

7. Review tools that are not group aware and correct as necessary.

8. Review tools that do not auto-register events with sitestats (via the entitybroker) and implement as necessary.

9. Review tools that could benefit from the addition of entitybroker providers and implement as necessary.

10. Convert portfolios (osp) to an indie release; the assignment tool might also benefit by moving to its own release schedule.

  • The conversion of OSP to an independent release was discussed, but it depends on the release of Assignments as an indie as well.
  • Comment from Mustansar Mehmood: Independent release of OSP is a great idea like samigo

11. Make portfolios i18N friendly.

12. Email Archive Enhancements (Wish list / development work without plans or resources)

  • Checkboxes for multiple deletion and sending
  • Performance improvements

13. Entity Broker Enhancements (Wish list / development work without plans or resources)

  • Search Integration
  • Archive Integration

14. Gradebook

  • Gradebook: Moving toward shared ownership of service layer, allowing for multiple front ends (eg. GB2 and legacy gradebook). IU currently conducting analysis of gap between OnCourse gradebook and the Sakai trunk gradebook, to assess effort of merging the two. See http://confluence.sakaiproject.org//x/_hIhB . Timeline unclear, but there seems to be a strong interest in getting this sorted as soon as possible. It looks like the only realistic work that could be accomplished by a 2.8 freeze would be an agreement around (and consolidation of) the data layer. This work could however not begin until mid-August.

15. Assigments2 inclusion in foundation distribution. 

  • Currently (Sept 2010), the project team is working towards creating an independent release of A2. The tool is currently being run at IU and UCT but would like to see broader pilots as well as accessibility reviews prior to inclusion in a Sakai Release. Timing for 2.8.0 doesn't seem right but looking to work towards inclusion in next release w/ features.

Questions from Alan Berg

  • What is the status of blogger and a replacement?
    • Anthony Whyte: Blogger is deprecated but is retained in sakai-2.7.0 as a stealthed tool. It is scheduled for removal in sakai-2.8.0. Currently, there is no scheduled replacement.
  • Who is going to vigorously maintain Search, rWiki, JSF etc? [MT reforms?]
  • Tools that are provisional such as reset password should they be elevated in 2.8
  • Which tools are going to be BasicLTI providers and to what extent in 2.8
  • Which extra web services are used by local institutions that we should add to the default set.

Comments

  • Charles Severance: I would say at this point a complete tool replacement (i.e. swapping out Assignments 1 for Assignments 2) should be considered both high cost and high risk. Swapping a tool is far riskier than adding a new tool so we need to be particularly careful. If there were strong community support that a new replacement tool were ready to go, I would suggest that it would take at least two releases to swap the tools. In the first release, the new tool would be added and stealthed. The new tool would need to coexist with the existing tool, providing either admin triggered bulk conversion or the ability to let instructors convert dynamically. The new tool should only be considered as a "replacement" after several schools have run the new tool at scale locally removing the original tool for at least a semester with no ill effect. For me - only then would we consider a replacement. I know this seems like an unnecessarily high bar - but our past experience with removing and replacing a tools in single release with overlap has pretty much failed every time we have tried it so far.

Post 2.8.0

  •  Lesson Builder

Additions / Deprecations that were deferred

What

JIRA 

Description of addition proposal

Notes

Status

Mailsender

 

Mail sender replaces functionality of now-deprecated Mailtool.

 

Project Team has recommended that this isn't ready for inclusion with 2.8.0 (but it may be made ready to work with it as an indie)

Warehouse

 

Complete removal from 2.8.0 release distribution.  Tool was deprecated in 2.7 via "stealthing". 

No user facing components.  OSP dependency may prevent this from occurring.

 

New Roster Tool

What

JIRA 

Description of addition proposal

Notes

Status

New Roster tool

 

Lancaster has rewritten the original Roster tool. A separate e-mail describing the technical details has been sent to the TCC for evaluation and discussion.

 

Deferred from 2.8.0 by project team

What

JIRA 

Description of addition proposal

Notes

Status

Updated blog tool

 

Lancaster has rewritten the original Blog tool in JS/Trimpath. Similar UI but with better post creation/editing facilities and an improved backend.

 

Deferred from 2.8.0

  • No labels

1 Comment

  1. There has been quite a bit of discussion on list about the need for better user documentation in 2.x lately, but I don't see it mentioned here. Does the TCC intend to address the issue of improving the volume, quality, and consistency of user documentation?