Overview

This page covers the current status of sharing, a list of general workflows as well as a running list of open questions and issues that we need to address going forward. This is a work in progress and is by no means complete.

Workflows

• 1) Mitch and Esther share a calendar, each have read/write access (P1-b).
• 2) Chao, Mimi and Sheila share a design calendar with read/write access (P1)
• 3) Sheila shares her free busy information with OSAF (P1)
• 4) Mimi shares her whole calendar with the engineering team, giving them read only access (P1)
• 5) Sheila shares her whole calendar with the engineering team, giving them read only access. She also shares this with Mimi and Chao giving them read/write access (P1-b)
• 6) Mimi wants to share her All Calendar and All Tasks but not All Email (P1)
• 7) Sheila has a design collection, she wants to share only the calendar and tasks and not the email (P2).
• 8) Chao wants to share his All Email collection with others (P3)
• 9) Mimi wants to share All or some portion of her In, Out and Trash collections (P3)
• 10) Sheila wants to browse Mimi's free-busy in order to schedule a meeting (P1).
• 11) Chao wants to browse Sheila's free-busy just to see what she is doing but not to schedule some of her time (P2/3).
• 12) Chao creates a new item on the shared design calendar and wants to send a notification to Mimi and Sheila that it has been added (P1).
• 13) Mimi changes the meeting room for a shared item and wants to notify Chao and Sheila that it has changed. (P2) - (P1) Chao, as the organizer, changes the meeting room and sends an update.
• 14) Sheila wants to share a calendar with a non-Chandler user (P2) - note- kind of works via webDAV icalendar files.
• 15) Chao wants to send an meeting invitation to someone not having access to the shared calendar. (P1) He changes some details and subsequently sends them an update (P1).
• 16) Someone who is not sharing the calendar updates the meeting information and wants to send it to Chao, Mimi and Sheila (P3).

*...there are probably more.

Sharing Discussion Points and Issues

Resolution for Reconciling Emails and WebDAV Accounts

• Examined several scenarios - tickets a possibility
  • Understanding how tickets work in more detail.
• Do we need to have constraints for Kibble, multiple webDAV servers, people who are not chandler users or don't have a webDAV account.
• What is really the post Kibble plan? Are there security issues we need to be worried about?

Do we still need to have sharing statuses?

• We have some unsolved problems tracking sharing statuses for sharees that do not have write priviliges to a share. They won't be able to update their information.
• What is the benefit of having sharing statuses...do we need them at all?
• Can we have some other receipt for indicating that a user has received and accepted the share. Does it matter if we never receive receipts from people.
• Do we feel this is an important enough feature to justify the cost of the work?

Shared collection with non-shared items

• Currently in the detail view, there is a lock to prevent a particular item from being shared.
  • Do we need to add another column in summ view to indicate that something is excluded.
• Is there a problem if we create a new collection and add non-shared and shared items? Do we need to show which ones are shared ones are shared? (Chao and Sheila don't think this is necessary).

Sharing Conflicts

• Don't know much about this yet.
• Are conflicts less likely or more likely in calendar-centric mode.
• Do we need to have the ability to version? Should the user be able to roll back to previous version?
• Do we need a conflict merge UI?
• What about a simple notification of conflict details via email but last update is the live version.
• Asking Morgen and Lisa for a proposal might be good first step.

Invitation Workflow and Sharing

• How will invitations for collection shared calendar events differ from invitations for non-shared calendar events?
• Should all attendees be able to update item?
• How do we handle a shared event where there are non-sharing attendees?
• I sharer creates an item and sends me an invite. When I receive it, how does this get reconciled with the event on the shared calendar. What if I want to change the item?

Other

• Did we ever solve the problem about accepting a share and adding items to the All collection.
  • Is this user specified? What is the default?
  • What are the pros and cons of each scenario?
• Do we need any UI to handle change in ownership of shares. How does this work on the server, is there anything we need to do for Kibble.
  • Deletion might be an issue.
• How do we handle a shared calendar that doesn't really have an owner ie: a meeting room. Is that different than our other workflows?
• Can we support private annotations on a shared item? How difficult is this?

ACLs

• We need to detail out all the ACL workflows once Heikki is done with the client UI.
• How much work is the widget that we are envisioning to handle this? What is the cost of this widget, how does it prioritize with other widgets work? Look at other UI alternatives.
• Is Free-busy just another ACL in the list? Find out what makes sense implementation wise.
• Should we consider notifications for changes in permissions or sharing termination?

Deletion

• Should non creaters of the item be able to delete it? (Yes).
• If I created a share for design and I moved teams and deleted it, can I transfer ownership to someone else?
  • How would this work in the UI.