🚀 go-pugleaf

In article <callewisCJ59p9.I9A@netcom.com>, callewis@netcom.com (David Scott Lewis) writes:
>Since we're running off the listserv at U.C. San Diego, it's only natural 
>to gate to a bit.* USENET group.

Why?  Most of the bit.* groups are gated from LISTSERV mailing lists.

>However, comp.* will receive greater 
>exposure with our target market.  Hence, we'd like to gate HOTT to both.

I can see why you want a comp group, but I'm less clear on the advantage of
having both.

>Also, my understanding is that getting a comp.* will take a lot of time.  

It takes about two months, start to finish.

>(I admit, I might be dead wrong on this issue!)  But I'd like to have a 
>USENET-gated group concurrent with the launch of the first issue.

I don't want to rain on your parade, but that might not be reasonable.
Some things take time.

>And, quite frankly, I don't have a clue as to how to get approval for a 
>comp.* group.  Any and all suggestions will be greatly appreciated!  Thanks.

Well, before considering gatewaying to a comp group, you should become a lot
more clueful of the way USENET works.  Start with news.announce.newusers.

--
Dave Sill (de5@ornl.gov)             Computers should work the way beginners
Martin Marietta Energy Systems       expect them to, and one day they will.
Workstation Support                                            -- Ted Nelson
URL http://gatekeeper.dec.com/archive/pub/DEC/DECinfo/html/dsill.html