My reply in-line.
On Apr 11, 2007, at 5:58 AM, Mimi Yin wrote:
I'm not sure I'm following. When you say 'Displaying the published
URLs before verifying the user's server account.' What published
URLs are you referring to?
When I create an account on the server today, there is a table of
information for me to publish (say my iCal) calendar on to the
server. It is the same information you see in the desktop Account
dialog box (for sharing server).
The proposal here: http://wiki.osafoundation.org/Journal/
SignUpForAnAccountForOtherCalendaringClients is about how to set
non-Chandler Desktop users up to use Chandler Hub or Chandler
Server (Cosmo), correct?
That is correct. I'm wondering since you can't currently create a
server account w/ the desktop, and have to go to the web ui and
create an account first. When you select 'Chandler desktop' in the
drop down menu, instead of an URL you'd see instructions for you to
continue back in the 'Account Preferences' dialog. (This relates to
all three use cases I had outlined.)
Or are you looking to address security issues relating to email
verification?
It's partially security, but more for us to tell if the accounts are
legit vs. bogus e-mails. See Jared's thread about 'telling users why
e-mail is required': http://lists.osafoundation.org/pipermail/design/
2007-April/006880.html
I'm wondering since this is for Post-Preview if we should re-
consider this workflow in a larger context. Meaning the 4 scenarios
I listed below:
- Subscribe with Chandler Server / Hub
- Subscribe to stuff on Chandler Server / Hub with some other app
- Publish with Chandler Server / Hub
- Publish to Chandler Server / Hub with some other app
Plus, the issues that have arisen on the Account Browser thread:
http://lists.osafoundation.org/pipermail/design/2007-April/006894.html
+ URLs for the Hub/Server user to use versus:
+ Sharing URLs for others to use
I understand all of these scenarios are addressed in various ways
in the End-user PIM UI and Account Browser today or are slated for
Post-Preview... But it seems like all of these features are related
and should have a single coherent framework?
Yes. That part is post preview. I just want to confirm that you
understand the proposal for preview vs work post-preview?
We can chat about this more after the Logo Group meeting today?
Sure.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
