Hi Mimi,
I noticed when reviewing the addressing options in the spec that the
concept of CC: or BCC: the Sender
is not in the spec.
If I remember correctly the sender of the message was suppose to also
receive a copy in his or her Inbox
as a notification.
I don't see this idea any where in the spec.
I do see:
Note: When 'Updating' Items, the previous Sender: or Updater: should
be automatically added to the CC: field of the message if they are
not already mentioned in one of the Addressing fields: From, To, CC,
BCC.
Are we no longer planning to notify the sender of the message?
Another question is what happens if another user receives the Edit /
Update via sharing then
Edits the item and sends it to the participants.
The senders info will not be in the Chandler from. to, cc fields
unless manually added which means
the sender could get lost if later changes are applied. An example,
John not in the addressing fields of
the email (but is the sender) edits the mail and sends it.
When receiving the mail the other collaborators have John as the last
modifier (sender). But if
Jean who is one of the collaborators makes a change then John will no
longer be the last sender
and since he is not in any of the Chandler addressing fields will no
longer participate in the
conversation.
In re-reading the spec it appears to me that we need to keep a number
of additional fields
around to capture the differences between the email worlds from:, to:
etc and the Chandler
world.
There are issues with that as well. If a user has been added to the
list because he or she is
in the email worlds Cc: list (They were a sender) but not in the
Chandler Cc: list how would one remove that
person from the workflow?
I think there needs to be more discussion (Meeting / Phone chat) on
exactly how this is suppose to
work from a Chandler users perspective and a Email GUI users
perspective. Once I have
a clear picture I can move on to the implementation.
-Brian
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
