Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Re: [tdf-discuss] overall communication guidelines and reply-to mangling


Regina Henschel wrote:
I see no problem for this steps. That has worked all the time for
our German OOo-lists, so why shouldn't it work for an international
list? Users get a reply from the list moderator which describes what
to do.

Ugh. Citing the late OOo as something that has worked especially
well strikes me as at least debatable. ;)

I think the point you want to make is - "I'm used to this" - which
is fine, but the problem that is to be addressed here is mostly
about people *not* used to it, but coming from outside / the fuzzy
edges of this project. I would think, if all LibO lists would behave
similarly, it wouldn't take longer than a day or two to adapt
personal habits?

At any rate, here's the ultimate answer in this whole
reply-to-munging debate (for who ever is amenable to technical
argument):

 http://woozle.org/~neale/papers/reply-to-still-harmful.html

Cheers,

-- Thorsten

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.