Schedule
OSP 2.5 will be synchronized with the Sakai 2.5 release with a current target release November 2007. The code freeze for the release is September 15th, 2007.
Existing JIRA Summary
Please review the summary of all OSP JIRA Issues.
Planning Meetings
A two-day OSP 2.5 Planning Meeting at U of Michigan was held on May 13th (evening)-15th, 2007 in Ann Arbor, Michigan.
An additional OSP 2.5 Planning Meeting in Amsterdam was held on June 15th, 2007.
Emerging 2.5 Team
In addition to the team below, there is a OSP community service team evolving that will lend direction and support to the release process. More will be posted on this soon
Project Management Team:
1. Functional Leadership: Sean Keesler, Janice Smith, Darren Cambridge, John Gosney, Melissa Peet, and Tony Camilli
2. Development Lead: Beth Kirschner
Functional Experts and Business Analysts:
- Darren Cambridge
- John Gosney
- Lynn Ward
- Janice Smith
- Sean Keesler
- Bas Toeter
- Tony Camilli
- David Goodrum
UI/usability leader
- Gonzalo Silverio
UI Designers
- Still have Critical Need - Sean Keesler & Kristol Hancock
Java Developers
- rSmart Developers
- Chris Maurer (100%)
- Another IU developer
- Beth Kirschner (50%)
- Jim Pease (25% on GMT)
OSP Library Development/Website and Confluence
- Will Trillich
- Noah Botimer
- Erik Scull
- Wende Morgaine
- Nate Angell (Confluence
Nate doesn't know what this means, can someone explain?) - LaGuardia participants
XML/XSL/Scripting/etc.
- Gonzalo Silverio
- Erica ?
QA Leads
Responsibility of functional leadership team
Requirements area (write test cases w/requirements)
- Sean Keesler (GMT)
- Jan Smith (Reports)
- Gonzalo Silverio (UI/Usability)
QA Testers
Participating institutions will provide QA testers - IU, UM, George Mason, rSmart, LaGuardia, Syracuse, SVSU
Documentation tools & library
- rSmart?
- Sean Keesler
- John Gosney
- Michigan - Zac Monahan & Melissa Peet use cases
High Level Scope
Each of the items below represents a high-level scope item. These are intended to frame the release and focus our efforts on elaborating requirements that fall into scope, and postponing work on requirements that fall outside the scope. Once requirements are complete, the set of agreed upon requirements will be posted.
Example focus areas include:
- Integration with other Sakai Tools
- User Interface focused on (student-centric) workflows
- Deeper integration of the Goal Management tools with OSP
- A well-populated community library
Requirements
Specific requirements are written up in JIRA and summarized in the Proposed OSP 2.5 Requirements page (currently under review).
Design
An initial plan is to work on a redesign of the OSP tools during the 2.5 development process so that the plan will be ready to implement by the 2.6 development cycle
Testing
More attention needs to be paid to this and will be the focus of more conversation in Amsterdam