From: grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Offline mail and group cooperation
Date: Tue, 24 Sep 2002 10:15:47 +0200 [thread overview]
Message-ID: <vafelbj3irw.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <878z1smmjp.fsf@emacswiki.org> (Alex Schroeder's message of "Mon, 23 Sep 2002 23:19:22 +0200")
Alex Schroeder <alex@emacswiki.org> writes:
> Your description did not contain any problem to solve. What is the
> problem you have with disconnected usage? All I can think of is "If I
> move a mail from folder X to folder Y, everybody else should move that
> mail from folder X to folder Y." Is this an accurate description of
> the problem? Perhaps another problem is that "I want all coworkers to
> have the mails in the same folders as I do." -- but really, why do you
> want that? So basically, before you start looking for a solution, you
> need to specify the problem. ;)
Back when we were using mail aliases, it often happened that some
messages were sent to a specific person, but not to everybody who
would be interested. Since we started using shared imap folders for
this, the problem disappeared because everybody automatically moves
mail regarding the foo project into the foo folder and so everybody
involved with the project knows about all messages.
So, what is the problem we want to solve?
* First of all, there is the disconnected thing. People access mail
from their laptop while at home, while at work, and they might want
to read it while in the train. So I want to slurp mails from home,
work on them in the train on the way to work, then send my
responses from the office.
* Secondly, there is the shared email thing. People work together on
a project and all email regarding the project should be seen by all
people.
* Some of these mails are todo items. It would be nice to have a way
to see which items are done and which still need to be done.
Does that make things clearer?
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-09-24 8:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 20:11 Kai Großjohann
2002-09-23 21:19 ` Alex Schroeder
2002-09-24 8:15 ` Kai Großjohann [this message]
2002-09-24 12:41 ` Clemens Fischer
2002-09-24 14:49 ` Kai Großjohann
2002-09-24 17:17 ` Alex Schroeder
2002-09-27 2:43 ` news
2002-09-27 10:24 ` Kai Großjohann
2002-09-27 17:05 ` Christoph Garbers
2002-09-27 17:59 ` François Pinard
2002-10-02 18:40 ` Scott A Crosby
2002-09-24 11:33 ` Simon Josefsson
2002-09-24 12:11 ` Kai Großjohann
2002-09-24 12:19 ` Kai Großjohann
2002-09-25 18:34 ` Björn Torkelsson
2002-09-26 8:14 ` Kai Großjohann
2002-09-26 8:44 ` dme
2002-09-26 14:40 ` Kai Großjohann
2002-09-26 16:11 ` Wes Hardaker
2002-09-26 16:59 ` Simon Josefsson
2002-09-26 17:11 ` Kai Großjohann
2002-09-26 17:28 ` dme
2002-10-17 19:54 ` Kai Großjohann
2002-10-17 20:15 ` Kai Großjohann
2002-10-20 19:53 ` Kai Großjohann
2002-09-24 11:55 ` Reiner Steib
2002-09-24 12:16 ` Kai Großjohann
2002-09-24 12:17 ` Christoph Garbers
2002-09-27 14:14 ` Frank Schmitt
2002-09-27 14:32 ` Kai Großjohann
2002-09-27 15:36 ` Frank Schmitt
2002-10-01 19:02 ` Paul Jarc
2002-10-06 20:05 ` Kai Großjohann
2002-10-07 2:30 ` Daniel Pittman
2002-10-07 23:25 ` Clemens Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafelbj3irw.fsf@lucy.cs.uni-dortmund.de \
--to=grossjoh@lothlorien.cs.uni-dortmund.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).