mirror of
https://github.com/boostorg/more.git
synced 2025-03-23 13:10:09 +08:00
Updated posting guidelines
[SVN r22566]
This commit is contained in:
parent
ff37d79f3c
commit
160cc4b032
@ -32,7 +32,7 @@ and dies.</p>
|
||||
<dl>
|
||||
<dt><a href="#acceptable">Acceptable Topics</a><dd>
|
||||
<dt><a href="#unacceptable">Unacceptable Topics</a><dd>
|
||||
<dt><a href="#quoting">Quoting and Message Size</a><dd>
|
||||
<dt><a href="#quoting">Effective Posting</a><dd>
|
||||
<dt><a href="#behavior">Prohibited Behavior</a><dd>
|
||||
<dt><a href="#culture">Culture</a><dd>
|
||||
</dl>
|
||||
@ -58,13 +58,14 @@ will let you know.</p>
|
||||
newsgroup instead.</li>
|
||||
<li>Job offers.</li>
|
||||
<li>Requests for solutions to homework assignments.</ul>
|
||||
<h2><a name="quoting"></a>Quoting and Message Size</h2>
|
||||
<h2><a name="quoting"></a>Effective Posting</h2>
|
||||
|
||||
<p>Please <b>limit the amount of quoted text</b> in replies to this
|
||||
list. Some people have to pay for, or wait for, each byte that they
|
||||
download from the list. More importantly, it will save time and make
|
||||
your post more valuable when readers do not have to find out which
|
||||
exact part of a previous message you are responding to.
|
||||
<p>Please <b>prune extraneous quoted text</b> from replies so that
|
||||
only the relevant parts are included. Some people have to pay for, or
|
||||
wait for, each byte that they download from the list. More
|
||||
importantly, it will save time and make your post more valuable when
|
||||
readers do not have to find out which exact part of a previous message
|
||||
you are responding to.
|
||||
|
||||
<p>A common and very useful approach is to cite the small fractions of
|
||||
the message you are actually responding to and to put your response
|
||||
@ -107,9 +108,12 @@ href="http://www.tinyurl.com">tinyurl.com</a>. Citing the relevant
|
||||
portion of a message you link to is often helpful (if the citation is
|
||||
small).
|
||||
|
||||
<p>Don't forget, it's a single writer but there are many readers.
|
||||
So, saving some time for the readers is worth spending extra
|
||||
time when writing a message.
|
||||
<p>Don't forget, you're a single writer but there are many readers,
|
||||
and you want them to stay interested in what you're saying. Saving
|
||||
your readers a little time and effort is usually worth the extra time
|
||||
you spend when writing a message. Also, boost discussions are saved
|
||||
for posterity, as rationales and history of the work we do. A post's
|
||||
usefulness in the future is determined by its readability.
|
||||
|
||||
<p>The mailing list software automatically limits message and
|
||||
attachment size to a reasonable amount, typically 75K, which is
|
||||
@ -117,6 +121,22 @@ adjusted from time-to-time by the moderators.. This limit is a
|
||||
courtesy to those who rely on dial-up Internet access.
|
||||
</p>
|
||||
|
||||
<p><b>When starting a new topic, always send a fresh message</b>,
|
||||
rather than beginning a reply to some other message and replacing the
|
||||
subject and body. Many mailers are able to detect the thread you
|
||||
started with and will show the new message as part of the original
|
||||
thread, which probably isn't what you intended. Follow this guideline
|
||||
for your own sake as well as for others'. Often, people scanning for
|
||||
relevant messages will decide they're done with a topic and hide or
|
||||
kill the entire thread: your message will be missed, and you won't get
|
||||
the response you're looking for.
|
||||
|
||||
<p><b>Do not reply to digests</b> if you are a digest delivery
|
||||
subscriber. Your reply will not be properly threaded and will
|
||||
probably have the wrong subject line. Instead, you can reply through
|
||||
the <a href="http://news.gmane.org/gmane.comp.lib.boost.devel">GMane
|
||||
web interface</a>.
|
||||
|
||||
<h2><a name="behavior"></a>Prohibited behavior</h2>
|
||||
<p>Prohibited behavior will not be tolerated. The moderators will ban
|
||||
postings by abusers.</p>
|
||||
|
Loading…
Reference in New Issue
Block a user