[mod.newprod] Administrivia

netnews@wnuxb.uucp (Ron Heiby) (02/05/86)

Hi!  Several people have sent me mail asking for more information about
one thing or another that has been announced in mod.newprod.  This was
probably done via the "reply" function of their news reading software.
A reminder, though, that I am just the moderator.  I don't represent the
products being announced in any way.  So, please send your requests for
more information to the contact listed in the BODY of the message.  My
.signature is appended to all the articles simply because I can't figure
out how to make inews ignore it.  While I'm talking here, here's the
mod.newprod guidelines.  Guideline "E" is new, modifying "D".  Thanks.

	A) Announcements should ideally fit within about 15 screen lines.
	B) There must be a name and address (electronic and postal) for
	   receiving more information.  (A phone number is suggested.)
	C) Announcements that look like advertising hype to the moderator
	   will be edited and returned to the submitter for approval.
	D) Announcements should happen no more than once.
	E) Certain "events" happen more than once, like UniForum, seminars,
	   and training courses.  Announcements of this nature may repeat
	   if there is real value to the community in doing so.

Announcements can go over the 15 line suggested limit if they appear to
be of general interest and contain sufficient meat to be worth people's
time to look at it.  I am open to further suggestions on modifications
to the guidelines.

Conflict-of-Interest Policy:  My position on AT&T products is that I will
not generate an announcement for any products and that AT&T products must
meet the same guidelines as other products.

Submissions should be sent to newprod@cbosgd.UUCP and comments/questions
to newprod-request@cbosgd.UUCP.  Thanks.
-- 
Ron Heiby {NAC|ihnp4}!cuae2!usenet   Moderator: mod.newprod & mod.os.unix
AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109

usenet@cuae2.ATT.COM (Ron Heiby) (07/02/86)

Hi!  Several people have sent me mail asking for more information about
one thing or another that has been announced in mod.newprod.  This was,
in this case probably due to mod.newprod material being re-posted to an
MS-DOS interest group without the full signature info that reminds people
that I am just the moderator.  I don't represent the products being announced
in any way.  So, please, if you are including mod.newprod material in another
forum, please be sure that people know to send their requests for
more information to the contact listed in the BODY of the message.

While we're "chatting", I've been getting some rather longer submissions
than I had planned on (>15 screen lines).  I bounced one that I thought was
mostly fluff, and it came back much meatier.  Others (about to be posted)
don't contain very much fluff.  So, I'm changing guideline A to modify
the length guideline.  Also, I'm changing guideline C to give myself more
lattitude.  Guideline F is new.  Let me know if you don't like the changes.
Thanks.

	A) Announcements should (within about 15 screen lines) present
	   enough information that the reader can make an intelligent
	   decision on whether or not to view the entire announcement.
	   "To the point" Subject lines are very important, too.
	B) There must be a name and address (electronic and postal) for
	   receiving more information.  (A phone number is suggested.)
	C) Announcements that look as though they contain advertising
	   hype (or other fluff) to the moderator will be edited.  They
	   may be returned to the submitter for approval before posting.
	D) Announcements should happen no more than once.
	E) Certain "events" happen more than once, like UniForum, seminars,
	   and training courses.  Announcements of this nature may repeat
	   if there is real value to the community in doing so.
	F) Between mailer delays and my working on my real job, there may
	   be a lag of as much as a couple of weeks between the time you
	   submit your announcement and the time it gets posted.  I am
	   sorry that the delay exists.  Please plan ahead with any postings
	   of a time-critical nature, to be sure the posting happens in
	   time.  (Also, although I try to send mod.newprod directly to
	   several backbone sites, some areas of the net are apt to experience
	   an additional week of delay after I post an aritcle.)

I am open to further suggestions on modifications to the guidelines.

Conflict-of-Interest Policy:  My position on AT&T products is that I will
not generate an announcement for any products and that AT&T products must
meet the same guidelines as other products.

Submissions should be sent to newprod@cbosgd.ATT.COM and comments/questions
to newprod-request@cbosgd.ATT.COM.  Thanks.
-- 
Ron Heiby {NAC|ihnp4}!cuae2!usenet   Moderator: mod.newprod & mod.os.unix
AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109
Submissions should go to newprod@cbosgd.uucp.
Comments to the moderator should go to newprod-request@cbosgd.uucp.
Requests for information should go to the author of the message.

usenet@cuae2.ATT.COM (07/07/86)

This message is mainly to try to be sure that everyone is aware that
the 68010 announcement from NetResults was the victim of an amazing
set of circumstances that made it *appear* bogus.  I have talked with
the submitter of the article at the phone number that wasn't working
last week when I checked.  I have talked with the president of the
telemarketing firm that is running the "800" service for NetResults.
He made it clear that it was his firm's fault, and not NetResults'.

I've also talked with NetResults' contact at Convergent Technologies,
who also assures me that NetResults is a real company dealing with C.T.

I'd encourage you to give NetResults the same chance that you would have
had the mess not occurred.  I apologize for any confusions or problems I
may have contributed to.  The person from NetResults that I spoke with
seemed genuinely concerned and professional.

I'd also like to thank all those who sent in suggestions.  I appreciate
your concerns and will consider your suggestions, even though this
incident doesn't require any special further action.  I'd encourage
you to send in any suggestion that you think may help mod.newprod be
a more useful/better service.  Thanks.
-- 
Ron Heiby {NAC|ihnp4}!cuae2!usenet   Moderator: mod.newprod & mod.os.unix
AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109
Submissions should go to newprod@cbosgd.uucp.
Comments to the moderator should go to newprod-request@cbosgd.uucp.
Requests for information should go to the author of the message.

usenet@cuae2.UUCP (Netnews Admin) (07/28/86)

Again, thanks for all the suggestions on bogus articles, and a reminder
in case you missed it, that the 68K box turned out not to be a hoax after
all.

Also, we had a bit of a head crash on the drive that holds our mailboxes,
so it is possible that up to two days worth of mail destined for mod.newprod
was lost.  There is no backlog now, so if you haven't seen your submission
and submitted it more before 7/22, you might re-send it and accept my
apologies.

I have received a couple of postings lately that I consider questionable.
One was for inexpensive floppy disks.  I rejected it on the grounds that
anyone in the market for floppies had ample selection in the ad pages of
magazines such as Byte, and that inexpensive floppies weren't all that
unusual.  It and another were already posted to other newsgroups.  I feel
that since they were already posted elsewhere, that they shouldn't be
posted here.  Anyone submitting an article who wants it cross-posted, should
let me know, and if it's appropriate and doesn't infringe on the customs
of that other group (to my knowledge), I'll cross-post it.  That way, people
will see it only once.  Thanks.
-- 
Ron Heiby usenet@cuae2.ATT.COM	Moderator: mod.newprod & mod.os.unix
AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109
Submissions should go to newprod@cbosgd.uucp.
Comments to the moderator should go to newprod-request@cbosgd.uucp.
Requests for information should go to the author of the message.

usenet@mcdchg.UUCP (03/27/87)

With my move from AT&T to Motorola and machine cuae2 to mcdchg, there
has been some confusion as to proper address for submissions to mod.newprod
and mod.os.unix.  Some messages are still being sent to cuae2.  Forwarding
of those messages does not happen reliably or often, so please check
(especially on pre-2.11 sites) to make sure your submissions aren't going
to those old addresses.  Sorry for the inconvenience.  Thanks.
-- 
Ron Heiby usenet@mcdchg.UUCP	Moderator: mod.newprod & mod.os.unix