Hi Priss,
On Apr 10, 2007, at 12:40 PM, Priscilla Chung wrote:
Do we want to have the Publish instructions available from within
the Logged-in UI? Do we want to always introduce users to the web
app UI? and then from there they can choose between Subscribe
with: and Publish to:?
Eventually I think we want to do this within the web app, (as
opposed to just the account creation) but this is the part that is
post preview. The issues I'm concerned about in my first email
(which I failed to make clear) were about displaying the published
URLs before verifying the users server account—specifically on the
hub. All the other complications about which URL the external
client uses is the concern bcm has filed in the bug 8081.
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? 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? Or are you looking to address security issues
relating to email verification?
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?
We can chat about this more after the Logo Group meeting today?
Mimi
Some other open issues:
+ Will Chandler Server / Hub support publishing to other servers
from the Chandler Server web app?
Post preview.
If we do that means we have 4 options:
- Subscribe with Chandler Server / Hub
- Subscribe to stuff on Chandler Server / Hub with some other app
So this we have already and is listed either in the 0.6/0.7 test
scenarios.
- Publish with Chandler Server / Hub
On the web ui, not for preview.
- Publish to Chandler Server / Hub with some other app
This is in the 0.6.1 test case scenarios, under: 'iCal calendar
(other CalDAV calendars) publish to Chandler Server sharing (repeat
this scenario w/ Sunbird)'
We will want to understand what the use cases are around the
additional scenarios and drive the product definition from there?
I think I've covered most of these use cases already in the 0.7
test scenarios—in one form or another. It may their own test case,
but let me know if you think I should single it out.
If I am missing anything then let's add it to the list—except for
publishing from the web app, which is post preview. ;)
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
