2010-3-10 Product Council Meeting

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

6pm GMT / 1pm EST

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

Agenda

  1. Updates on incubated projects
  2. Community Criteria updates
    • T&L learning capabilities
    • Accessibility WG
    • Technical criteria
    • Moving from incubation to product development
  3. Localization

Attendees

  • Stephen Marquard
  • Noah Botimer
  • Clay Fenlason
  • Eli Cochran
  • Michael Feldstein
  • Max Whitney
  • Nate Angell
  • David Goodrum
  • Lois Brooks

This meeting's etherpad (Meeting notes have been copied from EtherPad below. The EtherPad service will be going away on May 14th)

SPC Report for January 2010
Last meeting's etherpad: http://etherpad.com/iz7w7GClY6

Meeting Notes

(Reminder) GOALS:

  • Shepherd new Sakai 2 tools/capabilities through the process
  • Facilitate Sakai 2 -> Sakai 3 transition planning
  • Develop criteria and process for moving from incubation to product development (This was left ambiguous as the product development process was defined), with a particular focus on S3.
  • Facilitate development of objective criteria for S3
  • Review of PC activity and recommendations going forward. Test whether expectations are being met.

AGENDA:

1) Updates on incubated projects
 
 Assignment2 (Clay):

  • See http://confluence.sakaiproject.org//x/uAcQB
  • Turn It In integration
  • Portfolio integration
  • Functional gaps: forthcoming document that will be shared
  • A good candidate for a potential 2.8 or independent release in second half of year
     
     Sakai 3 (Clay and Max?):
  • Moving toward managed project coordination model
  • NYU getting deeply engaged
  • Stand-up meetings for UI development and design btw Cambridge and NYU. Not an open meeting just yet, just trying to build alignment along similar timeframes
  • Short deadlines has resulted in some compromises and potentially throwaway
  • Design work still very active, and some fundamental things still being worked on (content in particular).
     
     TinyURLService:
  • See Steve's comment at the bottom of: http://confluence.sakaiproject.org//x/KRgQB
     
    2) Community Criteria updates

 T&L learning capabilities (David, Clay):

  • in process of refining 7 themes (lenses)
  • working out a couple examples of what the next step would be - writing conceptual piece, with grading manifesto as a model
  • writing short user scenarios
  • would be good to meet with product council and talk over the work that's been done
  • may be some questions about content as this comes together, but the format looks helpful
  • should meet in the next month

 Accessibility WG (Eli):

  • statement put out to general community for comment, no comment has come back
  • next step to flesh out specific goals, with some specific technology recommendations
  • resource still going toward 2.7, and then it might shift over soon
  • question about whether there's a tension btw current approach and the goal of simplicity for UI development. May be an issue of how we're using Fluid skinning system, too soon to have a conclusion, but there may be a potential issue that will need more attention.
  • rhetorical marker: may need to give attention to rich text editors - whether they are the right solution
     
     Technical criteria (Max, Stephen):
  • first task: document technical infrastructure so far, explain choices.
  • New load testing node up at NYU
  • UCT has a S3 strategy proposed - new experimental functionality by December timeframe
  • looking at assumptions around scale and dimensions of scale
  • Much of S2 technical worksheet might still be useful as a starting point
  • Can do more work on this over next 2 weeks
     
     Moving from incubation to product development (Michael F, Nate, Noah):
  • unclear what this means for S3, first task to clarify
  • a meaningful bar? S3 in production?
  • first few milestones defined in terms of use cases
  • what product development means as an activity will evolve
  • one of the things we thought the stage was desirable was reducing uncertainty. Project management mechanisms for bringing more reliability.
  • S3 could be going into product development if, say, 3 committed institutions (multi-institutionality) were going into development with a credible resource commitment and an approved plan (formal process). An endorsement of all this. Then at the other end: did it turn out as we expected?
  • do we leave out criterion of milestones that are moving toward a quality release if we focus only on process?
     
     UX (Eli and Noah):
     
     3) Localization

    Next Steps