🚀 go-pugleaf

I think this is all rather premature.

The BeBox and all other non-PowerMac PowerPC machines generate a tiny fraction
of the posts here.

I would suggest we take a step by step approach.

First there is obviously no chance of getting the MacHeads to move on, so
I would suggest we first go for a group like comp.sys.powerpc.nonmac.
Then when the volume in that gets out of hand we think about creating
comp.sys.be.

I for one can say that I am interested in every and any PowerPC based system
except the PowerMac.  The PowerMac is obviously a mature enough system to
justify its own news group(s), but it continues and will continue to dominate
the traffic here.

If we go straight to comp.sys.be, then I will still have to wade through all
the Mac dross to find everything other than Mac stuff here.

Alternatively, if there is sufficient justification for a Be based group,
then lets have comp.sys.be AND comp.sys.powerpc.nonmac.

I shall reiterate:

I want to read stuff about the PowerPC architecture.
I want to read stuff about the BeBox.
I want to read stuff about Prep based systems.
I want to read stuff about CHRP based systems
  (running anything other than MacOS)
I want to read about embedded PowerPC systems.
I do not want to read about the PowerMac.

I wouldn't mind if the PowerMac stuff was <10% of the total bandwidth in this
group but it isn't.

The PowerMac people will NOT move on, so I think everyone else should and
leave this group to the MacHeads.

I will vote against comp.sys.be.* until the Be traffic is generating more than
20% of the total number of posts here.

IMHO of course.

Regards,

Andrew Bray