So I realize I may not have framed this proposal correctly when I
first sent out my e-mail. As stated on the working wiki page…I just
updated (w/ a lovely new flowchart!), please review workflow:
http://wiki.osafoundation.org/Journal/
SignUpForAnAccountForOtherCalendaringClients
This is a proposal to identify workflows for users signing up for a
Chandler Server account but want to use it for other calendar
clients. Based on Bug#8081
On Apr 9, 2007, at 1:18 PM, Mimi Yin wrote:
Just to clarify: This is a post-Preview proposal.
So yes, I think this is what I recommend currently in the bug,
however it is currently targeted to 0.7. There are some issues which
I'd clear up and it may be something we want to do in the 0.7
timeframe…I don't know and would need a swag for this proposal.
*Issue*
Currently the information for users who want to use the server for
other external clients, is displayed in a table after you sign up for
an account, but *without* verifying your e-mail. That is unless you
have downloaded the bundle—then the ppl using the bundle can do
pretty much what they want to do, meaning they can sign up for an
account w/out verifying their e-mail (is that correct?).
*Revised Proposal*
+ Reword the 'Create an account' dialog after you've sign up for an
account, but have not verified your e-mail address.
+ Eliminate the 'information table for setting up a sharing account
in an external client' in the 'Create an Account' dialog. This is
because the information is going to depend on the external client and
there will be a unique URL for each. (This was pointed out in the
original e-mail thread: http://lists.osafoundation.org/pipermail/
design/2007-February/006413.html)
+ Introduce a 'gateway' page after the user clicks on the
verification e-mail. This page will direct the user to either click a
button to auto [log in to the web app] or ask them if they want to
[set up on an external client].
*Addendum to the last Proposal*
+ introducing the gateway page, no auto login directly from email
verification on use case two and three.
+ In all cases the table information about 'setting up a sharing
account in an external client' will not appear after signing up for
an account with server.
+ In all cases, where e-mail verification is turn on/off the user
would be directed to the 'gateway page' to choose go to the web app
or to select the URL and publish to the server from an external client.
---
*Use Case One: Users who have downloaded the OSAF bundle (e-mail
verification turned off)*
1. User signs up for an account, clicks [okay].
2. If e-mail verification is *turned off*; an Instructional
message appears (on the gateway page): 'Start using Chandler Server'
or 'Set up on an external application to use this account.'
3. If user selects 'Start using Chandler Server' --> auto log
into the (Hub) web application from the bundle
4. If user selects: 'Set up on an external application'
5. A dynamic drop down list appears:
[ Which application? | V ]
* Chandler Desktop
* Apple iCal 2.x
* Feed reader
* Other…
This will behave similar to the collection details dialog box. The
instructions and URLs will appear dynamically on the 'Create an
Account' dialog. A [close] button will also appear in this dialog box.
----
*Use Case Two: Users who have downloaded the OSAF bundle (e-mail
verification turned on)*
1. If e-mail verification is *turned on*, a message appears on
dialog: 'Almost done! Your account is created but not enabled. You
will receive an e-mail shortly with a link to enable your
account.' [Close]
2. User checks e-mail, clicks on the link to verify account,
launches the 'gateway page', open a new window/tab (or is there a
reason not to replace the old window?).
3. An instructional message appears (on the gateway page): [Start
using Chandler Server] or [Set up on an external application] to use
this account.
4. If the user selects [Start using Chandler Server] --> auto log
into the web app from the bundle
5. If the user selects: [Set up on an external application]
6. A dynamic drop down list appears:
[ Which application? | V ]
* Chandler Desktop
* Apple iCal 2.x
* Feed reader
* Other…
This will behave similar to the collection details dialog box. The
instructions and URLs will appear dynamically on the 'Create an
Account' dialog. A [close] button will also appear in this dialog box.
---
*Use Case Three: Users who have sign up on Chandler Hub (e-mail
verification turned on—same as above)*
1. If e-mail verification is *turned on*, a message appears on
dialog: 'Almost done! Your account is created but not enabled. You
will receive an e-mail shortly with a link to enable your
account.' [Close]
2. User checks e-mail, clicks on the link to verify account,
launches the 'gateway page', open a new window/tab (or is there a
reason not to replace the old window?).
3. An instructional message appears (on the gateway page): [Start
using Chandler Server] or [Set up on an external application] to use
this account.
4. If the user selects [Start using Chandler Server] --> auto log
into the web app from the bundle
5. If the user selects: [Set up on an external application]
6. A dynamic drop down list appears:
[ Which application? | V ]
* Chandler Desktop
* Apple iCal 2.x
* Feed reader
* Other…
This will behave similar to the collection details dialog box. The
instructions and URLs will appear dynamically on the 'Create an
Account' dialog. A [close] button will also appear in this dialog box.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
