2010-11-01 Conference Call

Owned by Former user (Deleted)
Last updated: Jan 05, 2011 by Former user (Deleted)Version comment
3 min read

Meeting Minutes for Nov. 1, 2010

  1. Community Updates
    • OSP JIRA review status update. Chris' giant project is over, so he will be going into Jira and cleaning things up this week.
    • Teaching and Learning (T&L) Group updates. Specialized visioning meetings still make sense to continue as a separate effort. A good starting place is what to name the mini-specs.
    • Status updates on OSP Help UpdatesJan is about to send a letter to Elizabeth and Jonathan to say that 2.6 help is done. But are there any Sakai properties that are different, and if so, are they updated in the Sakai properties page. EMail notification has some changes. Sakai properties Confluence page needs to be updated to 2.8 so that the Help page can just point to it. What's left is 4 sections of text that need to be updated for 2.8: Matrices, Evaluations, Wizards, and Portfolios.
    • 2.8 QA Status Test Scripts, 2.8 QA Signup with links to test scripts. QA3-US server is up now as a 2.8 server. Next time a tag comes out, he will restore the 2.7 database and then run the scripts, so all material created in the meantime will be lost.
    • Sakai 3 General Status Updates
      • Virtual Meeting for Portfolio Visioning in Sakai 3.0
      • Sakai 3 ePortfolio
      • Groups have been writing up scenarios and figure out what personas are needed for them. Effort will be made to map scenarios to existing personas. One problem is that personas tend not to be in the same department, which Portfolios tend to require. A few new personas will have to be created.The Taxonomy group needs some help -- what do we want to call what for Portfolios?
    • Independent OSP release cycle: action items moving forward. There won't be any movement on this for a while.
    • Reporting. First meeting of the Reporting group just took place today. They want to nail down what are some desirable reports. What tools do we want the reporting data to feed? Will meet again next Monday at 10am. Reports don't have to be in a separate tool, they could just be another page on a tool, at least for progress info (how many cells a user has filled out v. what did they write).
    • Recruiting OSP resources for QA or other activities. Debbie from IUPUI: often at a loss as to how to contribute due to lack of background. Should we have one person volunteer to be the go-to person for testing questions, mentoring others. Noah: In a separate place keep track of available work and match it with people who have skills or time. A sort of job board. Jan: It does work to set up a structure, invite people, interact with them. Sure, people can get busy, but there is a lot of volunteer energy in the group. Maybe it would be good to have a list of committed OSP people so that new users can contact them? No, better to have people mail questions to the list. OSP landing page should be updated to make it easier to join the OSP mailing list. Is it possible to link directly to the Portfolio list page, rather than to the top level Collab page? Chris will revisit the page and see what links can be added to make it more useful to new users. It's almost impossible to find out what the Sakai Portfolio platform is. We need someone to do some marketing. Even the most rinky-dink portfolio tools out there have better info about their projects. This is important enough to be part of the permanent agenda. Three Canoes is renting some cloud space for a demo server. We could link to that. How can we get more developer resources? VA Tech may be ramping up, since they want all freshmen to have a portfolio.
  2. Sakai/OSP Maintenance Status (Bug fixes can be verified on the following QA servers Nightly Build (HSQLDB) or Nightly build (Oracle))
    • SAK-18766 Erratic Stickiness of Group and User, No page update after Manage Status in Matrices tool (UMICH)
  3. Sakai Development Status (next major release cycle)
    • SAK-14401 OSP Tools don't respect language/locale preferences (only when english is not the default locale)
    • SAK-19184 OSP Tools don't respect language/locale preferences (only when english is not the default locale) - Part 2
    • SAK-16693 Roster Synchronization (pending adding optional flag, branch, test server review and trunk merge). Tabled for 2.8, will try for 2.9.