2009-10-19 Conference Call

Meeting minutes for October 19, 2009

Sakai/OSP 2.6 Issues and Status
- SAK-12914 Database error when importing osp matrix. Not specific to 2.6. Problem with particular matrices.
- SAK-15958 Slow performance in Wizards Needs verification
- SAK-16785 Sortable columns in OSP Portfolio tool - patch on ticket. Aaron provided patch, but will need rework for 2.6 release.
- SAK-16863 Error when saving page in Freeform Portfolio. Nancy has found more things wrong with it. Brian said that there is a new fix by rSmart. Brook from rSmart was able to solve the problem, but is not sure of ramifications. Also issue with styles -- if you apply a style to the first page, it seems like it is set for the next pages. Should the documentation just document what's there, but include a comment in the docs saying that it's a known issue.
- SAK-16869 backtrace in share when a user has been deleted Reported at Rutgers. Needs to be verified to be merged into 2.6, otherwise it will go into 2.7. Marist can look at it.
- SAK-16871 osp share sends wrong password. There is a patch that needs review. Not ready for inclusion.
- SAK-17012 matrix breaks when default cell title exceeds 255 characters. Lynn will verify it.
- SAK-17055 Matrix group filtering does not differentiate Sections from Groups. Reported on email list. A couple institutions are affected by it. Shouldn't be difficult to resolve.
- Paste fromWord in new FCKeditor
Sakai 2.7/2.8 Development Status
- Code freeze Dec. 1
- QA Testing Resources for OSP 2.7 release? Please keep resources available as date approaches.
- IU changes: Chris has been really busy, so not in yet:
- Status Update (IU): SAK-13838 Add Forms and Attachments User Interface Rework, Version 2
- Status Update (IU): SAK-16693 Synchronize Portfolio Site Rosters with Associated Course Sites
- Status Update (IU): Indiana University Matrices Enhancements
  - 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
- Status Update (CRIM): Finer Grained Document-Level Matrix Permissions Updates. They will get back to us when they have address our comments.
- Status Update (UM): Collaborative Portfolio ContributionsThere is a link to the nightly server on the Meetings tab. VA Tech had a couple suggestions. When you share, there is by default it is set as inactive. When you share, should it overrride the inactive state. Question: how important is active/inactive status? Rests on top of old functionality that allowed portfolios to expire. Maybe portfolios should be active by default. Students don't usually share until they are absolutely ready. But they forget to make it active. What does review-all permission do with inactive portfolios. Is it possible to differentiate between people with whom you share and with whom you are collaborating. You have to uncollaborate before you share. Having shared ownership model. If someone creates a collaborative portfolio and then leaves, should the portfolio go with them? Will be written up as a feature request. Initially, If you have two collaborative authors, you can only add forms from your own or the site workspace. You can't see the workspace of your collaborators. We'll look at this next Monday. Beth will look at how it works with free form portfolios.
- Montreal has started working on structure pages within Sakai 3. Templating is interesting, but is a kind of wysiwyg thing. They would like to work more at the semantic level. The info provided inside a rubric can be reused or reorganized in different ways. Lynn: it seems like a content management system. Beth has looked at the back end and can imagine the value of all the tools being put in front of people. The Sling approach should make it way easier for non-technical people to create templates. Can rubrics be something built into the core of Sakai 3 the same way John Norman is talking about making gradability core. IU has worked with a private company to create a rubric builder.