[chandler-users] email in Chandler

[Rick Rawson]

Just some brainstorming...

The current implementation of email is not really email in the sense of 
being a bona fide email client and, according to chandlerproject, it is 
not intended to be so. Highlighting the need for email is the fact that 
I find myself using Thunderbird to email my colleagues with whom I share 
Chandler collections. Those emails are part of the collaborative effort 
of which Chandler is central, so it seems inefficient to use a second 
program. A plug-in could potentially resolve this problem.

Since Chandler's email is not really email, maybe it should not be 
called email. It's more like a pneumatic tube connecting two or more 
collaborators. The same material keeps getting shuttled back and forth. 
I suppose that if it's not called email, then using email addresses as 
part of the implementation would be slightly confusing. On the other 
hand, plenty of websites require me to use my email address as a 
username, so it might not be so surprising if a "user list" in Chandler 
consisted of a list of email addresses.

Having a plug-in for Thunderbird in a program that already contains some 
kind of email functionality might also be confusing. This may be all the 
more reason to rename the current system in Chandler. c-mail? 
(collaboration-mail)

Alternatively, if the plug-in were inserted seamlessly, then Chandler 
might be viewed as enhancing Thunderbird's email capabilities (rather 
than the other way around). Thunderbird (within Chandler) would now be 
capable of UPDATING, as opposed to REPLYing TO, emails that already 
exist within specified IMAP folders.


Rick