home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.novell:11032 news.groups:25028
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!paladin.american.edu!howland.reston.ans.net!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!haven.umd.edu!mimsy!ra!atkinson
- From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
- Newsgroups: comp.sys.novell,news.groups
- Subject: Re: proposal to rename comp.sys.novell
- Message-ID: <C0AJJJ.5KC@ra.nrl.navy.mil>
- Date: 3 Jan 93 18:33:19 GMT
- References: <1i51t7INNep2@mudos.ann-arbor.mi.us> <shephard.726037323@sfu.ca> <1993Jan3.141802.16593@infodev.cam.ac.uk>
- Sender: usenet@ra.nrl.navy.mil
- Distribution: na
- Organization: Naval Research Laboratory, DC
- Lines: 26
-
-
- In the interest of consistency with existing practice and many other
- somewhat related newsgroups (e.g. comp.os.msdos.*), I'd suggest
- something much more like this:
-
- rename comp.sys.novell to be comp.os.netware.misc
-
- Any other subgroups that might be needed really belong in comp.os.netware.*
- For example, the existing practice is to name groups ~.programmer
- rather than ~.programmING, so for such a group one would create:
- comp.os.netware.programmer
-
- RATIONALE:
- There is much experimental evidence that inappropriate cross-posting
- of news articles is minimised when all of the related newsgroups exist
- at the same level of heirarchy. So even if no subgroups are created
- right away, it is desirable to start the basic group with the ~.misc
- label and at the right level of heirarchy from the start. Renamings
- tend not to work well, so whenever it is practical, we should minimise
- the number of renamings that might be needed in the future.
-
- ASIDE:
- The comments under "RATIONALE" probably belong in some FAQ on the
- newsgroup creation process. They certainly are not my own ideas,
- rather they are widespread amongst net.oldtimers as part of the
- collected wisdom of the net.
-