<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.big-8.org/w/index.php?action=history&amp;feed=atom&amp;title=Nan%3A2025-06-12-mf-comp.newprod</id>
	<title>Nan:2025-06-12-mf-comp.newprod - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.big-8.org/w/index.php?action=history&amp;feed=atom&amp;title=Nan%3A2025-06-12-mf-comp.newprod"/>
	<link rel="alternate" type="text/html" href="https://www.big-8.org/w/index.php?title=Nan:2025-06-12-mf-comp.newprod&amp;action=history"/>
	<updated>2026-05-15T10:11:55Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>https://www.big-8.org/w/index.php?title=Nan:2025-06-12-mf-comp.newprod&amp;diff=4248&amp;oldid=prev</id>
		<title>Rayner Lucas: Page creation</title>
		<link rel="alternate" type="text/html" href="https://www.big-8.org/w/index.php?title=Nan:2025-06-12-mf-comp.newprod&amp;diff=4248&amp;oldid=prev"/>
		<updated>2025-06-12T21:20:24Z</updated>

		<summary type="html">&lt;p&gt;Page creation&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;lt;pre&amp;gt;From: Big-8 Management Board &amp;lt;board@big-8.org&amp;gt;&lt;br /&gt;
Newsgroups: news.announce.newgroups,news.groups.proposals,comp.newprod&lt;br /&gt;
Subject: MODERATOR FOUND: comp.newprod&lt;br /&gt;
Followup-To: news.groups.proposals&lt;br /&gt;
Date: Thu, 12 Jun 2025 16:59:36 EDT&lt;br /&gt;
Message-ID: &amp;lt;MPG.42b54ff3bf9863519896f7@news.eternal-september.org&amp;gt;&lt;br /&gt;
Archive-Name: comp.newprod&lt;br /&gt;
&lt;br /&gt;
REPLACEMENT MODERATOR FOUND&lt;br /&gt;
comp.newprod&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Big-8 Management Board is pleased to announce that Ivan Shmakov has&lt;br /&gt;
volunteered to take on moderation duties for comp.newprod. The group&lt;br /&gt;
will be open for submissions shortly, and this will be announced in a &lt;br /&gt;
post to the group.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
MODERATOR INFO: comp.newprod&lt;br /&gt;
&lt;br /&gt;
Moderator: Ivan Shmakov&lt;br /&gt;
Article submission address: &amp;lt;comp-newprod-submit@newsmod.am-1.org&amp;gt;&lt;br /&gt;
Moderation contact: &amp;lt;comp-newprod-contact@newsmod.am-1.org&amp;gt;&lt;br /&gt;
&lt;br /&gt;
POSTING GUIDELINES FOR COMP.NEWPROD:&lt;br /&gt;
&lt;br /&gt;
[No charter is on file with the ISC for comp.newprod; the following &lt;br /&gt;
guidelines are taken from the periodic posting &amp;quot;Comp.Newprod submission &lt;br /&gt;
guidelines&amp;quot;, posted monthly until 2018-07-15]&lt;br /&gt;
&lt;br /&gt;
1. The submission must be an announcement of a new product or&lt;br /&gt;
service. The product must be computer-related, and it must be of&lt;br /&gt;
potential interest to a large number of Usenet readers. The&lt;br /&gt;
message must be of lasting value, thus we do not accept trade show&lt;br /&gt;
announcements, special pricing offers, etc. Commercial messages&lt;br /&gt;
other than new product announcements are not appropriate for this&lt;br /&gt;
newsgroup.&lt;br /&gt;
&lt;br /&gt;
2. Announcements should *briefly* describe the product, requirements&lt;br /&gt;
(e.g. supported platforms), availability, and pricing. It should&lt;br /&gt;
only take a couple of screenfuls to convey this information. If&lt;br /&gt;
your description is longer than that, then you&amp;#039;ve either got too&lt;br /&gt;
much detail or too much fluff. All you should do here is summarize.&lt;br /&gt;
Anybody who is interested will contact you for the additional&lt;br /&gt;
information. Similarly, do not include lengthy product matrices&lt;br /&gt;
or order forms; ask interested people to write to you for a copy.&lt;br /&gt;
The ideal length is on the order of 60 lines (excluding headers).&lt;br /&gt;
If your message is much longer, it needs tighter editing. (Please&lt;br /&gt;
note, excessive length is the most common reason for rejecting&lt;br /&gt;
submissions.)&lt;br /&gt;
&lt;br /&gt;
3. The announcement must be informative. It must contain a brief&lt;br /&gt;
technical description of the product or service, subject to the&lt;br /&gt;
length constraints just mentioned. This newsgroup is NOT a place&lt;br /&gt;
for advertisements! It is a place for factual product info.&lt;br /&gt;
&lt;br /&gt;
4. The product must be available to all Usenet users throughout&lt;br /&gt;
North America, if not the world. Products with regional availability&lt;br /&gt;
should be announced in regional newsgroups, not comp.newprod.&lt;br /&gt;
&lt;br /&gt;
5. All announcements must contain the manufacturer&amp;#039;s name and a&lt;br /&gt;
contact for additional information. This should include a name,&lt;br /&gt;
telephone number, postal address, and email address. Americans,&lt;br /&gt;
please remember that your 1-800 telephone number might not work&lt;br /&gt;
for people outside the U.S.&lt;br /&gt;
&lt;br /&gt;
6. The announcement must be from a representative either employed&lt;br /&gt;
by or designated by the product&amp;#039;s manufacturer. We do not accept&lt;br /&gt;
announcements from distributors or resellers for products in mass&lt;br /&gt;
distribution.&lt;br /&gt;
&lt;br /&gt;
7. Leave out the quotations from your company executives and ecstatic&lt;br /&gt;
customers. If there is useful info in that quote, it may be&lt;br /&gt;
provided more concisely and compellingly as a statement of fact.&lt;br /&gt;
Moreover, we don&amp;#039;t need to know about your corporate history,&lt;br /&gt;
customer list, or distribution methods. Please avoid the superlatives&lt;br /&gt;
and superfluous hype. Just the (technical) facts, please. These&lt;br /&gt;
violations are the second most common reason (after message length)&lt;br /&gt;
for returning submissions.&lt;br /&gt;
&lt;br /&gt;
8. Note that a typical press release does NOT meet the above&lt;br /&gt;
guidelines. They tend to be either too long or too heavy on the&lt;br /&gt;
hype. We aren&amp;#039;t the press. We don&amp;#039;t want to edit (or spindle or&lt;br /&gt;
fold or mutilate) your announcements as the press might. We simply&lt;br /&gt;
want to publish them. You need to do the editing.&lt;br /&gt;
&lt;br /&gt;
9. Your article must have a suitable Subject, not something like&lt;br /&gt;
`submission for comp.newprod&amp;#039;. Do not use all UPPER CASE or&lt;br /&gt;
superfluous !!!punctuation marks!!! in your subject (or messages).&lt;br /&gt;
Putting phrases like `new product announcement&amp;#039; in your subject&lt;br /&gt;
is dumb. If it wasn&amp;#039;t it wouldn&amp;#039;t be in this newsgroup! Select&lt;br /&gt;
your subject with care; a person is going to decide whether or&lt;br /&gt;
not to read your announcement based upon those six short words.&lt;br /&gt;
&lt;br /&gt;
10. We almost never accept articles that are cross-posted to multiple&lt;br /&gt;
newsgroups or have been posted to other newsgroups. By definition,&lt;br /&gt;
if a message is appropriate for comp.newprod then it is NOT&lt;br /&gt;
appropriate for most other Usenet groups. One exception: some&lt;br /&gt;
`announce&amp;#039; groups accept product announcements, and we will cross-post&lt;br /&gt;
there if its moderator says OK.&lt;br /&gt;
&lt;br /&gt;
11. We do not accept articles with a limited `Distribution&amp;#039;. If you&lt;br /&gt;
have availability restrictions then do mention them in the&lt;br /&gt;
announcement, but the announcement must be submitted for distribution&lt;br /&gt;
throughout all of Usenet.&lt;br /&gt;
&lt;br /&gt;
12. If the contact person for additional information is not the person&lt;br /&gt;
who submitted the message, then put a `Reply-To&amp;#039; header in the&lt;br /&gt;
message. Do NOT try to redirect email to somebody else by saying&lt;br /&gt;
`send email to ...&amp;#039; in your announcement. People won&amp;#039;t. They&lt;br /&gt;
will just hit the `r&amp;#039; key and the message will go back to you.&lt;br /&gt;
If you do not know how to set a `Reply-To&amp;#039;, ask for help.&lt;br /&gt;
&lt;br /&gt;
13. We use a standard keywording system for all comp.newprod messages.&lt;br /&gt;
We require a `Keywords&amp;#039; header on your message. The format is&lt;br /&gt;
`Keywords: company name; product name; keyword, keyword, keyword ...&amp;#039;.&lt;br /&gt;
We welcome (plead for!) your suggestions on keywords. If the&lt;br /&gt;
product is esoteric or outside our areas of expertise, we might end&lt;br /&gt;
up picking crummy keywords.&lt;br /&gt;
&lt;br /&gt;
14. Your message must be properly formatted, avoiding long lines&lt;br /&gt;
that wrap around a typical terminal screen and strange line breaks.&lt;br /&gt;
We suggest that you break your lines at 78 columns or less.&lt;br /&gt;
Whitespace is your friend (within reason). Carefully spell check&lt;br /&gt;
and proofread your submissions; nothing screams `unprofessional&amp;#039;&lt;br /&gt;
louder than poorly crafted prose. Please go easy on the Cap-Shift&lt;br /&gt;
key. Do NOT right-justify your text; leave `ragged right margins.&amp;#039;&lt;br /&gt;
We are not impressed that you can construct your company logo out&lt;br /&gt;
of Xs and /s. `ASCII art&amp;#039; and gratuitous typesetting effects are&lt;br /&gt;
discouraged. A double pox on people who use overly long signatures.&lt;br /&gt;
&lt;br /&gt;
15. If you fear the headers of your message might get mangled in&lt;br /&gt;
transit, feel free to note correct header information at the very&lt;br /&gt;
top of your message. Clarifying comments addressed to the moderator&lt;br /&gt;
also may be placed at the top of your message. If, while you are&lt;br /&gt;
at it, you&amp;#039;d like to suggest some keywords for your message, that&lt;br /&gt;
would be great. We will cleanup the headers and remove these&lt;br /&gt;
comments prior to posting.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
DISTRIBUTION&lt;br /&gt;
&lt;br /&gt;
news.announce.newgroups&lt;br /&gt;
news.groups.proposals&lt;br /&gt;
comp.newprod&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
CHANGE HISTORY&lt;br /&gt;
&lt;br /&gt;
2025-06-12 Announcement&lt;br /&gt;
&lt;br /&gt;
-- &lt;br /&gt;
Usenet Big-8 Management Board&lt;br /&gt;
https://www.big-8.org/&lt;br /&gt;
board@big-8.org&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rayner Lucas</name></author>
	</entry>
</feed>