Child pages
  • 2009-08-31 Conference Call

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Meeting minutes for August 31, 2009

  1. Sakai/OSP 2.6 Issues and Status
    • There are a number of issues that should have gone into 2.6.0, but did not. According to Anthony, they will go into 2.6.1. They have been removed from the agenda.
    • SAK-15958 Slow performance in Wizards
    • SAK-10949 Adding a group causes Manage Matrices dropdown menu not to appear. This needs developer attention.
    • SAK-16863 Error when saving page in Freeform Portfolio. Has been reproduced. Needs someone to look at it.
    • SAK-16869 backtrace in share when a user has been deleted Charles Hedrick submitted a patch that Beth reviewed and merged. Sean will verify it.
    • SAK-16871 osp share sends wrong password. There is a patch attached to the Jira. There is probably a better way to solve this, but if time is lacking, we should go with the patch provided. If this is a priority for any institution, they should work on it.
  2. Sakai 2.7/2.8 Development Status
    • SAK-16884 Can't add a matrix in trunk. May be related to the Spring framework upgrade. Needs developer attention.
    • SAK-16770 Matrix ScaffoldingId parameter lost on import & save. May be related to Spring Framework upgrade.
    • Status Update (IU): SAK-13838 Add Forms and Attachments User Interface Rework, Version 2 Was reviewed and approved by the community around a year ago. Was supposed to go in 2.6, but didn't make it. It is on the testing branch that IU made available for people to use, but that version is a little outdated and broken in some browsers. Chris is working on merge to trunk.
    • Status Update (IU): SAK-16693 Synchronize Portfolio Site Rosters with Associated Course Sites. This should have some more community input. It should go in a separate branch so people can check it out.
    • Status Update (CRIM): Finer Grained Document-Level Matrix Permissions Updates. CRIM wasn't on the call but Montreal reports that they have something working. Beth will send an email to Narjes to see what the status is. There were questions raised that . Should go into a branch that people can play with before it is merged.
    • new Collaborative Portfolio Contributions. Beth sent out email about proposed feature of collaborative portfolio authoring. Lynn brought up the question of how sharing would be separated from the authoring process, since you use the share page to give write permission. There are multiple use cases, such as for grant evaluation or a shared portfolio about project experiences. Jan: community that wants to create institutional portfolios could use it. Functional details: the owner of the portfolio would go to the share with others tab, and say that write access should be given to everyone the portfolio is shared with. Once write access is granted, the Actions dropdown would have edit in it. They would be able to add and delete forms, but not edit content or change share settings. Only the original author could change share settings. Two classes of shared users. It would be hard to have true collaborative editing in the in the time frame Michigan needs. True editing would also involve a change to the interface. You can only add forms, not edit someone else's form. Collaborative authoring has implicatons for work flow; what if content already evaluated? Really a Sakai 3.0 thing? Would it be possible to make a copy and edit it? That would involve things to untangle, like people working on a copy but thinking it is the real thing. Wikis are the only place currently where you can edit collaboratively, but people are coming to expect it.

  3. Standing Agenda Updates
    • Sakai 3 Development & Content Authoring. UX calls are being reinstated. A 3.0 demo given recently at UM showed lots of progress. Lynn proposed that we have another get together like a couple years ago at UM or last year at IU where we could plan for Sakai 3.0. Noah proposed it would be a good way to reach out to non-OSP people. He proposed that we take 2 weeks to do some homework questions about what to do, and then try to have a date settled on by the end of September. We would need to do it in October, or wait until January or February. Should start with a demo of 3.0 so we aren't reinventing the wheel.
    • Teaching & Learning & requirements gathering
      • Moving content from http://osportfolio.rsmart.com to www.sakaiproject.org Pieter says that sakaiproject.org will be ready to start hosting in a coupl weeks. The old site is in Drupal, so the export is not necessarily straightforward. People need to look at the material to be sure it is up to date and accurate.