2010-03-08 Conference Call

Owned by Former user (Deleted)
Last updated: Mar 08, 2010Version comment
3 min read

Meeting minutes for March 8, 2010

  1. Sakai/OSP 2.6 Issues and Status (Bug fixes can be verified on the following QA servers Nightly Build (HSQLDB) or Nightly build (Oracle))
    • n/a
  2. Sakai 2.7 Development Status
    • Status update: 2.7 QA Testing (The OSP Test Scripts can be found at OSP Test Scriptsand Scripts for Testing IU Enhancements) Marist has switched projects around. Brian be doing more. He will try to have the wizard stuff tested by the end of the week.
    • SAK-17659 potential NPE's and s resource leaks in OSP found by static code review. Noah has been working on this.
    • SAK-16557 Indexes are missing on OSP tables with Oracle. Michigan has promised, but without a timeline.
    • SAK-17852 !site.template.portfolio lacks roster perms for all roles. Not adopted by anyone, should be simple to fix.
    • SAK-17940 Auto-select of Portfolio Forms causing intermittent problems. Michigan hopes to take a look at this, but hasn't done it yet.
    • SAK-18142 Reports fails on Tomcat startup. Seems to be doing an abort instead of a log message due to a change made by Noah. 
    • Brian asked about problem where, if a group is created in a site, the matrix doesn't work. When you add the first group with matrix in Normal mode, users won't be able to see anything. Really a usability issue rather
    • 15929 Chris wizards not respecting a use permission. There is a lot of testing involved.
  3. Sakai 2.8 Development Status
    • SAK-17351 Duplicating portfolios (merge pending review on osp test server). Anthony, Beth, and Aaron were setting up a new server for testing branched changes. Should be deployed to trunk/experimental. Beth hopes that it will be an alternative to the osp-nightly server.
    • SAK-16693 Roster Synchronization (followup on questions/answers since Feb 15 call). Beth: the roster synchronization provides auto site synchronization, as opposed to Site Info means. Seems like a reasonable feature, but should be optional. Configuration mechanism -- xml file somewhere on the server as part of the build. You can drop it into sakai.properties instead of having it in a WAR file. There isn't another good candidate mechanism. Would it require a rebuild if you make a mistake in configuration? No, should be possible to just change the file. Would anyone else use this functionality? Could stay as IU branch, but good to have everyone on the same code base. Should be something you can turn off globally, but you can turn it on on a site level. Jan strongly in favor of including. Beth will add comment to Jira that it is a good feature as long as it's optional. Should there be a demo server? Beth will set one up.
    • SAK-15547 Skip First Step of Portfolio Creation (if only one choice presented to user)
    • SAK-17579 OSP fails if compiled on Java 1.6. The maintenance team may have some pointers as they start to work on it. Not clear that the problem is in our code.
  4. Standing Agenda