Design Engineering Meeting Notes

Attendees

• Mimi, Lisa, Sheila

Agenda

• Free form discussion on sharing, issues, what the plan should be.
• Mimi and Sheila wanted to have a open discussion with Lisa and ask a bunch of questions regarding sharing and interoperability.
• The purpose of the meeting was not to make any decisions...just brainstorm ideas.

Notes

Free busy information

• Talked about free busy information
• Chandler users should be able to publish free-busy information and make it visible to non-chandler as well as Chandler users.
  • Mimi and Sheila will revisit workflow for this. Probably easiest in phase 1 to specify people to whom we want to publish, the same way we do for sharing.
  • What is the workflow to publish free-busy?
  • What if the user shares their whole calendar? Is the free-busy publishing still separate?
  • If the user shares some calendar events but not others, do we use this as partial free-busy? Do we infer free-busy from the shared calendar?
• Free busy view not as critical for 0.6 as some other things but likely a good idea to have a publish step to get the infrastructure in place.
  • This would allow us to get the synchronizing and updates working.
  • We can have a non-fancy way to view this in Chandler. Probably need to work with apps team to figure out what makes sense although it is my understanding that the display is not a big deal.
• If there is no CalDAV solution (not using our server), is there an alternative? Do we publish free-busy to a webDAV server?
• Sheila is going to spend some time with the RFC to understand how we represent free busy.
• Mimi and Sheila will work on workflow proposal for Kibble, then figure out what is in 0.6.

Storing shared events on the WebDAV server in iCalendar format

• Talked a bit about this.
• What are the alternatives for representation of our events in iCal format.
  • How do we handle anytime, all day events.
  • Think about extensions to the standard.
  • What information specific to Chandler can be embedded in the data. Stamping, anytime info.
    • Mimi, Lisa and Sheila will work on this problem further.
  • What if we want to share to a server that doesn't support CalDAV.
• Overall, it seems like we can make this work ok.
  • Mimi and Sheila need to fill out interoperability scenarios and priortize.

Invitations

• Try to support iMip in 0.6.
• How do invitations to an all day or anytime event work? Mimi will think about this.
• Mimi and Sheila are ok with one-way invitations with owner update broadcasts for Kibble. Will look at whether or not we can use iMip for item sharing post Kibble.
• Sharing invitations - what are the next steps for this.
  • Should we support sharing invitations for non-chandler users in 0.6?

ACLs - Sharing Permissions

• Looks like Heikki has something for Morgen to use at the end of 0.5.
• Apps team may not have time for special grid widget used in sharing invitation. This may not be possible even for Kibble.
  • Mimi and Sheila will detail all the sharing invitation and detail view items that are necessary (feedback statuses etc).
  • Then we will sit down with apps team to come up with a UI proposal for Kibble.
  • Stage this over 0.6 and 0.7.

Polling

• Make this a PI for 0.6.
• Mimi and Sheila will talk to Morgen about next steps to make this work, conflicts and issues we need to solve in the design.

Next Steps

• Mimi and Sheila are going to prepare a "this is how sharing should work for Kibble proposal". This includes what interoperability scenarios we would like to have.
• Will forward to Lisa for discussion, feedback and iterations. We may need to bring Brian Moseley in on the discussion.
• Figure out what should be done for 0.6 and 0.7 based on this plan.