From: bkottmann@falcon.aamrl.wpafb.af.mil (Brett Kottmann)
Newsgroups: misc.jobs.misc
Subject: Re: Geographic split: proto-formation of RFD
Summary: Some clarifications....
Date: 2 Oct 92 18:45:56 GMT
Followup-To: misc.jobs.misc
Organization: Logicon Technical Services, Inc.

In article <BILLD.92Oct1122025@gdstech.GRUMMAN.COM>, billd@gdstech.GRUMMAN.COM (Bill D'Camp) writes:
> 
> Personally, I'm opposed to geographic splits for the following
> reasons:
> 	Given the current economy access to all geographic areas is
> pretty important.
> 
> 	How can we be sure all of the geographic groups will reach us?
> I'm concerned that distribution of the geographic groups will be
> limited to the corresponding region.  My news site is in New York, I
> live in San Diego, if the distribution is limited I won't see anything
> except usa.east.  I'm also interested in getting a job out of the
> country, what will be the distribution for groups outside the US?

	This is precisely what I hope to "fix" with the split.  As people have
noted, there are already ba.jobs, ne.jobs, etc.  But all suffer from regional
propagation.
	Misc.jobs.offered.x will all be network groups with (suggested) world
propagation.  They (hopefully :) will be created so that people can find jobs
*located in those areas*, and not just so people already in those areas can 
find jobs. 

> I had not previously responded to this thread because I didn't realize
> that there was a real possibility of it happening.  By the way, I have
> no way to influence my news administrator about the groups subscribed
> to, so that is not an option.

	A lot of admins take a passive approach.  If the group passes the vote
and is newgrouped by Dave Lawrence, they carry it.  (Which is why ne.* and ba.*
remain regional: there is not network-wide method of voting on them.)

	As a side note, I don't expect traffic, as in noise traffic, to grow. 
The splits of rec.arts.sf.* and rec.games.frp.* resulted in a much higher
signal to noise ratio.  More groups with less traffic (but better defined) are
just as easy to read as one big group with a kill file.

	Someone mentioned that misc.jobs.offered would either have to be
renamed or removed.  Since I don't think of this as a "renaming", I'd rather
see misc.jobs.offered retired as a message-carrying newsgroup.  It would then
exist as part of the hierarchy.  (a la misc.jobs)

	Spotty group creation:

		There is a chance we'd end up with *.usa.east and
*.europe.southern and nothing else, but voting on other splits seems to
indicate that intelligently named splits succede.  The main thing to avoid is
"group creation overkill" where too many groups cause a backlash.  That's why
I'm recommending as simple a split as possible.

	Amazingly, I've gotten (sometimes nasty :) email saying that group
split notices should have followups to misc.jobs.misc (as opposed to
misc.jobs.offered).  Which they already do.  If your site doesn't, then
something is broken between here and there.  And yes, notices have to be posted
to *.offered and *.resume, how else are potential readers supposed to know what
is going on?
	And yes, only the debate in news.groups "counts" as far as the CFV is
concerned.  But if we don't go into news.groups with some concrete proposals,
we'll get bogged down in useless (and endless) debate.

	So please, let's stick to the issues!  I've done this before and don't
intend on messing up the split by not following proper procedures!!

Brett--------------------------------------------------------------------------
	"Why the courts don't tell a husband who has been living off his wife
to go out and get a job is beyond my comprehension."--Joan Lunden
-------------------------------------------------------------------------------