Mimi,

As we agreed in IRC, I rewrote the triage details from the dashboard spec to try to clarify things:
http://wiki.osafoundation.org/Journal/TriageStatusImplementationNotes

In this version, things are arranged by cause-then-result, not by result-then-cause; this gets rid of a *lot* of copy-and-pasted (or copy-and-pasted-then-slightly-modified) text, which (hopefully) means that minor nuances will stand out more. This will make it a lot easier for me to understand what needs to be implemented, and for QA to determine whether the implementation meets the spec.

This version has some of what's come up in this thread in the last few days: specifically, purge doesn't purge items that are unread. However, I didn't try to capture any of the recurrence behavior in this spec, because it wasn't in your original spec; I think it's important to cover here, though, so I intend to add it.

Have I missed anything, or can I replace the current triage stuff in the spec with this?

Thanks,
...Bryan

Mimi Yin wrote:
I have updated the Dashboard spec with stuff from the wiki, including: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Dashboard-0.7.html

http://wiki.osafoundation.org/Journal/DashboardSharingCommunicationsRecurrence

http://wiki.osafoundation.org/Journal/WhosTriageStatusIsItAnyway

http://wiki.osafoundation.org/Journal/AutotriageRules

Gasp!

The new and/or edited sections are colored GREEN.

The updates cover:

+ Color versus Section Triage status and how they relate to sharing.
+ Clarification around the Purge workflow and how it relates to sharing.
+ Uber table explaining all the various Auto-triaging rules
+ Recurring events wonderfulness including:
-- Pruning stray instances of recurring events in the Dashboard
-- Sending, Editing, Updating recurring events
-- Triaging and Marking recurring events as Read/Unread

Please review and let me know if anything is missing and/or wrong.

Mimi

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to