Child pages
  • Working Groups
Skip to end of metadata
Go to start of metadata

Status Summary for Working Groups (WGs)

Key:

  • The green/yellow/red/white button at the beginning of each row is a quick indicator reflecting both how things are progressing relative to an activity's stated goals and how up-to-date the Status Summary message from the activity leader(s) is.
    • On target.
    • Some concern over progress or status out-of-date (more than 1 month since last update).
    • Not making appropriate progress or no recent status update.
    • Activity not directly tied to Sakai releases, see associated website for status and release information.
  • Title is the name of the WG.
  • Status Summary contains a short summary of the WG's current or on-going activities.
  • Additional Information lists the activity leads, and provides a links to the WG's Confluence space and Collab site, if they have one.

 

Title

Sakai 2.5 Plans

Additional Information

WG: Accessibility

06-Jun-2007 The Accessibility Working Group is readying Confluence for the next cycle of accessibility evaluation and testing. The tentative dates for reviewing Sakai 2.4 are from June 23 to July 20, with a kick-off meeting June 23 at 10:30. During the last review period, thirty-five reviews were done by the accessibility team at Indiana University!

Find out more about the 2.4 review and sign-up to review a tool at: http://confluence.sakaiproject.org/confluence/x/uq4

Lead(s): Mike Elledge

Confluence_Space

Collab_Site

WG: Course Management

14-Sep-2007 As of 2.4 status, work in the WG has reached its final planned milestones. Work could be picked up again given more will and resources.

Lead(s): Marc Brierley

Confluence_Space

Collab_Site

WG: Commercial Affiliates

Unable to render {include} The included page could not be found.

Lead(s): Chris Coppola

Confluence_Space

Collab_Site

WG: Data Analysis

08-Aug-2007 New event log community resource created in Confluence - Continued collaboration with SiteStats team and efforts to improve event logging system-wide.

Lead(s): Steve Lonn

Confluence_Space

Collab_Site

WG: Design Patterns

Unable to render {include} The included page could not be found.

Lead(s): Marc Brierley

Confluece_Space

No Collab Site

WG: Documentation

Unable to render {include} The included page could not be found.

Lead(s): Clay Fenlason

Confluence_Space

No Collab Site

WG: Framework

Unable to render {include} The included page could not be found.

Lead(s): Glenn R. Golden

Confluence_Space

Collab_Site

WG: I18N-L10N

Unable to render {include} The included page could not be found.

Lead(s): Beth Kirschner, Alex Ballesté

Confluence_Space

Collab_Site

WG: K-12

Our focus right now is on the following:
  • Create a community of current K-12 Sakai users
  • Develop a method of sharing K-12 resources
  • Develop a CLE model where students throughout the world can engage each other in an safe "walled garden" environment
  • Explore opportunities to further develop the K-12 Sakai community

Lead(s): Michael Korcuska

Confluence_Space

Collab_Site

WG: Licensing

Unable to render {include} The included page could not be found.

Lead(s): Megan May, Peter A. Knoop, Chris Coppola

Confluence_Space

Collab_Site

WG: Migration

Unable to render {include} The included page could not be found.

Lead(s): Mark J. Norton, Zach A. Thomas, Aaron Zeckoski, Mike Osterman

Confluence_Space

Collab_Site

WG: Performance

Centralized Performance Testing Goals

Limited progress has been made to date, however designing a "generic" (non-campus-branded) Sakai testing environment continues to be the primary goal of the working group.

In the meantime, organizations involved in performance testing are encouraged to share their testing scripts, plans, and results on the WG:Performance Confluence site.

University of Michigan is working on a proof of concept of such a generic testing environment, when not busy actively conducting tests for campus needs. Thus far we have a working 2.4 Sakai build and are busy using Alan Berg's provisioning scripts to populate it with sites and tools. This phase is expected to involve some script tuning to get the right combination of data input and output to enable iterative testing.

Other campuses continue working independently on developing tests to meet campus requirements.

Lead(s): Linda M Place

Confluence_Space

Collab_Site

WG: Podcasting

Unable to render {include} The included page could not be found.

Lead(s): Steve Lonn

Confluence_Space

No Collab Site

WG: Programmer's Cafe

23-May-2007 Awaiting update from Project Lead(s).

Lead(s): Thomas Amsler, Aaron Zeckoski, Bill Crosbie, Mike Osterman, Zach A. Thomas

Confluence_Space

Collab_Site

WG: QA

Unable to render {include} The included page could not be found.

Lead(s): Megan May

Confluence_Space

Collab_Site

WG: Release Management

Unable to render {include} The included page could not be found.

Lead(s): Lance Speelmon, Andrew Poland, Megan May, Peter A. Knoop, Brian Jorgensen

Confluence_Space

No Collab Site

WG: Requirements

Unable to render {include} The included page could not be found.

Lead(s): Mark J. Norton

Confluence_Space

Collab_Site

WG: Sakai Community Practices

Unable to render {include} The included page could not be found.

Lead(s): Mark J. Norton

Confluence_Space

Collab_Site

WG: Sakai Foundation Website

Unable to render {include} The included page could not be found.

Lead(s): Susan Hardin, Aaron Zeckoski

Confluence_Space

No Collab Site

WG: Sakai Software Project Courses

Unable to render {include} The included page could not be found.

Lead(s): Aaron Zeckoski

Confluence_Space

No Collab Site

WG: SCORM

Unable to render {include} The included page could not be found.

Lead(s): Jon Gorrono

Confluence_Space

Collab_Site

WG: Triples

Unable to render {include} The included page could not be found.

Lead(s): Jim Eng

Confluence_Space

No Collab Site

WG: User Experience Roadmap

Unable to render {include} The included page could not be found.

Lead(s): Tim Archer

Confluence_Space

No Collab Site

  • No labels