Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!jarthur!bgribble From: bgribble@jarthur.Claremont.EDU (Bill Gribble) Newsgroups: comp.sys.handhelds Subject: Re: New newsgroup? Message-ID: <10850@jarthur.Claremont.EDU> Date: 16 Feb 91 09:33:59 GMT References: <3476@gmuvax2.gmu.edu> <1991Feb15.161438.25961@rodan.acs.syr.edu> Organization: Harvey Mudd College, Claremont, CA 91711 Lines: 31 In article mamos@uafhp.uark.edu (Mark _E_ Amos) writes: > > SOME sort of division must occur, and bickering about the best way to do it > will get us nowhere -why don't we just separate hp stuf first and THEN worry > about yet more subgroups. 1.) the conclusion that a division needs to happen is FAR from foregone. At this point I can say for certain that I would vote no on any split that's been proposed; they all seem too frivolous. Not to say that I wouldn't change my mind were a better idea to come up. 2.) What makes you think that, even if there is a split, it has to be the HP people who leave? I've been reading this newsgroup for well over a year, not nearly long enough to have been around when it formed but long enough to see that, if the HP users didn't form the group as an HP forum, they certainly have squatter's rights by now. As has been said before, the non-HP volume on this group is too low to merit its own newsgroup, but if you want it that badly form your own newsgroup rather than kicking the HP users out. Sorry if I offend anyone, but this discussion has gone on too long. An idea: I'll conduct an informal straw poll. Send me mail with the subject line "HP Split" and your vote in the body - nothing specific, just a 'yes' if you're for the idea of the split or a 'no' if you want to maintain status quo. Feel free to include comments, with the knowledge that I may post them in my summary. ***************************************************************************** ** Bill Gribble Harvey Mudd College, Claremont, CA ** ** bgribble@jarthur.claremont.edu Never heard of it? You're stupid. ** *****************************************************************************