Josh Baron was on the call to discuss our requirements process and its relevance for Sakai in general. There are several new initiatives, Product Council and Sakai 3. People ave been focused on nitty-gritty issues, but we need a higher level visioning process, especially for Sakai 3. As he talked to people, he heard about the OSP vignettes page and the approach of using one word. Josh wanted to understand the process better and see if anyone in OSP was interested in helping Sakai as a whole do something similar. Jan: this started in Amsterdam with people thinking, wouldn't it be great if portfolios could do the following things and do them well. Currently a primary goal is to see what could be functions that the larger Sakai community is behind so that OSP doesn't have to do it, and then what do we want to do specifically for portfolios, as well as for the community. Our long term goal is to work collaboratively with the community, but not get lost. Josh had tried creating his own list, but then found almost all of them in the existing list. Would like to see more portfolio-like things throughout Sakai tools, such as assessment. T&L needs to reschedule their calls, and they were thinking of having some calls with us. Our calls are different from T&L in that a fair amount of time is spent on development activities. Would it be better to have representation rather than everyone blend? We should try to get the message out that we are trying to do something new in September or October. How about working with international members of the community? Adding minutes in a public place and announcing their availability. Clay will have increasing role in this as well. As product manager, he will be trying to move this kind of collaboration forward.
SAK-12922 Configuring OSP to run successfully without autoddl enabled. Global Sakai issue.
SAK-13838Â Add Forms and Attachments User Interface Rework, Version 2 Work is mostly done. There is a completed enhancement template for it. This is work we looked at a while ago. Important because of changes they have made where there are a lot of links from other tools that need to be displayed nicely with info about where they come from. People should look at this. Lynn will demo 8/10.
Merge to Trunk Status: Indiana University Matrices Enhancements Still in progress. They have a release in mid-August. It is holding up some other changes, like the Montreal work. They need to be working off the IU changes.
Reporting Strategies. There is a link on the Reporting Strategies page to a feature template for UM stuff. Serensoft, using the data warehouse functionality, put in data in a way that can be accessed easily. IU tools run against the live database rather than the data warehouse. Part of the nudge for this page came from Teggin - are all these approaches really different? Lynn will add power point from her session at the conference.
Status Update: Finer Grained Document-Level Matrix Permissions CRIM has developed them and wants to merge them to trunk. They have completed a functional spec. People should look at it so we can discuss it next week. Is it acceptable to IU? 2.7 release?
Page Composer delayed by UM mission critical work. What's new: Autosaving has been improved. Helped by a fix that is not yet in 2.6.x. Will try to get it in 2.6.1. Or you can use a patch. Theme picker that shows a preview. Can have multiple pages with multiple subpages.