2009-11-11 Product Council Meeting

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

1. What we're prepared to say about Sakai 2 tools

technical review protocol
started by focusing on graduation to maintenance
questions for a production deployer
4 categories of questions
not driving toward checkboxes, not quite a scorecard
general technical items, code maintenance and metrics, production worries, interoperability
looked at GB2 as a first pass, to see how onerous
used provisional criteria and scorecard to see what could be reused or added to
next steps: get PC to take a look and see if they feel reasonable
UX on a separate checklist? yes
didn't see questions about whether sakai participated in essential Sakai services (e.g. Search)
would like to get these things itemized, descriptive rather than necessarily dispositive
is this project introducing a new capability which should be supported by other tools?
this has become quite Sakai-2 specific so far, or can we carry this through to Sakai 3? May want to fork it on the level of detail.
would be an interesting exercise to do for Sakai 3 right now, to understand what the equivalents are on a similar set of principles.
several of these tools now have a relationship with the rSmart distribution ... if there are remarks to say from someone outside, should that just be plugged in?
approval process? emphasis on documentation, but the presumption is that things will go through unless something serious comes up during review and in community discussion
a bad idea to dilute the distribution aspect of our licensing