🚀 go-pugleaf

In article <wjPQnMD0aez4@0humpty.tomate.tng.oche.de>, Humpty@TOMATE.TNG.OCHE.DE writes:
> 
> So what ? I don't understand all these discussions.....There will be a new
> system, which sooner or later will need all its belonging groups. So why
> not creating them now ? Why wait and waste bandwith with any future RfD ?

-- Because nobody really knows what groups will be necessary.  We
can't make an informed decision now, when the BeBox's markets are
still unclear.

-- Because time is of the essence.  The RFD for comp.sys.be has
already been made, but agreeing on a split up hierarchy would take
weeks or months.

-- Because the resulting fracas could easily result in no groups
getting approved at all, which would be a disaster.

-- Because the Be is still a very new system and it may be
counterproductive to split up its users so early.  Cross-pollination
among different sectors of the user community is important.

-- Because the group split will result in a huge amount of discussion,
which is inappropriate on comp.sys.powerpc, but would be appropriate
on comp.sys.be.

All these reasons have already been mentioned, by me *and* others,
several times.  Any one of them is compelling, and taken together I
think there is utterly no question whatsoever as to the proper path.
Let's put this issue to bed.

--
Martin Frankel			mdf@sgi.com
Silicon Graphics, Inc.		(415)933-6191