Wow, what an opus. I'm going to start giving you feedback in pieces,
cuz it's gonna take me a while to digest the whole enchilada. :o)
Overview
Cosmo is a sharing server for calendar and other items. Cosmo is
also a calendaring web application to support Chandler users. This
document details the features for Cosmo 0.6.
Do we want to genericize Cosmo to say that: Cosmo is also the web
application piece of the Chandler small workgroup collaboration
product suite/service with support for notes, tasks, calendar and
lightweight communications.
Cosmo 0.6 will focus on the features based on the Cosmo target
user, the Casual Collaborator (CC). An example of the CC usage
scenario is an OSAF employee who is tasked to use Cosmo to put in
their paid time off (PTO) on the office calendar. We’ve selected a
set of features to implement based on this usage scenario.
This document will outline the following features:
Casual Collaborator
Time zones
Sharing
OSAF Administrator Features
Settings
Links to Technical Documentation on the OSAF wiki
Should we reframe it as workflows rather than features? Re: CC - Do
you mean the feature set that is intended to support CC usage scenarios?
1. Subscribing to a shared collection with Cosmo UI
2. Lightweight calendar collaboration
* Anonymous access
* Read-write collaboration
* Read-only collaboration
* Timezones
3. Account set-up and management
* Signing up for a Cosmo account to publish shares with Chandler
* Signing up for a Cosmo account to subscribe to shares with
Cosmo UI
* Managing account settings
5. OSAF Administrator workflows
6. Access to Administrator and Home directory browsing functionality
7. Access to Help on the project wiki
8. Access to technical documentation on the project wiki
Back to top
Casual Collaborator
Goals and Objectives
Is this where we want to talk about 0.6 as Cosmo's first dogfoodable
release for lightweight, aka casual calendar collaboration? Should we
define Casual Collaborator first?
+ 0.6 is the Cosmo projects first dogfoodable release. This means:
- Coherent account sign-up and account management
- Basic collection management: Renaming and Removing calendar
subscriptions
- Read-only view
- Time zone support
+ We hope to meet the needs of our target user, the 'Casual
Collaborator' someone who occasionally collaborates with the Chandler
target user: Helen the Hub. The CC could be Ivan the Individual
Contributor or Eli the Executive Assistant.
+ We believe this entails supporting the following features:
- Coherent subscribe workflows for both Cosmo and non-Cosmo users
- Anonymous access to view and edit shares.
- Ability to send email notifications to others about significant edits
Do we want to say who we're not focusing on? Although we will try to
support this person as much as possible, aka within the realm of
functionality we know we need for the CC.
+ Remote access for the Chandler user (Helen the Hub).
This section will outline the feature set to meet the Casual
Collaborator usage scenario. One of the goals is to allow access of
the Cosmo web UI with anonymous access. The CC will be able to edit
and update a calendar collection sent from a Chandler user. The CC
will then be able to notify the Chandler user about the changes
made on the shared collection. For 0.6, the notification will be
sent by clicking on a 'mail to' link to launch the user’s desktop e-
mail. For a future release it would ideal to be able to send
through the Cosmo UI.
In addition there will be ongoing improvements to Cosmo:
Start working on features which will compliment Chandler, for
example sharing format.
Completing ongoing features for the OSAF Administrator to host
Cosmo on osaf.us (hosted service).
The primary use case is 0.6 is to enable someone from OSAF to
easily update their PTO on the office calendar, using the web
client as an interface. Today, this individual would simply send an
e-mail to everyone at OSAF with PTO in the subject line and an
office admin (or in this case the executive assistant, Esther) is
responsible for updating an iCal version of the office calendar.
Eventually Esther’s time and the use of the iCal version of the
office calendar would be eliminated in the process and everyone
would update their PTO or other travel time on the shared read-
write office calendar.
Use Cases
Are these workflows rather than use cases? I know we haven't been
strict about this in the past, but it might be good for us to start
being more rigorous about design terminology? Use cases to me would
be more concrete, providing enough context to understand why a user
would decide to sign-up for an account versus edit the calendar
anonymously versus subscribe with Apple iCal.
User A does not use the office calendar but wants to be able to
view and/or edit (depending on the URL) the information in this share.
Should we separate out read-only from read-write?
Do we want to say 'ticket' instead of 'URL'?
User B receives the URL to the office calendar and decides to sign
up for a new account on Cosmo.
This seems like it would be more likely after the user has received
several tickets and finds themselves sharing multiple calendars via
Cosmo? Not sure if it's necessary to call that out here. But it does
User C receives the URL to the office calendar and wants to view
the office calendar in iCal (or some other Cal DAV client). Note
currently you cannot edit in iCal even with a read-write URL.
User D already has a Cosmo account. After clicking on the URL/
ticket, user D would like to add the shared collection.
as in: add the shared collection...to their account?
Do we want to itemize what we're not supporting, even for lightweight/
casual usage? As in, stuff we think is important to the CC, but don't
have time to do for 0.6.
+ Search
+ Quick item entry
+ List view
+ Easy way to add a share the CC just accessed anonymously to a newly
created account
On Dec 28, 2006, at 1:02 PM, Priscilla Chung wrote:
http://svn.osafoundation.org/docs/trunk/docs/specs/cosmo/rel0_6/
zeroDot6.html
I've tried to capture most of the discussions on the list. I'm sure
there are more questions/concerns which I'd like to capture by
following up with a spec review next Thursday in the Cosmo meeting.
Cheers, -Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
