[news.groups] Splitting comp.sys.amiga

peter@sugar.UUCP (Peter da Silva) (11/06/87)

I was initially opposed to splitting comp.sys.amiga. However it IS the highest
traffic group on the net. It would certainly look better on the regular traffic
reports if it were split (I'm sure the mac groups would beat it if they were
counted together, so this isn't just a pr campaign).

Suggestions:

	comp.sys.amiga.misc and comp.sys.amiga.guru

		I like this one just because of the name of the wizard group.

	comp.sys.amiga.500, cmp.sys.amiga.1000, and comp.sys.amiga.2000

		Often suggested. I think it stinks.

	comp.sources.amiga and comp.sources.amiga.d

		This would pull all the "bug in shell 2.05" stuff out of
		comp.sys.amiga. Probably the best solution. (The .d group
		would of course be unmoderated, and would serve the purpose
		of .bugs, .d, and .requests).

	comp.sys.amiga and comp.sys.amiga.newprod

		In the same vein as the above. Perhaps part of the problem
		is that stuff is being put in comp.sys.amiga that belongs
		in other groups? (no, I don't think so either)

	comp.sys.amiga.flames

		While popular, would undoubtedly be useless.

	comp.sys.peter.da.silva

		Has been suggested. Perhaps it should be changed to
		comp.sys.mike.meyers. (:->, in case you don't know)
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.

urjlew@ecsvax.UUCP (Rostyk Lewyckyj) (11/09/87)

Peter da Silva wants to split comp.sys.amiga and is already
plotting and choosing names for the new subgroups. O.k. then
I propose comp.sys.amiga1 and comp.sys.amiga2. People would
be requested to post alternately to each of the two groups
in order to achieve a balance in the volume of material in
each group. Alternately we could suggest to the high fluff
volume experts to cross post to the other groups, thus raising
their volumes so that the volume and S/N ratio of comp.sys.amiga
would look better in the eyes of the gods.
I suggest a concerted action team composed of Peter, Paul, and
Mike for implementing the second approach.
By the way thats Peter da Silva, Pauls Dolan and Higginsbottom,
and Mike Meyer.
Cheers to you all
Rostyk

mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer) (11/09/87)

In article <995@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
<I was initially opposed to splitting comp.sys.amiga. However it IS the highest
<traffic group on the net. It would certainly look better on the regular traffic
<reports if it were split (I'm sure the mac groups would beat it if they were
<counted together, so this isn't just a pr campaign).

Good luck. I don't think it's gonna split, though.

<	comp.sys.amiga.500, cmp.sys.amiga.1000, and comp.sys.amiga.2000
<
<		Often suggested. I think it stinks.

I like it a lot more than I used to. Then again, I wasn't seeing
people with pure-500 and pure-2000 problems then. My kill file now
throws out a non-trivial number of such postings (and it's still
missing some).

<	comp.sys.peter.da.silva
<
<		Has been suggested. Perhaps it should be changed to
<		comp.sys.mike.meyers. (:->, in case you don't know)

Hmm. Who is mike meyers, and what has he done to cause such a
suggestion?

I think the best suggestion (which you didn't pick up) was:

	comp.sys.amiga.hardware, comp.sys.amiga.software

This allows the A500 and A2000 to be split off later if it seems
apropriate.

	<mike
--
The sun is shining slowly.				Mike Meyer
The birds are flying so low.				mwm@berkeley.edu
Honey, you're my one and only.				ucbvax!mwm
So pay me what you owe me.				mwm@ucbjade.BITNET

richard@gryphon.UUCP (11/09/87)

In article <995@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>
>Suggestions:
>
>	comp.sys.amiga.misc and comp.sys.amiga.guru
>	comp.sys.amiga.500, cmp.sys.amiga.1000, and comp.sys.amiga.2000
>	comp.sources.amiga and comp.sources.amiga.d
>	comp.sys.amiga and comp.sys.amiga.newprod
>	comp.sys.amiga.flames
>	comp.sys.peter.da.silva

Sorry, don't like any of 'em. How 'bout:

	Comp.sys.amiga.general
	Comp.sys.amiga.programming
	Comp.sys.amiga.products

We've tried this here on a local BBS (PNET) and it work rather well.

>-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter


-- 
Richard J. Sexton
INTERNET:     richard@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4, nosc}!crash!gryphon!richard

"It's too dark to put the keys in my ignition..."

childs@cadnetix.UUCP (David Childs) (11/10/87)

Here are my views on a split up.  Maybe something like this:
comp.sys.amiga.misc
               guru
               hardware
               software
               languages
and maybe a few more if anyone can think of some.

David Childs  childs@cadnetix.UUCP  303 444-8075

richc@vaxwaller.UUCP (Rich Commins) (11/12/87)

	I suggest we create only this new group:

		comp.sys.CBM-bashing

	Half of all the traffic on this net recently has been destructive
	criticism of CBM and has no place here!


-- 
-- 
Rich Commins   (415)939-2400				          \  /\
Varian Instruments, 2700 Mitchell Drive, Walnut Creek, CA 94598    \/--\
{ptsfa,lll-crg,zehntel,dual,amd,fortune,ista,rtech,csi,normac}varian!richc

richard@gryphon.CTS.COM (Richard Sexton) (11/13/87)

In article <1089@cadnetix.UUCP> childs@cadnetix.UUCP (David Childs) writes:
>
>
>Here are my views on a split up.  Maybe something like this:
>comp.sys.amiga.misc
>               guru
>               hardware
>               software
>               languages
>and maybe a few more if anyone can think of some.

Nahh, too many. Misc and guru is the best delineation of the lot, 
but whose gonna read just one or tother ?

Hardware and software doesn't make much sense either as all hardware
has software aspects to it.

Software and languages seems a bit nebulous as well.

Nobody has comments on:

.general (or misc if you prefer)
.programming
.products 

???

>David Childs  


-- 
Richard J. Sexton
INTERNET:     richard@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4, nosc}!crash!gryphon!richard

"It's too dark to put the keys in my ignition..."

bilbo@pnet02.cts.com (Bill Daggett) (11/15/87)

Rich,

Do you think "bashing CBM" is really destructive?  I mean if it wasn't done
would CBM be getting "the message" about their products?  Or would we be
sending them a false message?  I know there is a taste factor to consider
always - but I think Commodore can take our shots.  Computers and products
that are talked up and down are "popular".

 Bill  Daggett -- a.k.a.
*Bilbo Baggins*  Recombinant Hobbit
* Sometimes The Dragon Wins! *

INTERNET: bilbo@pnet02.CTS.COM
    UUCP: {hplabs!hp-sdd!crash, ihnp4!scgvaxd }!gryphon!pnet02!bilbo
   WHAT?:

richc@vaxwaller.UUCP (Rich Commins) (11/17/87)

In article <2294@gryphon.CTS.COM>, bilbo@pnet02.cts.com (Bill Daggett) writes:
> Rich,
> 
> Do you think "bashing CBM" is really destructive?  I mean if it wasn't done
> would CBM be getting "the message" about their products?  Or would we be
	       ^^^^^^^^^^^^^^^^^^^^

	I think bashing CBM is destructive.  The message got across after
	the first dozen or so.  The repeats and negative comments
	WERE destructive.  I agree that feedback is necessary, but lets
	keep it on an UP beat and we'll all win BIG.



-- 
-- 
Rich Commins   (415)939-2400				          \  /\
Varian Instruments, 2700 Mitchell Drive, Walnut Creek, CA 94598    \/--\
{ptsfa,lll-crg,zehntel,dual,amd,fortune,ista,rtech,csi,normac}varian!richc