W3C home > Mailing lists > Public > ietf-discuss@w3.org > July 1999

RE: Proposal: Mailing list archive requirement(s)

From: Jacob Palme <jpalme@dsv.su.se>
Date: Thu, 29 Jul 1999 11:34:16 +0200
Message-Id: <v04210118b3c5ce9ee985@[]>
To: IETF Applications Area Discussion List <discuss@apps.ietf.org>
Non-simultaneous group communication is done through two different
kinds of services:

(b) Groupware systems, like Usenet news, where the same user interface
     is used for reading, searching, filtering, writing.

(a) E-mail mailing lists. Here, reading is done by ordinary mail clients,
     but these mail clients can use filters, to put each list into a
     separate folder. The reader will then have the same kind of
     structured reading as in groupware. Archiving is done by separate
     archiving systems, which again can provide the same services
     as groupware systems.

I am not sure that users want it to be this way. Users want to discuss
topics, organise their discussions, browse old discussions. Users
probably prefer to do this in a unified way.

At 13.43 -0700 99-07-27, Dan Kohn wrote:
>To make a specific proposal, I think we're suggesting that BCP 25, RC
>2418 <http://www.normos.org/ietf/bcp/bcp25.txt> should be updated to add
>additional requirements to the working group mailing lists in section
>I would suggest that working group mailing lists have the following
>additional requirements:
>1) The mailing list should support standard -request commands for
>subscription requests.
>2) The mailing list should have a web-based archive that supports
>searching and threading.
>3) The mailing list should also archive the messages in original rfc822
>message format or in standard Unix mailbox format.
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/~jpalme
Received on Thursday, 29 July 1999 05:38:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:08:06 UTC