Received: from ATHENA-AS-WELL.MIT.EDU by po6.MIT.EDU (5.61/4.7) id AA04336; Wed, 19 Jan 94 21:04:16 EST
Received: from BLOOM-BEACON.MIT.EDU by MIT.EDU with SMTP
	id AA29360; Wed, 19 Jan 94 21:04:10 EST
Received:  by bloom-beacon.mit.edu (5.61/25-eef)
	id AA04724; Wed, 19 Jan 94 21:03:21 EST
Received: from world.std.com by bloom-beacon.mit.edu with SMTP (5.61/25-eef)
	id AA04700; Wed, 19 Jan 94 21:03:15 EST
Received: by world.std.com (5.65c/Spike-2.0)
	id AA09077; Wed, 19 Jan 1994 21:03:12 -0500
Date: Wed, 19 Jan 1994 21:03:11 -0500 (EST)
From: Jana Asher Groff <Emilia@world.std.com>
Subject: principality issue...
To: carolingia@world.std.com
Message-Id: <Pine.3.89.9401192005.A21588-0100000@world.std.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


(Delete now if not interested.)

Since a couple of people have mentioned Pikestaff in connection with this 
issue, I feel the need to throw my two cents in.

1)  The creation of a Prinicality does not diminish the work involved with 
Pikestaff.  

2)  Splitting the Kingdom would decrease the size of Pikestaff.  
It would decrease the subscription base.  It would decrease the work 
involved in putting out the Pikestaff somewhat.  I imagine, but don't 
really know, that the general work level of each Kingdom officer would 
diminish.

3)  Personally, I'm happy with my job as it exists.  I agree with Kathryn 
on her reasons for a Principality.  I don't want Carolingia in it.

Dana and I DON'T have the same opinion.  C'est la vie.  But then again, 
he lives in Carolingia and I live in Stonemarche.

Jana/Emilia