🚀 go-pugleaf

In the referenced article DOUG@ysub.ysu.edu (Doug Sewell) writes:
#In article <91050.181303JIM@auvm.auvm.edu>, Jim McIntosh <JIM@auvm.auvm.edu>
#says:
#>A gateway  has been  established at  AUVM.BITNET to  connect WIN3-L@UICVM
#>with a new NETNEWS list bit.listserv.win3-l.
#
#Any particular reason to gateway it as a bit. group, rather than to
#comp.windows.ms ?

I was thinking the same thing.    We have hundreds of 'main net' groups,
and loads of bit.listserv ones, and quite a few overlap.   That's a problem
for users who don't have the time to read every single newsgroup (i.e. all
users).   However there may be historic reasons which prevent the overlaps
being fixed.

Here we have a new gateway with no history.   Couldn't we have discussed
whether it should have been to the existing windows news group?

Please don't tell me that the BITNET people don't have to discuss bit.
groups with the main net - I know that.  But here's a case where some
discussion would be a good idea.

So - could the list gateway to comp.windows.ms?   Should it? 
The benefit could be better interchange of information about MS Windows.
What are the problems, if any?

Regards,          "None shall be enslaved by poverty, ignorance or conformity"
        David Wright             STL, London Road, Harlow, Essex  CM17 9NA, UK
dww@stl.stc.co.uk  <or> ...uunet!mcsun!ukc!stl!dww  <or> PSI%234237100122::DWW
<or> /g=David/s=Wright/org=STC Technology Ltd/prmd=STC plc/admd=Gold 400/co=GB