Publish free-busy data from one collection, extracting event data from that collection and sharing it in a location separate from any shared calendars.
Access other users' free-busy data.
Assumptions
We will share free-busy data in 0.5 by leveraging the WebDAV account also used for sharing the whole calendar.
The WebDAV server doesn't have any special calendaring logic.
Free-busy information on the server will be publicly readable in 0.5.
Some users will want to publish only free-busy information, and not the rest of their calendar. Or if they want to do both, the permissions will be more restrictive for the latter.
Design issues/tasks
Consider whether there is a GUI for publishing free-busy information. The user might simply select a calendar and turn on "free-busy publishing". Partial answer: We're thinking that only one collection would have publishable free-busy, and the user would take action to publish that. Note that it's also possible to have free-busy information published automatically (or with a checkbox to disable) as soon as the WebDAV account information is configured.
Consider whether there is special GUI to access somebody's free-busy information. Is there somewhere to type in the URL?
Is there some connection between accessing somebody's calendar and accessing their free-busy published information? Can you find out about one from the other? See architecture task 1.
How does a user select another user to view their free-busy? Do we need to correlate email addresses and webDAV sharing accounts again? Partial Answer: when an item is stamped as an event, then you start to add people, a "schedule" button shows that. If the user clicks the "schedule" button, we start downloading free busy data.
How about coordinating free-busy viewing with sharing circle? We could make the sharing relationship setup automatically exchange free-busy publishing locations. Temporary answer: See tuesday's notes
How do multiple calendars relate to somebody's free-busy information -- do we do roll-up? Can I select a calendar and choose to make it part of my free-busy, or not? Answer: In 0.4, there will be some item collection (we will pick one) that is the source of free-busy information. Thus, if I download somebody else's calendar, unless I drag an event into my own collection, it doesn't roll up into my free-busy.
Architecture work
Consider whether free-busy information must be in a separate collection.
Consider what format to publish free-busy information in. Is it CalDAV-like?
Figure out how to correlate email addresses and WebDAV account locations. Do we annotate WebDAV account collections with a set of known email addresses and make that publicly readable? Or is this part of the information shared in sharing circle invitations?
Regardless of the limitations of 0.5 free-busy sharing, we need to plan for ultimately having the ability to roll up free busy from multiple collections, or to separately publish multiple sets of freebusy.