2010-01-11 Conference Call

Owned by Former user (Deleted)
Last updated: Jan 11, 2010Version comment
5 min read

Meeting minutes for January 11, 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))
    • SAK-17055 Matrix group filtering does not differentiate Sections from Groups In need of testing
    • SAK-17481 Error saving a free form portfolio when a page has been created with no layout. Resolved by Brian.
    • SAK-17119 Previewing Unsaved Freefrom Portfolio results in stack trace. Resolved by Brian.
    • SAK-16433 FCK editor freeform portfolio item plugin does not create hyperlink SAK-15813 is a related ticket. Code has been there since the beginning, not clear why it's not working now. Noah, will look through code some more. Brian has a way to fix it, but nervous about changing something that's been there from the beginning.
    • SAK-17678 In Portfolios>Share with Others, the "Add and return" button does not work with user IDs or email addresess. Beth fixed it. QA servers don't have latest build. Works for Michigan. Dup 17345. Not in 2.6, not QA'ed. Merged into CTools release. Chris and Brian will merge it into 2.6.
  2. Sakai 2.7 Development Status
    • Status update: 2.7 QA Testing (The OSP Test Scripts can be found at System Test Scriptsand Scripts for Testing IU Enhancements). Alan Berg will be devoting much of his day to testing on Wed., so test scripts need to be ready. Hongbo will begin testing soon.
    • Status update: Code review / bug fixes - info from Alan Berg - SAK-17647In the neighborhood of 30 issues that are guaranteed null pointers, etc. Should take about 15 minutes apiece. Noah will talk to Hongbo about it.
    • Known issues remaining for merged SAK-15710 (IU enhancements)
      • SAK-16237 Not allowed to evaluate in Evaluations tool in My Workspace. Brian has been working on it and thinks he has it working, but it takes a lot to test.
      • SAK-17350 Broken link back to associated assignment when editing a cell. Brian not sure about status.
    • SAK-16557 Indexes are missing on OSP tables with Oracle. Noah posted them. He checked with Chris, who has not yet had a chance to look at them. In the next weeks they will try to get scripts written for installing on Oracle safely.
    • SAK-17508 Can't change name of portfolio in Portfolios tool. Waiting for qa1-nl to be updated to beta 1 release.
    • SAK-17579 OSP fails if compiled on Java 1.6. A number of Sakai tools are in this boat. Seems to be related to JSF MyFaces library. Update might help.
    • SAK-17326 In Portfolios tool, auto-select newly created forms when adding/editing content. Chris has closed this. Beth will verify this. For 2.7.
  1. Sakai 2.8 Development Status
    • SAK-17564 Support display of Public Portfolios within a site. Michigan proposed but has not worked on yet.
    • SAK-17351 Copy Portfolio - Review Unicon proposal. On 5th, Unicon said it was important to their customers, so they are willing to do some work on this. Lynn: is it enough to just duplicate forms? Three questions: What should happen to a matrix inside a portfolio. It can't really be copied. Noah thinks that there is no real way to make a copy of a matrix. But what can we copy? The references to the forms and the templates for the portfolio.Not necessarily duplicating material, but ability to update. The portfolio part, the part that links the different parts of the content, is what gets duplicated. VA Tech being able to copy portfolio options form would be a huge help. It's an intrinsic part of the portfolio. For VA Tech, the options form is the portfolio. Should the ability to copy forms be broken out as a different functionality? Should it be within the Portfolios tool? No place where the users goes and sees list of forms. We should think about this offline and come back. Lynn thinks capability should be exposed inn many places. Copying and updating the new copy to show growth is a good thing. IU wants this for showing growth from year to year. Should things mostly be copies or mostly links to originals. Copying the references is the easiest to understand, but we may need to make real copies that can be tweaked. Maybe start with references, but let user choose to create copy for editing on each form.Backtracking all the links -- do you want to change everywhere? Should comments, updated time, etc. be copied? Should be created fresh. This change should be written up as a Feature Template. Unicon should be willing to write this up. Noah told Charise that we would talk about it today and get back to them. Which is Unicon interested in, copying portfolios or copying forms? Noah will respond on list and cc Charise.
    • SAK-17323 In Portfolios tool, prompt user to give portfolio a name at the time of creation. Is this something we want included in the common Sakai source tree? What do we want for 2.7 v. 2.8?
    • SAK-17324 Add Portfolio Name to Portfolio Details on Summary Screen. Was implemented in time frame for 2.7 release, but Michigan had second thoughts. Urmila came up with a proposal that Beth likes. The title should still be preceded with "Portfolio Title" or else link should say "Edit Title". Sean suggested that a textfield always be present with the focus there. Not approved. Desirable for the 2.7 time frame. Beth will dig up Jira ticket about not prompting users for  portfolio template if there is only one and add comment about watching out for this issue.
    • SAK-16693 Roster Synchronization (see Roster Synchronization for details) Was originally on 2.7 status list, but didn't make it for 2.7. IU is using it locally in their 2.6 instance. Does the rest of the community want it in a controlled or configurable way. We should talk about it the week after next. People should review the write up, which has screen shots. Chris can probably set up a test server with this on it.
  2. Standing Agenda Updates