Design Session Dashboard Sharing/Communication/Recurrence Meeting

• Mimi to walk through: http://wiki.osafoundation.org/bin/view/Journal/DashboardSharingCommunicationsRecurrence

• Next steps: to update the spec. and schedule another conference call might be Friday.
• Need to schedule follow up meeting: last two points. Sheila/Mimi to update the spec. figure out what in preview/post preview buckets

---

Q. Changes in triage status counts as modifications--> we do.

• status of unread to read.
• does it count as a modification
• reason why we care as modification
• sharing the fact that someone read something is significant to you.
• things which are modification that get shared.
• what fields change when modification, * little line item underneath the address field. * the 'Who column' (depends on the modification) * the item becomes unread looks different, if you're share read/unread status

At the bottom we'll have something at the bottom which will be post preview. More granularity on what was changed.

• read vs unread would also update those same fields as well. If read/unread status is NOT share, it will not change. (optional to share)
• Only care about edits when it's shared.

Q. What if an item that belongs in multiple collection? If we're sharing an item in two collection, we sync them independently. What happens to changes just on that machine, what other changes might apply?

• Different ppl have different last modified. Bryan: One person, one item, it's in multiple collection.

• One item it's in multiple collection, different collection, what proposal different triage status for
• Last modified is a per user thing.

WHO MODIFIED WHAT, WHEN & SHARING

• Share time, in your repository that is last modified.
• Disable 'purge' in the calendar view. Already done.

---

Sort by triage status

• Triage status: What is the status of this item as far as I'm concerned.
• Different then tracking an item as a tasked as a shared thing.

• Bryan: The acting that a bug has been assigned to me, It's confusing we're sharing two different things. Users each of whom has their own status, not making sure how to share triage status

Individual status till post preview. The PPD collection is not in my personal task list, and there items which are 'my items', I set the triage status on that item, it's a way for other ppl to know this is what I'm working on now. For task list, there might not need to be a group triage status, tasks are owned by individual. Bugzilla being a larger scale thing, the status of that bug vs. would be helpful has been slated for Alpha 4 but is not working on it.

• Bryan: don't know what the rules are for this attribute. Three things going on–will go offline. Sharing triage status with a group of people.

• Bryan: Having multiple people changing triage status and sharing it doesn't make sense–but is ok as the thought of sharing triage status would be with himself.
• Sharing item status and triage status, what's in my 'now' section.

• Understanding what section it appears in and what triage status
• Issue: We don't want to share what section it appear, but can share triage status.

• Don't understand the use case, but there is automatic things that happen to the field and conflicts.
• New items appears in 'now'. Status is still later. How to move into the later section, hit 'purge/triage'.

• Sharing has an effect on the temporary status. Section vs. color (real).

• Now, now to later, clicked to later, color is yellow, section stays green–the sharing the color is yellow and the section is green. Hit's 'purge' make section match the color.

• Grant: Attribute name is going to change (the way it's indexing is currently different then what is expected.)

Sharing color triage status but not section triage status.

• Useful to the shared sense of state. (color triage status to be real and purge to place everything in the correct section and color)

Section triage that will look weird.

1. triage and haven't 'purge' yet.
2. receive an update.

• For unread items, you're about to purge, we want to warn you of items you have not read yet.

forget about the 'New'.

• If you're sharing triage status you're sharing alarms.
• Nice to have: triage status, change value time that is effectively changed. Explicit ordering. Would share that if you're sharing triage status w/ yourself.

• Explicit ordering, and you share triage status, you automatically share in that order.

---

Creation

• Auto triage should set both attributes excepts in the command line space where it's only setting the section.
• Which triage status are you setting.

---

• Recurring events/communication
• Preview, sending recurring events/forwarding/addressing fields replies to the entire series.

• Sheila: What you see in the table when you create a new series?
• Review the dashboard spec under recurring events: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Dashboard-0.7.html
• If events change from the reminder triage, who modified that event. Everyone would change the setting to now.

Person who syncs first modifies the item.

• Need to also have the same for undo.
• How Esther does things, make modifications regularly, every recurring event, just the time.
• A bunch of recurring events, I go make a change to it.

• Could we replace the previous recurring event if there is a modification?
• Imported a recurring event long time ago, it can start sooner rather then a long time ago.

-- PriscillaChung - 01 Nov 2006