2009-07-13 Conference Call

Owned by Former user (Deleted)
Last updated: Jul 13, 2009Version comment
3 min read

Meeting minutes for July 13, 2009

  1. Sakai/OSP 2.6 Issues and Status
    • 2.6 QA Testing Status
    • SAK-16536 Free-form Portfolio Tool Stack Trace on Add Page Chris got the local resolver working. Needs to be verified.John Bush said that some clients weren't having trouble. Noah will push on the Release people for 2.6.1 to come out quickly.
    • SAK-15909 Creating Portfolio Template throws stack trace (with invalid schema).You also can't import a matrix with a form that has an invalid element. It would be good to have a utility to deal with residual invalid forms. The utility would run through forms and test them. Hopefully would be ready for 2.6.1.
    • SAK-16557 Indexes are missing on OSP tables with Oracle. Michigan will be working with their DBA to try installing the indexes. Should particularly help with viewing a particular user's matrix.
    • SAK-16591 Inconsistent evaluator selection options between Wizard main page and subpages In one case the roles are hard coded, while in the other all possibilities are available. Depends on whether you have evaluate permission in one place.
    • Crash Will had at conference is something to look at.

  2. Proposed for Sakai 2.6 inclusion
    • SAK-13810 Add description to XML provided for form rendering - John & Stephen did a bunch of work, incorporate?
    • SAK-14867 Matrix Owner name confuses students
    • SAK-15748 Add owner name information to form metadata for view renderer use
    • SAK-15862 Portfolio Share notification should set reply-to in email
    • SAK-15911 Cannot tell result of Form save attempt - disallows autosave

  3. Sakai/OSP 2.7 and beyond Development Status
    • SAK-16691 OSP Permissions crash. Permissions helper problem.
    • SAK-14165 Portfolio assembly is slow with many completed Forms. Michigan may have rolled this into production last Saturday. We have a good case for getting this into 2.6.1.
    • SAK-16608 List of presentations needs to differentiate between 'shared' and 'public' portfolios. There is a screenshot on the ticket. Please look at it.
    • SAK-16610 Create "Review" option allowing authorized users to review all portfolios. Allow designated roles to review all portfolios, even if they aren't shared.
    • SAK-12922 Configuring OSP to run successfully without autoddl enabled.
    • Merge to Trunk Status: Indiana University Matrices EnhancementsIU still looking for time to do merge.
      • SAK-15822 In Matrices, "manage status for all users" only changes current user
      • SAK-16261 Make the Manage Status function in Matrices and Wizards Group Aware

  1. Misc
    • The domain osportfolio.org is now gone -- the domain expired. Do we care? Noah will follow up with Nate about it to see what's going on, since some people thought rSmart had renewed the domain.
    • Current thinking, very tentative: Code feature freeze for 2.7 by September 30, code freeze by November 30
    • Sakai Conference updates. 30% newbies. Lots of well attended sessions. New people presenting, showing new work. Lots of work on reporting. Two or three reporting tools being developed -- do we want all three or just one, or what? OSP now seen as integral to Sakai, not just trouble. Some of our processes may be adopted throughout the community. Introduction of product mananger role is positive. Should help push the cohesion of the project. Michael Korcuska will make some design time available to content authoring. Open Syllabus people will be working with a designer to have some things in September. We should put a timeline on synthesizing the information/vision from the Friday 3.0 session.
    • Might be useful to have time on the call when newbies can ask questions. Maybe we should do the Jiras last, not first.
    • Talking about reporting: each of the three groups working on reporting (Serensoft, IU, an Michigan) will provide some documentation of what they are doing. People will look at the docs and then discuss what they want to do with reporting. We will make a page under confluence design and development named Reporting Strategies.