Mailing List Rules » History » Version 8

laforge, 04/16/2016 01:03 PM
clarify HTML requirement

1 6 laforge
2 1 laforge
3 6 laforge
h1. Project Osmocom mailing list rules
4 6 laforge
5 6 laforge
6 1 laforge
You are strongly advised to go through these set of rules before posting to any of the Osmocom mailing lists.
7 3 laforge
8 1 laforge
Failure to comply with list rules may result in removal of your messages from the archive, forced unsubscription/ban from the list, or setting your status to moderated.
9 1 laforge
10 1 laforge
11 6 laforge
h2. Subject Line
12 6 laforge
13 6 laforge
14 1 laforge
Make sure that your post contains a valid subject line containing a gist of your post rather than things like 'Help!!!', 'HELP ME PLEEEEEASE', 'Urgent Request' or 'Proposal'.
15 1 laforge
16 1 laforge
Also, don't be afraid to modify the subject if a discussion has moved to a different topic than that originally present in the subject!
17 1 laforge
18 1 laforge
19 6 laforge
h2. Top-posts
20 6 laforge
21 6 laforge
22 1 laforge
Do not "top-post/full-quote" (reply to a message by adding text to the top of the message and quoting the full original message), as it loses the reader and the flow of the message and can annoy other readers.
23 1 laforge
24 1 laforge
For more information, see
25 1 laforge
26 1 laforge
27 6 laforge
h2. Overquoting
28 6 laforge
29 6 laforge
30 1 laforge
If you are replying to another message, quote only the portions of that message that you are specifically responding to, and insert your comments after those quotes. Do not simply quote back the entire message! Trim off everything apart from the most relevant lines of the original message.
31 1 laforge
32 1 laforge
In general, your reply should contain at least as much text as the amount of text you are quoting, if not more. Never quote back dozens of lines of text and simply add a single line of text to the bottom - people will *hate* you for that!
33 1 laforge
34 6 laforge
h2. HTML Messages
35 6 laforge
36 6 laforge
37 1 laforge
HTML is not email, and email doesn't contain HTML, so please turn HTML formatting OFF in your email client. Do not use italics, colors, bold, fonts, pictures, sounds, or other HTML elements. Please use only 7-bit characters when sending email to the lists, with proper quoted printable encoding.
38 1 laforge
39 8 laforge
The above applies both to HTML-only e-mail, as well as to e-mail that contains an alternative HTML portion together with plain-text.
40 8 laforge
41 8 laforge
Mails should always be plain-text only.
42 1 laforge
43 6 laforge
h2. Message Recycling / Threading
44 6 laforge
45 6 laforge
46 1 laforge
Do not start a New message or thread by hitting "Reply" in your mail client and changing the subject. When you do this, you mess up other participant's ability to read mail in a threaded fashion. When you mean to post a new message, use New, and when you want to reply to an existing message, hit Reply.
47 1 laforge
48 1 laforge
49 6 laforge
h2. Pseudo-legal disclaimers
50 6 laforge
51 6 laforge
52 1 laforge
Do not attach obnoxious pseudo-legal, nonsensical disclaimers to your messages. People on Free Software / open source lists do not like to be threatened with these. If your company insists on attaching such disclaimers to messages going out to mailing lists (where, by definition, the sender has *NO* control over who gets to see the message), then either use a free / webmail system, or just don't post.
53 1 laforge
54 1 laforge
55 6 laforge
h2. Off-topic
56 6 laforge
57 6 laforge
58 1 laforge
Stay on-topic for the list. This isn't a good place to discuss automobiles, politics, music, or anything that is not related to the respective Osmocom mailing list. Sometimes topics will diverge from the general discussion, but please try to keep it relevant to the list topic.
59 1 laforge
60 6 laforge
h2. No SPAM/UCE/UBE/Sales/Marketing/Commercials
61 6 laforge
62 6 laforge
63 3 laforge
The lists are for technical discussion of developers and users of the given Osmocom software project only.
64 3 laforge
65 1 laforge
*Do not send any spam, commercial announcements, product news, corporate press releases or other non-technical messages to our lists.*
66 7 laforge
67 7 laforge
This includes invitations to newsletters, whether contained in the body of your e-mail, or in the signature.
68 3 laforge
69 3 laforge
70 6 laforge
h2. Message time and date
71 6 laforge
72 6 laforge
73 1 laforge
Please make sure the date and time on your computer is always current. When your date is set to something such as the year 2099, messages posted by you will get sorted based on that date, which may put them outside of the related month or year they belong in.
74 1 laforge
75 6 laforge
76 6 laforge
h2. List Archives
77 6 laforge
78 1 laforge
79 1 laforge
All messages sent to one of our mailinglists will be archived in the mailinglist archive. The archives are accessible to any interested party, and email addresses will not be obscured.  Furthermore, it is customary practise for various other sites (like gmane, MARC, etc.) to keep their own independent list archives.
80 1 laforge
81 1 laforge
Thus, be careful in what you post.  After you have sent it, it will be distributed to hundreds of other project members and will be published in several public archives.
Add picture from clipboard (Maximum size: 48.8 MB)