2010-2-10 Product Council Meeting

Owned by Former user (Deleted)
Last updated: Apr 28, 2010Version comment
2 min read

6pm GMT / 1pm EST

Phone number: 1 (812)856-7060
Internet: 156.56.240.9
Room code: 348#
Password: 72524#

Agenda

  1. Review of SPC report
    • Consensus on what we'd like to improve from the 2.7 process
    • Consensus on goals between now and the conference
  2. Practical steps toward goals
  3. Review of accessibility statements (Eli)

Attendees

  • David Goodrum
  • Stephen Marquard
  • Clay Fenlason
  • Michael Korcuska
  • Nate Angell
  • Noah Botimer
  • Michael Feldstein
  • John Lewis
  • Eli Cochran
  • John Norman

Etherpad
SPC Report for January 2010
Accessibility Statement

Notes

Goals between now and the conference:

  1. Shepherd new Sakai 2 tools/capabilities through the process
  2. Facilitate Sakai 2 -> Sakai 3 transition planning
  3. Develop criteria and process for moving from incubation to product development (This was left ambiguous as the product development process was defined).
  4. Facilitate development of objective criteria for S3
  5. Identify 3.0 functional target functional goals and criteria
  6. Review of PC activity and recommendations going forward. Test whether expectations are being met.

Practical steps for achieving S3 goals:

  1. Identify areas where criteria need to be developed
    • Accessibility
    • UX
    • Functional completeness/coherence
    • Back-end technologies
    • Front-end technologies
  2. Stakeholder communities that might help do the heavy-lifting in developing the criteria pertinent to particular stages.
    • Accessibility WG - wg very active now, if small. Could move quickly and effectively
    • UX - should it be a criteria that user testing is conducted and critical issues are attended to? Would need to be careful about what sort of testing and the objectivity of results.
    • T&L group developing functional themes, which will be fleshed out as narratives or manifestos. Perhaps the Product Council should affirm and adopt these as providing guidance for functional coherence and completeness?
  3. Other exercises:
    • BA mapping screens to functional goals (BA), locating gaps
    • identify and communicate fundamental interaction models - design work
    • Metrics for performance, security, test coverage of Nakamura, documentation
    • Client-side technologies - need good technical review, but our community capacity in this area is limited
  • PC's role includes turning criteria into something timely and actionable

Next Steps

  1. Preliminary Assignment 2 review
  2. Preliminary Incubation -> Product Development criteria
  3. Set up Sakai 3 accessibility testing with accessibility WG
  4. Facilitate T&L development of functional categories and manifestos
  5. Develop our UX criteria - needs thinking from the ground up
  6. Develop technical metrics for Nakamura and client-side technologies (who can do this?)