When I started to write up the test scenarios for 0.6.1, I had
noticed a workflow was over looked from what was specified for the
Casual Collaborator (workflow B in the 0.6 spec: http://
svn.osafoundation.org/docs/trunk/docs/specs/cosmo/rel0_6/zeroDot6.html
+C).
*Workflow:*
+ Ivan the Individual Contributor receives a read-only bookmarkable
from Helen the Hub.
+ From his desktop e-mail client, Ivan click on the URL and opens a
new tab/window from his browser.
+ Bart sees Helen's work calendar and clicks on the 'Sign up for an
account' button/graphic.
+ A dialog pops up to enter in the user's account information.
+ Once the information is entered, an e-mail is sent to his account
to verify his account. Ivan goes into his e-mail client and clicks on
the URL to verify his e-mail account is active.
+ A new tab/window in the browser opens and asks Ivan to log into his
Chandler Hub account.
+ Ivan logs into his new Chandler Hub account—defaults to a blank
'Chandler' calendar.
*Issue:*
Currently in 0.6, In order for Ivan to subscribe to Helen's
collection, Ivan would then need to go back to the previous window w/
Helen's read-only calendar collection or back to his e-mail to click
on the read-only bookmarkable from Helen and follow the workflow to
click on the '+' to subscribe to a collection sent from a Helen the
Hub (Chandler Desktop user).
*Proposal*
+ From a bookmarkable URL, when a user clicks on 'Sign up for an
account' a 'Creates an account' dialog appears. In the 'Create an
account' dialog at the bottom display a check box that says:
[ √ ] I'd like to subscribe to this collection once I create my
account. (default to: checkbox is checked)
+ Once the user goes through the sign up process (e-mail
verification), the user logs in and will be placed into the
collection they were previously looking at—the collection sent from
Chandler Desktop user.
+ On the left navigation, once the user logs in it will default to
the collection they were looking at, but they will still be able to
switch to the default 'Chandler' blank calendar. Meaning the user
would start off with two calendars in the left navigation.
I believe we had a discussion on the list to see if it was necessary
to keep the out of the box 'Chandler Hub' calendar. I think for now,
I don't see much harm to keep a blank calendar for the CC users. When
we introduce remove, perhaps they would be able to remove it from
their list?
Any thoughts on this proposal?
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
