SAK-17940 Auto-select of Portfolio Forms causing intermittent problems
SAK-14401 OSP Tools don't respect language/locale preferences (only when english is not the default locale). Beth looked at this. It is a broad, shallow bug. She fixed it in OSP, which has never observed internationalization best practices. The fix is trivial, but involves changing a lot of code. Any developer who touches a JSP file should fix the internationalization. If you are fixing something functional, check in the change to the JSP, then as a separate commit, make the internationalization change.
SAK-18458 Need a MatrixManager.getNode signature that doesn't check locks for scalability. Noah opened in last couple weeks. UM was running at scale with a few dozen sites and a few thousand forms. Running reports against forms involves checking for authorization, but one check doesn't actually need to be done and really slows things down. Checked into trunk. Will go into 2.7 as appropriate.
SAK-18459 OSP role-based authorization is far too inefficient. The number of sites someone is in impacts looking at a form in the matrix. It progressively slows down with more sites.Should go into 2.7.1. Most apparent for reviewers.
Sakai 2.8 Development Status
SAK-16557 Indexes are missing on OSP tables with Oracle
Teaching and Learning (T&L) Group & requirements gathering. The two-day session went very well. The lenses aren't quite done, but will be presented to the Product Council later in May. The committee is well on the way to finishing. David Goodrum created a concept map that may be used to present to the Product Council. Workflow is the next topic they were planning on working on, but the may get direction from the Product Council. The lenses are high level, the spreadsheet is granular, but they really need a middle level to be useful. The page is called Seven Lenses/Themes. The plan is to put everything together in confluence.
Documentation & Communication
Moving content from http://osportfolio.rsmart.com to www.sakaiproject.org. Beth will send Sean an email for an update.
Status updates on OSP Help UpdatesThere are only a few more things to review. Brian Dashew has been doing it. After this is finished with KB, somebody will pull updates from the Knowledge Base and put them in subversion for trunk, so it will go out to everyone.