How does Scooby show shares we have subscribed to using Chandler desktop

On 7/12/06, Sheila Mooney <sheilaosafoundation.org>
wrote:
> As I understand things, currently when I log into
Scooby, I am
> logging into my account on Cosmo. From there I am able
to view
> whatever calendars I have published to that account.
For desktop
> users, they could be viewing a wide variety of shared
calendars...
>
> + calendars published on Cosmo Demo
> + calendars published to other servers
> + calendars they have subscribed to from Cosmo Demo,
.Mac, Google etc.

i don't know about any of that. scooby just shows you the
calendars in
your cosmo home directory. those calendars had to have been
put there
by some client. that client may have originated those
calendars or
copied them from some other location, but cosmo and scooby
don't know
anything about that.

> The issue is that for some people their primary
calendars will be
> ones that they have subscribed to and not published.
This leads to a
> bunch of questions around what we need to do in order
to support this
> and what (of the desktop world view) should really be
viewable in
> Scooby.
>
> + What happens if I have calendars published on several
servers? I
> don't quite understand how this works with the logins.
Do we even
> need to worry about this?

cosmo and scooby won't know anything about what you've
published with
chandler to any other servers.

> + How does Scooby know about calendars I have
subscribed to? Say that
> I have subscribed my Chandler to a remote .ics URL
(like .Mac or
> Google Calendar)?

it doesn't, unless chandler actually makes local copies of
those
calendars and then syncs them to cosmo (i have no idea if it
does that
or not).

> + Do I need my Chandler to turn around and upload that
calendar to
> Cosmo (and keep it in sync) in order for Scooby to see
it or is
> giving Scooby the calendar's remote .ics URL
sufficient?

at the moment, chandler is the middle man. cosmo and scooby
have no
capability for dealing with calendars that are not in the
cosmo home
diretory.
_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

Brian Moseley wrote:
> On 7/12/06, Sheila Mooney <sheilaosafoundation.org> wrote:
>> As I understand things, currently when I log into
Scooby, I am
>> logging into my account on Cosmo. From there I am
able to view
>> whatever calendars I have published to that
account. For desktop
>> users, they could be viewing a wide variety of
shared calendars...
>>
>> + calendars published on Cosmo Demo
>> + calendars published to other servers
>> + calendars they have subscribed to from Cosmo
Demo, .Mac, Google etc.
> 
> i don't know about any of that. scooby just shows you
the calendars in
> your cosmo home directory. those calendars had to have
been put there
> by some client. that client may have originated those
calendars or
> copied them from some other location, but cosmo and
scooby don't know
> anything about that.

In the long run, I'd think we want users to be able to
subscribe to 
calendars on other servers (cosmo, .mac, google, other
caldav, etc.) 
from either scooby or chandler. Information about those
subscriptions 
could be stored on cosmo so that they could be seen from
both the web 
and desktop clients, and the web and desktop apps should be
able to 
fetch the data.

In the short run, I'm guessing we don't need to support
subscriptions to 
other cosmo servers -- probably the ".osaf"
service (or whatever it is 
called) will be the only one out there in the
"beta" timeframe.

So the open question is, will scooby support .mac, google,
etc. 
subscriptions in the next 6 months? I'm guessing no, but
that we'll want 
that eventually.

>> The issue is that for some people their primary
calendars will be
>> ones that they have subscribed to and not
published. This leads to a
>> bunch of questions around what we need to do in
order to support this
>> and what (of the desktop world view) should really
be viewable in
>> Scooby.
>>
>> + What happens if I have calendars published on
several servers? I
>> don't quite understand how this works with the
logins. Do we even
>> need to worry about this?
> 
> cosmo and scooby won't know anything about what
you've published with
> chandler to any other servers.

They can if Chandler tells Cosmo about it by storing
subscription 
information.

>> + How does Scooby know about calendars I have
subscribed to? Say that
>> I have subscribed my Chandler to a remote .ics URL
(like .Mac or
>> Google Calendar)?
> 
> it doesn't, unless chandler actually makes local
copies of those
> calendars and then syncs them to cosmo (i have no idea
if it does that
> or not).
>> + Do I need my Chandler to turn around and upload
that calendar to
>> Cosmo (and keep it in sync) in order for Scooby to
see it or is
>> giving Scooby the calendar's remote .ics URL
sufficient?
> 
> at the moment, chandler is the middle man. cosmo and
scooby have no
> capability for dealing with calendars that are not in
the cosmo home
> diretory.

I don't think its a good idea for Chandler to be
republishing calendars 
on Cosmo like this (it doesn't do that now). As Brian and
Mikeal 
discussed earlier, I think it makes more sense to store
subscription 
information on Cosmo, and have the web and desktop apps be
responsible 
for grabbing the data.

http://lists.osafoundation.org/pipermai
l/scooby-dev/2006-July/000608.html

Cheers,
Katie


_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

Brian Moseley wrote:
> On 7/12/06, Sheila Mooney <sheilaosafoundation.org> wrote:
>> As I understand things, currently when I log into
Scooby, I am
>> logging into my account on Cosmo. From there I am
able to view
>> whatever calendars I have published to that
account. For desktop
>> users, they could be viewing a wide variety of
shared calendars...
>>
>> + calendars published on Cosmo Demo
>> + calendars published to other servers
>> + calendars they have subscribed to from Cosmo
Demo, .Mac, Google etc.
> 
> i don't know about any of that. scooby just shows you
the calendars in
> your cosmo home directory. those calendars had to have
been put there
> by some client. that client may have originated those
calendars or
> copied them from some other location, but cosmo and
scooby don't know
> anything about that.

In the long run, I'd think we want users to be able to
subscribe to 
calendars on other servers (cosmo, .mac, google, other
caldav, etc.) 
from either scooby or chandler. Information about those
subscriptions 
could be stored on cosmo so that they could be seen from
both the web 
and desktop clients, and the web and desktop apps should be
able to 
fetch the data.

In the short run, I'm guessing we don't need to support
subscriptions to 
other cosmo servers -- probably the ".osaf"
service (or whatever it is 
called) will be the only one out there in the
"beta" timeframe.

So the open question is, will scooby support .mac, google,
etc. 
subscriptions in the next 6 months? I'm guessing no, but
that we'll want 
that eventually.

>> The issue is that for some people their primary
calendars will be
>> ones that they have subscribed to and not
published. This leads to a
>> bunch of questions around what we need to do in
order to support this
>> and what (of the desktop world view) should really
be viewable in
>> Scooby.
>>
>> + What happens if I have calendars published on
several servers? I
>> don't quite understand how this works with the
logins. Do we even
>> need to worry about this?
> 
> cosmo and scooby won't know anything about what
you've published with
> chandler to any other servers.

They can if Chandler tells Cosmo about it by storing
subscription 
information.

>> + How does Scooby know about calendars I have
subscribed to? Say that
>> I have subscribed my Chandler to a remote .ics URL
(like .Mac or
>> Google Calendar)?
> 
> it doesn't, unless chandler actually makes local
copies of those
> calendars and then syncs them to cosmo (i have no idea
if it does that
> or not).
>> + Do I need my Chandler to turn around and upload
that calendar to
>> Cosmo (and keep it in sync) in order for Scooby to
see it or is
>> giving Scooby the calendar's remote .ics URL
sufficient?
> 
> at the moment, chandler is the middle man. cosmo and
scooby have no
> capability for dealing with calendars that are not in
the cosmo home
> diretory.

I don't think its a good idea for Chandler to be
republishing calendars 
on Cosmo like this (it doesn't do that now). As Brian and
Mikeal 
discussed earlier, I think it makes more sense to store
subscription 
information on Cosmo, and have the web and desktop apps be
responsible 
for grabbing the data.

http://lists.osafoundation.org/pipermai
l/scooby-dev/2006-July/000608.html

Cheers,
Katie


_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

On 7/12/06, Katie Capps Parlante <cappsosafoundation.org> wrote:

> I don't think its a good idea for Chandler to be
republishing calendars
> on Cosmo like this (it doesn't do that now). As Brian
and Mikeal
> discussed earlier, I think it makes more sense to store
subscription
> information on Cosmo, and have the web and desktop apps
be responsible
> for grabbing the data.

i'm undecided. it does seem like a waste of bandwidth and
processing
for both cosmo and chandler to retrieve remote data, but i
guess
there's no practical difference between chandler sending it
to cosmo
and cosmo fetching it from the source.

however, bobby does bring up a good point about stamping and
so forth
that occurs in chandler. presumably we want cosmo to know
about these
changes to the original data.
_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

On 7/12/06, Katie Capps Parlante <cappsosafoundation.org> wrote:

> I don't think its a good idea for Chandler to be
republishing calendars
> on Cosmo like this (it doesn't do that now). As Brian
and Mikeal
> discussed earlier, I think it makes more sense to store
subscription
> information on Cosmo, and have the web and desktop apps
be responsible
> for grabbing the data.

i'm undecided. it does seem like a waste of bandwidth and
processing
for both cosmo and chandler to retrieve remote data, but i
guess
there's no practical difference between chandler sending it
to cosmo
and cosmo fetching it from the source.

however, bobby does bring up a good point about stamping and
so forth
that occurs in chandler. presumably we want cosmo to know
about these
changes to the original data.
_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

On Jul 12, 2006, at 5:07 PM, Katie Capps Parlante wrote:

> So the open question is, will scooby support .mac,
google, etc.  
> subscriptions in the next 6 months? I'm guessing no,
but that we'll  
> want that eventually.

disappointed_users++

Ted
_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

On Jul 12, 2006, at 5:07 PM, Katie Capps Parlante wrote:

> So the open question is, will scooby support .mac,
google, etc.  
> subscriptions in the next 6 months? I'm guessing no,
but that we'll  
> want that eventually.

disappointed_users++

Ted
_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev