On 12 Jun, 2007, at 10:06, Aparna Kadakia wrote:

Grant,
I believe I am the original publisher of the Office calendar and I believe when we share any calendar, triage status is checked by default.

So the question is:

That's two questions :)

1. why does it trigger unnecessary changes?

Because anytime someone else changes the triage status of an event (or possibly auto-triages it, I'm not sure), it will show up in the "Now" section of everyone else's Dashboard view of the office calendar. So far as I can tell, a bunch of events from the office calendar -- ones I've never touched -- are showing up as conflicts for me due to triage status changes by Mimi.

2. should the default triage status on the publish dialog be unchecked?

Yes. Unless you want to be using the office calendar as a task management tool :o.

--Grant

Aparna

On Jun 12, 2007, at 9:59 AM, Grant Baillie wrote:

On a related note, why is triage status being shared on the office calendar? I don't think that makes any sense for an office-wide calendar, and it seems to trigger unnecessary changes.

--Grant

On 12 Jun, 2007, at 09:42, Morgen Sagen wrote:

Every couple days or so I have been removing bogus events from the office calendar, such as the "Lorem ipsum..." ones, or the duplicate "Ops Group Meeting" ones, and inevitably they reappear. I suspect this is because one or more dump files (oops, I mean "export" files) still containing these events are being reloaded and sticking those events back on the calendar. I'm trying to think of a way we can permanently scrub these events out of existence without causing too much inconvenience for everyone. Ideally we could declare today a "resubscribe day" and have everyone not reload their .chex files, but instead use a settings (.ini) file to resubscribe to their calendars, and then export new .chex files.

How does that sound?

~morgen



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

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to