[Xastir] Refactored/rewritten/split xastir

[Gerry Creager N5JXS]

Realistically, I'd recommend the new project.  It's going to take some 
time to see a workable Xaster-TNG (Gene Roddenberry is rolling in his 
grave, no doubt), so there will be some maintenance on Xastir as we know 
it.  If a new developer corps arises, that's great.

A lot of discussion goes into project forks in the Open Source world. 
This isn't a project fork, in my mind, but an orderly progression and 
evolution.

gerry

Curt Mills wrote:
> On Sun, 2 Jan 2005, Tom Russo wrote:
> 
> 
>>Honestly, the things being discussed in this thread would warrant an entirely
>>separate repository, IMNSHO.
> 
> 
> That's probably the best way to go of all, regarding CVS that is.
> Either a new SourceForge project, or a new root module on the CVS
> tree for the new development.  It kind of depends on whether someone
> will want to continue the Xastir monolithic development after we go
> the split-code route, or whether everyone will let it die in peace.
> 
> If a possibility of further development, new project is in order.
> If not, we could remain with the current SourceForge project, but
> we'd have to do a bit of work to the RFE and Bug lists to separate
> out which are for which project.
> 

-- 
Gerry Creager -- gerry.creager at tamu.edu
Texas Mesonet -- AATLT, Texas A&M University	
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578
Page: 979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843