Cosmo Design Session Notes:

• Atom/GData
  • foundation for Mashups, integration
  • who might use it?
    • "Any developer, scripter" who wants to get information in and out of Cosmo
    • but who are the end-users of THOSE developers
      • answer: we don't know, but it opens to doors to new uses of Cosmo which we cannot envision right now
    • Mimi: two different understandings of "Data Hub"
      • "Data Hub" in the sky (on a server)
      • Lots of different clients
  • possible use cases
    • firefox plugin to "grab" events from a page and upload to cosmo
    • website pulling events from cosmo
    • CRUD operations (Create, Read, Update, Delete)
  • Mimi is concerned about redundancy of technologies - i.e. Why CalDAV AND GData?
    • Jared notes that dev's seem happy that there are multiple ways to do things, designers are not
    • Different technologies have different strengths
      • CalDAV is good for desktop calendar apps
      • Atom/GData possibly better for mashups.
      • Atom is not specific to CalDAV

• Import Existing Data
  • ability to import data from iCal (presumably .ics files)

• Account Activation
  • account not activated till email confirmation

• WebDAV Principal Support

• Cosmo/Snarf as a windows service
  • people running Cosmo on a windows box would need this for proper OS integration
  • could be done externally

• CardDAV^?
  • it's almost done
  • just need to port to new hibernate codebase

• Cosmo Use Cases
  • user running cosmo on their own
  • small workgroups using hosted service
  • small workgroups running cosmo on their own(ex. lpfi)
  • isp/oem
  • enterprise
  • people developing for cosmo

• Katie raises the question: Do we think that people running their own cosmo's should be supported for the beta time frame?
  • Jared thinks it's risky NOT to support this - could be excluding groups who won't use hosted service
  • Priss makes similiar point, many small orgs want to host their own data
    • but she says not necesarily for beta

• Decisions To Be Made:
  • what's in/out for beta
  • what's the strategy for 1.0

Notes taken by BobbyRullo^? -- Revision 1.1 on date Tue, 05 Sep 2006 15:59:25 Local

---

Cosmo features

Priscilla’s Notes on the electronic whiteboard

• 060905cosmoDSmtgNotes.pdf: Design session notes

Atom/GData

• Dev/Scripter (or their users)
• Understanding the user
• Example: events on the web -->go to BCM's Calendar --> Drag N Drop to BCM's calendar

1. Cosmo as a data hub UI ie. Button on firefox extention -->go to BCM's Calendar easier
2. ie. Friend's site pulling data on to their blog

Jared:

• Decouple client from the server people to write alternate UI
• foundation blocks for themselves
• support
• ie. Flicker API --> iPhoto extension - common thing is people running over the web

Use Case - event/calendar data

• email submission
• ie. AIM Bot 7PM dinner
• No UI - reuse UI AIM
• Update data base --> too many clients
• Quick event
• Read
• Update
• Delete

• Dev - multiple ways of doing things -GOOD
• Design - multiple ways of doing things -BAD

• Alt Atom & not do CalDAV? Most likely NO.
• Offer both --> better
• Rich desktop CalDAV Ted says no.
• Web app -->Atom
• awareness--> Atom --> no specific to calendar

• BCM's Picture of the Target User

  CalDAV	Atom
  Older, suit type person	Younger, 20 something
  	intern project

• couple weeks
• not if we should do this or not
• not an end user concern

Card DAV

• Personal address book server
• LDAP --> Grant permission
• VDAP --> sync to Thunderbird address book
• In the code base --> need to merge the code *couple of weeks.

• GData another generic calendar to get

Use Case

• Run Cosmo on their own
• Someone like Jared
• University (legacy issues)
• Couple in the home
• Dev against Cosmo
  • Data in/out --> what are

• University
• Enterprise ( Alternate to MSExchange)
• ISP Hosting
• OEM
• Technical Enthusiast
• Small Group
• Hosted service --> users
• Longer term goals --> tech enthusiast
• University --> past relationship

Beta - Support Jared, he is the target user --> what's in the beta 1.0 stratgy Small group? Many user types

• Hosted service
• Hosted themselves (not for beta)
• Higher bar for installation requirements are higher
• May not be the same as the tech. enthusiast

LPFI --> how to support for them?

Next steps:

• What’s in/out for beta
• What’s the strategy for 1.0 --> PPD to send proposal to the list
• Mimi/BCM to meet more to go over questions

-- PriscillaChung - 11 Sep 2006