Meeting agenda: http://lists.osafoundation.org/pipermail/design/2006-July/005080.html

Introduction:

• Today's design session is going to be a little different
• Context: Huge discussion on the list: http://lists.osafoundation.org/pipermail/scooby-dev/2006-July/000628.html
• Not talk about whether we should merge and related interop and product strategy issues
• Instead discuss ramifications for UI, target users and usage scenarios

BCM Speaks:

• End-users interact with cosmo via:
  • Sign up for an account
  • Once you've registered --> Account page
  • Account page: Home directory URL, Tells you settings to plug into Chandler to enable sharing
  • Link to change password
  • Link to browse home directory
  • UI is raw, no real design work
  • What's in the directory, grant and revoke tickets
  • Smart enough to distinguish between directories versus calendars versus events
  • Atom feed
• Merging with Scooby: Augment and replace what we have now
• Take the capability of browsing home directory...make it more like browsing collections with Chandler
• Different view based on what Kind of data you're looking at (e.g. list versus calendar)
• Can communicate to you and others the URL to the shared collections
• Set preferences
• Potentially manage ACLs

• Account management for Administrators
• Create new accounts
• Edit accounts
• Delete accounts
• Browse anybody's home directory
• Grant and revoke tickets
• Potentially manage ACLs
• Status dashboard
  • Operational tools for getting sharing data
• Set system-wide timezones
• Customize notification text of email messages (may not have UI)
• Edit config files (no UI)

• Need to star features that don't have UI

Question Does Scooby just have these components? Is there a separate UI for different Cosmo users??

• Cosmo: need to be able to browse all of your collections, not just calendars
• Web server directory listing
• Administrator Scenario: User is abusing their quota. Need to nuke some of their data.
• Admins probably want to look at a tree of content in the server
• Run reports on sharing service
• Not all of this has a Web UI

Question Is there a cosmo user that is not in the target user group and not an administratory

• Not an ecosystem user
• Not an administrator

• Developers using Cosmo to plug into a 3rd party client (e.g. Evolution)
• Like the Repository viewer in Chandler

Large-scale administrators versus Small-scale adminstrators

• Large-scale need scripting functionality
• Small-scale need OOTB simple out of the box web UI with minimal configuration

Developers

• Need a simpler UI
• See larger amounts of data
• Consume the directory index
• You want to see 'last modified on' date, rather than the 'date received' for messages or 'start time' of an event.
• Doesn't care about contents of resource
• Care about item properties and less about user semantics of contents

Evolution users

• Want to know how to configure their Desktop client to Cosmo
• Account management
• Client configuration information

• 2 scenarios:
  • Running your own Cosmo
  • Using our Hosted Service

Question Can you rip Scooby out? Can you run Cosmo without Scooby? What is Scooby anyway? Ecosystem UI? Browser UI? Admin UI?

• Define products around target users.
• We want people to use the front-end to acce

• Scooby: Subscribe to remote calendars

Question What do we call this?

• Cosby is the project
• What are the products?
  • Ecosystem user
  • Browser UI user
  • Administrator user

Browser UI

• QA needs, need to see every field
• Different from end user needs and usage scenarios

There are things we need to do in the backend to support 3rd party CalDAV clients

• e.g. Scheduled data refresh push
• It's a matter of prioritization

Question What clients do we want/need to interoperate with: http://wiki.osafoundation.org/bin/view/Documentation/CosmoEndUser#Supported%20Clients

• Chandler
• iCal
• Evolution
• Lightning: plugin for Thunderbird (has more momemtum than Sunbird)
• Sunbird
• Google calendar
• Custom clients that other people develop
• WebDAV clients: Remote folders, content items would show up as individual resources
  • Alternative to the browsing interface
  • Web folders, Network Neighborhood, Cadaver. Finder
  • Nautilus on Linux
• Not used for end-user task management workflows
• Alternate way to do task management? or a way to do debugging?

Question Is this the same for the Chandler Repository Viewer?

Ted People are going to want ways to get data out of Chandler and sync it with their apps

Katie Does we need a repository viewer to get data in and out of Chandler?

BCM Parcel developers need repository viewer to check newly created items

Katie Retracts statement that Cosmo is more of a platform/data hub and therefore Cosmo's needs for a generic data viewer are more compelling

BCM Like Firefox's javascript debugger

Question Would ever want to access this generic data management view? but you're not an administrator? YES.

Question Are browser UI and WebDAV client users trying to do the same kinds of things?

• Difference: WebDAV client users are running scripts
• Mashups? could be done with either.
• WebDAV clients are primarily used to make file sharing easier
• Pieter doing filesharing with Sheila via file sharing
• WebDAV client has an augmented feature set relative to the Browser UI

Next actions

• BCM to propose a vote on the cosmo/scooby merge
• Primary stakeholders make the decision: BCM, John T, Bobby, Matthew
• Voting is a polling technique

• What's the next logical discussion to have. Wait for John T to come back and after OSCON
• Summarize Cosmo/Scooby merge thread: John T?

Question How do these target users and usage scenarios speak to the merge?

Answer Clarifies open questions about how UI grows on both Cosmo and Scooby

• UI for Ecosystem end-users, calendaring, task management, collaboration scenarios
• UI for administrators
• UI for browsers and debuggers
• Distinguished from the server product and the desktop client product

Orthogonal to the merge issue

Need meeting for Project planning issues

• QA and Release issues
• Architectural changes...impact on product planning schedule?

-- MimiYin - 18 Jul 2006