home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mozz.unh.edu!kepler.unh.edu!pss1
- From: pss1@kepler.unh.edu (Paul S Secinaro)
- Newsgroups: news.groups
- Subject: Re: RFD: comp.os.nt
- Date: 25 Jan 1993 12:48:22 GMT
- Organization: University of New Hampshire - Durham, NH
- Lines: 37
- Message-ID: <1k0nimINNbtt@mozz.unh.edu>
- References: <1jvvqbINNeqn@rodan.UU.NET>
- NNTP-Posting-Host: kepler.unh.edu
- Keywords: Microsoft Windows NT Win32
-
- In article <1jvvqbINNeqn@rodan.UU.NET> georged@sequent.com (George Dolbier) writes:
- >PROBLEMS:
- >---------
- > First problem: the name. comp.os.nt is short and to the point,
- >but maybe too short. comp.os.windows-nt is too long, comp.os.windowsnt
- >is too mushed, comp.os.ms-windows.nt IS NOT the correct location.
-
- How about comp.os.winnt or comp.os.win-nt? Might be a little too
- abbreviated, though. I don't mind comp.os.nt myself.
-
- > Second problem: subgroups. Initialy comp.os.nt will be enough to
- >hold all discussions relating to Windows NT. But soon it will become
- >apparent that subgroups will need to be created. Cross that bridge
- >when we come to it is what I say.
-
- It might be better to create subgroups from the start. That way, you
- don't get people posting to the comp.os.nt node forever, like has
- happened with some other group splits. Maybe something along the
- lines of:
-
- comp.os.nt.
- .programmer (possibly splitting into subgroups by API?)
- .apps
- .setup
- .drivers
- .misc
- .advocacy (of course! :-) )
-
- Paul
-
-
-
- --
- Paul Secinaro
- pss1@kepler.unh.edu
- Synthetic Vision and Pattern Analysis Laboratory
- UNH Dept. of Electrical and Computer Engineering
-