2) Sooby landing page - where are we with getting this finished
3) FLOSS usability spring in late May...should Scooby go as a project
4) Performance goals for 0.7 - survey results and next steps
5) Next steps on product planning - target user, user problem
6) Stamping next steps
7) Email brainstorm - 0.7
Design session next week (April 11th)
A couple of options
implementation details - domain model conversation
email brainstorm
Scooby landing page
Pieter and landing
FLOSS usability spring in late May...should Scooby go as a project
May 19th, 20th, 21st
Last weekend in May.
Yes we should do this.
Matt? He is aleady coming to OSAF in early May
John? Yes, we could send John as an alternative
Can Sheila go?
Have Eugene come for lunch or sit in on a design session
D-camp
Who is going to go? Ted, probably Katie and perhaps Mimi.
Performance goals for 0.7 - survey results and next steps
Next steps:
work on representative data set based on survey results so far
take some real calendars, office calendar, free-busy, shares etc
scrub office calendar data
send out a note to the list with summary and next steps
take a look at the current list of performance scenarios - addtions/removals
brainstorm a set of dashboard scenarios
Next steps on product planning
Katie created the strategy list
Need to get people on the list - Katie
Katie will send an intro to the list framing the product planning proces
Priorties discussion - what is the next step to put this on the list
Mimi will follow-up Katie's email with a priortization of things that will affect the plan
List will be used for Marketing, Product Plan and Strategy Discussion
Marketing/Competitive Analysis - Sheila is scheduling a kickoff meeting
After the meeting - send an email to the list with spreadsheet/process etc
Mimi has written up notes for Lori, Francesca interviews - send to the list
Pending interview with SF Moma person
Collect all old interview information - past year - put in a central location on the wiki. Follow-up with a design session where we model how the ecosystem would solve these people's problem
Target this for the week after the email discussion - April 18th
Marketing stuff - look at apps for neat integration of data
Stamping Next Steps
Answer Alec's questions on the list
Let discussions percolate on the list - handle questions
Ted can initiate domain model questions
Email 0.7
Send/Receive bugs
Stamping bugs
Fix stamping architecture - data/domain model
Unstamping bugs
Attributes maintained
3rd party parcels screw up
Task stamp - alarms/none
Markup bar not show recurring events as stamped
Task stamp need to be preserved over email
Stamp/Comm -> status for email - sent, read, etc
Send/Update toobar button
Sent to New to: katie(*)
Addressings - handle invalid email addresses
Who/what appears in what column * Account dialog work * Reply, Reply All, Fwd
Email 1.0 Brainstorm
Scenario #1
Ted/Julie's home tasks/calendar
PPD Team tasks/calendar
Mitch/Esther - Esther's tasks, Mitch's calendar
Personal task/cal
Small number of items
Hand selects or creates manually
Fully hosted OSAF solution
Scenario #2
Collaboratively manage discussion list/feeds
Not all of somebodies email
1 folder
auto-generated 10-20 items
3-5 active managers
50-100 subscribers
Not hand selected - subscribe
More organization - tagging/social labelling
You can use any client and we can window onto that
A: clean slate, B: window onto other accounts
Scenario #3
Desktop gmail
Performance
Org structures
Sophisticated editing tools
Filtering
SPAM
Spellchecking
Better reading environment
Good search
Could use OSAF server - hosted by OSAF
Scenario #4
Replace Thunderbird
Assumptions:
#1, #2 - people will have a primary email account somewhere else
#3, #4 - people will replace their email client
Interaction between design and implementation - start the discussion