On 10/26/2010 4:18 PM, Friedrich Strohmaier wrote:
Hi Barbara, *,
Barbara Duprey schrieb:
On 10/26/2010 1:31 PM, Friedrich Strohmaier wrote:
Hi TDF enthusiasts,
I changed the footer for mails of this list.
[..]
I'd prefer having a wiki page containing a short 3 step guide
summarizing that tipps and link there. If somebody would set up one
would be a great thing.
[..]
I notice that the footer has gone back to implying that +help will
accomplish the unsubscribe, rather than providing instructions --
this was fixed before,
I'm not aware of that..
I can look up the discussion, but it was changed for a while (maybe only on the users list? think it
was Florian...).
it's misleading. It would be best to provide both unsubscribe
addresses and the help one:
Email to discuss+unsubscribe@libreoffice.org to unsubscribe from the
list Email
to discuss+unsubscribe-digest@libreoffice.org to unsubscribe from the
list digest.
Email to discuss+help@libreoffice.org for general help information.
too long! I had to fight for "permission" of four lines max. 80 chars
each..
Or if that is regarded as making the footer too cumbersome, just point
to the general help but without implying it will actually do the
unsubscribe:
Email to discuss+help@libreoffice.org for help with list
operations such as unsubscribing.
How would You pack that in max. 80 chars?
In the other discussion, it was mentioned that the longer lines were a problem because they wrapped
inside the mailto, so I suggested starting the message with "Email to" as you've done here -- but
from what you say they're not allowed to exceed 80 characters at all. If so, I'd just leave off the
last three words. People looking to unsubscribe certainly should know that's a list operation.
Another option would be to make it "for help with unsubscribing" -- but it does more than just that.
Or even leave out the "with" there. I'm just trying to avoid the implication that using +help is
itself the way to unsubscribe.
[..]
The other footer info looks OK, though possibly the guideline
information should be incorporated into our own support structure
rather than referencing an outside source. That would allow tailoring
it to reflect specific guidelines for our lists, if desired.
Exactly that's what I asked for someone to realize in a wiki page, to
link at instead. Would You like to do that? :o))
What I'm planning is to set up a discussion wiki for collaboration on what would most likely become
a Support page that contained, or if necessary linked to, all the information we'd like people to
consider when they're looking for help -- use of FAQs, forums, mailing lists, archives, issue
trackers, etc. If this were properly organized, it could be referenced by, say, moderators receiving
posts from unsubscribed users. I'm trying to come up with a strawman for the structure to get the
ball rolling.
There is some effort going on about the whole issue of how to support
users at their first point of contact, whatever that is, and I think
your suggestion fits in that discussion very well. Thanks!
my pleasure :o))
btw.: Do You or someone else have a link to a good mailinglist
netiquette. Quoting ist just *one* aspect of writing good mails in a
mailing list.
Gruß/regards
How about www.openoffice.org/ml_guidelines.htm?
--
Unsubscribe information: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
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.