TCC CLE Action Items

Action items for CLE 2.10

From the TCC Atlanta 2012 Conference Meetings

New 2.10 features and proposals

  • Sakai trunk all vs trunk 
    Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Swap trunk and trunk all so trunk all is the main trunk and trunk indies is the extra one
  • Configuration in the UI properties/messages (all other major LMSs have this)  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Complete config cleanup:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Create an admin UI  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Config persisted in the DB (master from files)   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Register the config props in code (like function manager)   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • john bush put some thinking into a design with a raw prototype last year, see, /wiki/spaces/~jbush/pages/14094502597.  rSmart would very much like to get involved in this effort as it is closely related to the runtime config of i18n work we did a few years back.
  • Tomcat 7 required - webdav no longer works in 5.5 (2.9+)
    • Agreed - no more support for running on 5.5 or 6
    • ACTIONS
      • Update to newest TC 5.5 in 2.8.x but no higher  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • AZ to email dev list (tick)
  • Java 7 / Open JDK compatible/recommended (Java 6 required). Analysis. (build on the OpenJDK work already done)
    • Oracle JDK for Mac has issues (we think)
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • ACTIONS
      • Earle looking into OSX JDK issues (tick)
      • Update QA servers to OpenJDK 7 & Oracle JDK 7 (warning) (question)
      • AZ email dev list regarding the java requirements (tick)
  • Updating maven plugin (via config) to deploy to standard TC 6/7 layout (ie /lib) and making Sakai work with that. (2.10+)
    • Changes to deploy.xml across everything that has it
    • Config options to support the old structure
    • Possibly making our own dirs and config
    • Done (OPTIONAL to enable - off by default)
  • Search, cluster issues  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • http://collab.sakaiproject.org/pipermail/sakai-dev/2012-May/017368.html
    • Suggestion from Ian Boston: http://www.elasticsearch.org/ (based on Lucene)
    • SOLR (from Oxford and others)
    • Issues are (A) must scale ad (B) more stuff indexed (easier to index)
    • ACTIONS
      • Create abstraction layer  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Move all search handling over to to the new shim  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Implement SOLR under the shim  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Implement legacy search under the shim?  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Oxford improvements (completed) in Core and JIRA
    • OAuth (+admin) -  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      Soft Delete  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      Direct endpoints (resources / message center) - done - with Resources and MSGCNTR
  • Kernel cleanups/migrations
    • Move EB (or most of it) into kernel (warning)
      • Make it another package in kernel OR just do it like the other services
    • Move jobscheduler into kernel (warning)
      • Scheduled processing should be part of the kernel
      • Needs ticket created (warning)
    • Remove JCR  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Sometimes causes build failures, not being used, etc.
  • Version numbering for sakai core and kernel (in progress)
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Move LessonBuilder to aligned version (warning)
    • Move sakai/trunk to reflect what is in sakai-trunk-all (NOW) (tick)
  • New tool/replacements for 2.10
    • Signup tool from Yale
      • contrib tool - Home
    • Roster2 to replace Roster (Neal will followup) (warning)
    • Assignment2 to replace Assignment - NOT NOW
    • A blog of some description: Clog, BlogWow
      • No blog or clog in core - NO ACTION
    • Web Content portlet 
      • Better backend detection of whether sites will allow themselves to be framed or not (tick)
      • Grabbing 'preview images' like facebook (question)
      • Wisconsin "web proxy portlet"? (error)
      • OAE proxy servlet? (error)
    • News Feeds to replace News
      • Could be improved (options page) - 85% done
      • OK to go as is though (warning)
      • Needs ticket for moving this in (question)
  • Calendar tool that supports all features of ical - NO ACTION
    • Work ongoing and some stuff already done, needs to be consolidated? 
    • Bedework? as a pluggable option? (maybe we have an attempt available)
  • DOCS project - NO ACTION
  • Hibernate upgrade ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. (tick)
    • Will break all contrib tools that use hibernate (maybe 50% or so)
    • Mysql indexing, number of sql/hql params, requires artifact name changes
  • Spring 3 upgrade (tick)
    • This breaks all the contrib tools (that use spring - almost all)
  • Spring annotations for components (add support to the kernel to allow it)
    • OK for 2.10 (warning)
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Caching
    • Address Performance issues
      • 2.9 candidate (definite 2.10)
      • Authz caching:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Authz query (from VT):  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Tool look/feel improvements
    • CKEditor tune-up
      • Remove unnecessary buttons (tick)
      • Optimize a view for mobile now that iOS supports it again (warning)
      • Make sure no double scroll bars (tick)
      • Standard CKeditor configs (minimal vs full) (warning)
    • Megan - Samigo team update (tick)
      • Newer release of Samigo for 2.9
  • i18n centralized settings:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Continue getting more duplicate settings into here to eliminate inconsistency in labels and make translation easier
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Not for 2.10? (warning) (question)
  • i18n cleanup of unused strings (for 2.10) (warning) (question)
  • Stuff that should be enabled by default
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Shorturl enabled by default, and activated in Resources:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • OK
    • Announcement reordering (tick)
      • OK, also 2.9
    • site.roleswap - added to Instructor and maintain roles (tick)
      • OK and 2.9 (migration and install) - check lessons
  • Replacement for WURFL  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - No Longer Used - NO ACTION
    • see if we can enable RTE for ipad, etc.
    • ACTIONS
      • SS will look at replacing with mobile-detect library and we will merge back to 2.9
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Drag and drop in resources
    • GSOC and rsmart projects:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Dash API hook in kernel:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

 

Post 2.10 Release features and proposals

  • Configuration in the UI properties/messages (all other major LMSs have this)  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Create an admin UI  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • New tool/replacements
  • Turning on portal chat by default? (question)
    • Needs to pass performance testing - needs large scale production use
    • Maybe needs abstraction for how it communicates (alternative to jgroups, ability to turn it off in user prefs)
    • Config and jgroups?? (warning)
    • Abstract way to handle messaging (warning)
  • Hibernate upgrade to 4.1
    • Much bigger effort than the previous upgrade (question)
  • JSF upgrade
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Needs to be done for each tool individually - no need to upgrade across the board (warning)
      • Create tasks for each tool?
  • Removal of deprecated kernel methods
    • not now (maybe 2.11)
  • Caching
    • Request level (threadlocalmanager replacement)
      • Replace with actual cache or at least TLM patches that look for request and operate differently when outside one? (warning)
    • Sessions (portable and cached)
      • Eliminate sticky sessions, less memory use, possible to cycle servers (warning)
      • Wrap and redirect objects out of the session and put it in the cache? (warning)
    • Messages, Queues, Events (through the DB currently)
      • Use JMS api, change current implementation to use a "to the db" impl (warning)
    • Invalidation, cluster caching (abstracted)
      • Try to turn this on in ehcache, see if anyone dies (warning)
  • Multi-tab / multi-window / less-session heavy tools
    • assignments (warning)
    • samigo (warning)
    • gradebook? (warning)
    • forums? (warning)
    • announcements (warning)
  • Fix long operations to use async processing
    • probably in quartz or jobscheduler
    • alternatively bringing in a jms provider (messageservice in contrib/activemq) is another way to do this.  One of the problems using quartz this way is that the quartz log can get really noisy for things that fit this bill that occur often, then you need a purging solution, otherwise the quartz event log gets unwieldy.  Once consideration we run into when attempting to use quartz for this purpose.
    • Related to  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2.9 Release specifics

  • 2.9 Release
    • When will betas be done (end of july-ish) and 2.9.0 released (depends on QA, late Fall maybe)
    • Criteria for releasing (all criticals and blockers resolved and tested)
    • Making sure security issues are addressed/responded to
    • Expected future of 2.9 releases (probably once a quarter)
    • Use the trunk skin (only if it can be ready by July 4th - a11y, GS)
  • 2.8 Release
    • Future 2.8 releases (maybe 1, possibly 0)
  • 2.7 will be deprecated @ 2.9 release (assume 2012)
    • If you're running it, watch out for security fixes but there will not be more releases or active bug fixing or merging
  • TODO: Send out info to let people know about the 2.7/2.8 status (tick)