Common Reasons for Rejection

[Osma Ahvenlampi]

Common Reasons for Rejection

July 15, 1997

This file is a supplement to the documents "Instructions for
Submissions" and "Guidelines for Software Announcements," which are
posted at the same time as this one. Read those documents before you
read this document. This document is a list of common reasons that I
give for rejecting posts or asking for revisions. Before you post,
please check it to see if your message could be rejected for any of
these reasons.

ALL ANNOUNCEMENTS
This section gives common reasons for rejection of all announcements.
* Your message includes only an e-mail address, but not your name.
Please include your full name.
* Nowhere in this post did you explain why you are authorized to
make this announcement. Please include a short note in your post
explaining your relationship to this subject material.
* Your post is just too long. Please write a shorter announcement
with only the important information, and provide a source (perhaps
e-mail) from which people can request more information.
* Your post is right-justified. All submissions must have a ragged
right-hand margin.
* You obviously didn't read the administrative posts carefully.
Please do so and try again.
* Your post contains numerous spelling or diction errors. If your
native language is not English, let me know, then I will try to
fix them myself. Otherwise, fix them (perhaps with a
spell-checker) before you send this post in again.
* Your post is too full of hype, denigrating comparisons with
competing products, or other inappropriate material.

SOFTWARE ANNOUNCEMENTS
* You are not using the proper URL format. Please see the document
"Guidelines for Software Announcements" for an explanation of how
to do this. The document is available from the mail server at
<be-an...@warped.com> and can be found in the newsgroup.
* Your description section is much too long. Please describe the
important features. People interested in the details can read the
documentation.
* You gave me the documentation instead of an announcement. Please
write an announcement appropriate for this newsgroup.
* Your announcement contains a list of every single minor feature
and bug fix added since the last version. Please include only the
important new features and the major bug fixes.
* You described the new features of your system, but you never
actually said what the system does. Please do so.
* Your announcement uses jargon that is impossible for novice Be
users to understand. Please explain the background so that any
reader of this newsgroup who might be interested can understand
it.
* You took a section from your documentation and listed every single
new feature of this version. That is not appropriate for an
announcement. Please tone down that section and list only the
important new features. People who really need to know about every
single new feature can download the software and read the
documentation.

_________________________________________________________________

This document was heavily inspired by the comp.sys.amiga.announce
documentation, written by Dan Zerkle. Thanks, Dan!

--
Osma Ahvenlampi comp.sys.be.announce moderator
be-an...@warped.com Announce submissions
be-announ...@warped.com Moderator contact address