🚀 go-pugleaf

In article <1992Oct27.110112.1017@beckman.com>, dsroberts@beckman.com writes:
>So I would like to ask that a newsgroup called
>
>vmsnet.decus.journal
>
>be created for this purpose.  We would like it moderated so that any replies
>can be processed by the journal editor before posting to the newsgroup.

This sounds perfectly acceptable to me. (Sorry for the delay, I was out of town
much of last week.)

I agree with Jeff Killeen that since this is a request from DECUServe, there's
no reason for us to bend over backwards to re-fight the VMS vs. everyone else
naming battles. Don's list of reasons for coming here tell me that DECUServe is
aware of the alternatives, has considered them, and has chosen VMSnet. If other
units of DECUS have a problem with this, they'll have to take it up with
DECUServe. Last time the flap was because we as a community made a decision that
many felt undercut relevant portions of DECUS. That is clearly not the case
here. People may complain, but if they complain to us, they are talking to the
wrong people. 

DECUServe knows their business better than I do, so what right do I have to
question their decision? We only have to decide whether to grant the request or
not. Don has made it clear that they may move the journal to a new home if
circumstances warrant, so if they decide this was a bad decision, they'll fix
it. In either case, we are merely being asked to provide a place for the
Journal.

I think we should. I'll wait a bit to see if there are any objections.

I guess the only thing I wonder is whether vmsnet.decus.journal is sufficiently
descriptive. On the other hand, given that we've got vmsnet.decus.lugs, I'd hate
to add a vmsnet.decuserve.* subtree, and vmsnet.decus.decuserve.journal seems
unwarranted, unless more decus and/or decuserve groups get created. On balance,
it seems to me that the proposed name is the best compromise, with the caveat
that we may someday need to change the name to differentiate among various decus
activites, or to collect various decuserve activities, in either case by
renaming the group to vmsnet.decus.decuserve.journal.

Don, creating a moderated group is a little more work, and takes a little
longer, because I have to coordinate with Gene Spafford. Please send me the
address that will be used to submit articles, and "administrative" address that
will reach the moderator, and the moderator's actual name. Spaf needs this info
to update the various periodic postings, and won't set up the posting aliases
till he gets it. The group can not actually become active until the aliases are
installed in all participating backbone groups.

(Note to ANU users, it is neither necessary or desirable for you to add the
group and moderator address to your mailpaths file, or with a set
newsgroup/moderator=xxx command, contrary to anything that the documentation
might say. Set up your mailpaths file as described in the monthly posting to
news.announce.newusers just once and then forget about the whole thing. That's
what moderator aliases are for.)
--
Terry Poot <tp@mccall.com>                   The McCall Pattern Company
(uucp: ...!rutgers!depot!mccall!tp)          615 McCall Road
(800)255-2762, in KS (913)776-4041           Manhattan, KS 66502, USA