This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/
[iot-wg] mailing list etiquette - again
- Previous message (by thread): [iot-wg] iot-wg Digest, Vol 21, Issue 1
- Next message (by thread): [iot-wg] Draft minutes from RIPE77
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Fri Nov 9 09:43:21 CET 2018
On 7 Nov 2018, at 15:04, Avetik Yessayan <avetik.yessayan at shte.am> wrote: > > Dear colleagues, I like to put forward my candidacy on WG co-chair. You've probably not helped your candidacy by breaking two of the golden rules of mailing list etiquette. :-) Could everyone please take care to use meaningful and relevant Subject: headers? And in particular, *never, ever* reply to a list digest message. Thanks. In case this needs further explanation, here's what I posted about this subject last year: Replies to message digests create unnecessary and easily avoided problems. Here are the main ones: [1] It messes up the article threading used by everybody’s mail clients. [2] It’s not clear which message(s) in the digest are being replied to. [3] The list archives contain completely useless Subject: headers (like "iot-wg Digest, Vol X, Issue Y”) which make it difficult when browsing the archives to find out who said what and when. Item [3] becomes a real nuisance if/when there’s a need to consult the list archives to verify a consensus decision or review the development of things such as policy proposals.
- Previous message (by thread): [iot-wg] iot-wg Digest, Vol 21, Issue 1
- Next message (by thread): [iot-wg] Draft minutes from RIPE77
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]