Thursday March 30th, 2006 Staff Meeting

Agenda

Question of the week: Given our assets (the design and engineering work we've done for cosmo, scooby and chandler), what do we have that is unique and valuable to users? (Alternatively, what are we close to having that will be unique and valuable to users?)

Yes, this is a big question (the million $ question, as Mimi puts it). We're not looking for the definitive answer here at the meeting, this is just an exercise to get people thinking.

• OSAF strategy projects (Katie)
• Self assigned projects update (Philippe)
• Demo of foxmarks metrics (Jared)
• Demo of Chandler preferences (Alec)
• Demo of receiving invitations in Chandler (Bryan)

Question of the week:

• David: Issues of data sharing
• Philippe: Expand data
• Katie: Shared task management, e-mail unique and valuable
• Jeffrey:kumquats and pomegranate juice is not a good combination
• Aparna: cross platform, sensable product, calendar sharing, free busy
• Andi: All of the above
• Jed: Transition data
• Priscilla: Sharing for personal data
• Jarred: multi machine, read write
• Grant: sharing is most compelling
• Mimi: reliable, peer to peer feel, who either don't care about data to actaully care about it to share about it w/ other people
• Alec: user effort w/ Python, smart dev. community pretty unique
• Mikeal: parcel archetecture useful, mashups
• Bobby: Don't know of any open source products that have desk top
• Heikki: I agree sharing is most important in the very short term, but I think the fully integrated email, calendar etc. data solution in the next 2 years would be a big hit
• Pieter: Reference to open source/standards page and how that is going to work
• Brian K: Free app that runs on 3 platforms, local networks for mom & pop shops
• Reid: Chandler sharing calendar platform ina family
• Sheila: Sharing compelling, dashboard to make me use Chandler
• Morgan: Sharing. Million different ways?
• Philip: Open platform, start distributing plugins start people being about to dev. extensions
• Bear: Calendar data from Cosmo, anyway you want, and use that data to manage that data in calendar
• Matthew: Open access important, anybody to use and contribute
• Ted: High volume of data, what kind of information I'm going to be able to store in my
• John T: Cross platform solution.

OSAF Strategy

Currently there are three projects going on:

• Business plan - Mitch will talk about it next week
• Product plan - PPD team is working on
• Market research - Priscilla, Pieter and Ted is working on

The process for the planning strategy is not going to be public, only within the OSAF (core team is the steak holders). Creating a mailing list and an internal wiki.

Ted comments: This is really the beginnings of creating this process down. With the public press, while we are figuring out what we want to do and not be distracted by the articles. From previous experience, lesson learned. Limit to the core Chandler community. Not to the public who do not have a steak in what's going on.

Product plan

Purpose is to have a common target to define the 1.0 projects. Chandler, Cosmo, and Scooby, whatever sweep of prod

• 12-18 months timeframe, funding levels.
• identify who the target users are, roadmaps. Tenets, workflow, plan for staging, for those 12-18 months.
• first steps, elements of the vision at OSAF.
• Small work group, GTD., We'll be sending out to the whole stratgey list, and ask to prioritize them.
• What elelments are the focus in the 1.0 timeframe.
• Elements compete w/ each other, and we want to be clear, and a discussion
• Remind decisions on what was already made.
• List is coming soon

Mimi: Priortization is more about similar to sticky plan. What is doable in the 16 month time frame. Is it ok to just have potential and that it doesn't have to be fully functional.

Self assign projects

Philippe:

• Self assign projects start now
• List of collaborating projects -->add yourself to the list
• Information on the chart, project, owner, start date, compleation date if you manager has approved it?

Demo from Alec:

• New features added a while ago.
• Timezone is dropped out. It is now timezone free, Bryan Grant, Andi, lot of people are working on this
• Go to 'View' menu, yes I want to use 'timzezone'. And it appears in event details after selecting the time.
• This is a move closer to iCal model and be timezone free
• Also a new feature is the 'I can't see enough hours with in the day. Go to the 'view' menu,
• You can select a range from 5-12 hours. So you can show 6 hours in your calendar and experiment what is good for you to view your events.

Demo from Bryan:

• The last demo was sending an event from Chandler to announce about the film festival
• You wold receive an attachement to darg into the Chandler calendar
• This weeks demo, go to 'File', 'Get mail'
• Go to Chandler calendar to see the event sit on your calendar
• Not all issues have been addressed. A lot of work included Jeffrey

Demo from Jared:

• Analysis work done for Foxcloud using Cosmo
• Foxcloud is: A two way sync for bookmarks on Firefox
• Foxcloud analysis report, process into CNV files, 200 response code, put into file
• Take the last line used to report the number of users and sign ups yesterday
• Turn this data into a graph --> What we're hoping for is a view/tool for product managers.
• Access log, date stamp, 'cronolog' (time stamped files)
• All analysis is daily based.
• CSV files from Cosmo every night
• New sign ups. you can see spikes, daily active users, cumulative new sign ups, daily puts/daily active users
• Make changes the bookmark file in the next hr. will be stored in cosmo
• Weekly Active Users/total accounts, how many people continue to use the service
• Users experiencing internal servers error
• Admin will be able to see operations, graphs are a cheap way of getting an analysis
• Unique IPs/week
• Base metrics, basic model to create some file, done through analysis plugin
• Write into a simple shell script and plug into