[evla-sw-discuss] code organization

[Bryan Butler]

On 10/26/06 15:37, Pete Whiteis wrote:
>    After being out yesterday, I'm still trying to figure out what 
> triggered this discussion.   I thought we had a discussion/meeting on 
> this a couple of years back and had commited to a plan.

well, we did, but i think the situation has changed enough that it is time to 
revisit it.

>    Basically, I don't have any attachment to a particular version 
> management tool.   What would cause me pain is 1) the current directory 
> structure changed.  This could potentially force me to change dozens of 
> Makefiles, as well as utility scripts    

well, the issue of whether it is a good idea to put hard paths into makefiles 
and scripts aside, how much work would it really be?  a day?  a week?  this is 
certainly an issue, i agree - we won't do this changeover for free - it will 
take some amount of work from everybody involved to get their code switched over 
(if we choose to do so).

> 2) Losing tag information would 
> be very bad.   I tag every release I've placed into production since 
> early 2004 and I've had to fall back on at least 2 occasions.

whatever we did, we would always retain the old cvs repository.  if we switched 
to subversion, there are two ways to handle this:
  1 - try to get all of the old versions from cvs into subversion
  2 - start fresh on the subversion (only copy over the most recent
      versions), but keep the old cvs repository around

>    We should take a hard look at quantifying the benefits of converting 
> to a new repository vs the effort  involved.  If a case can be made for 
> significant payback, then I'd be more agreeable.     I sure hope we have 
> a chance to meet about this before any hard action is taken.

of course.  i intend to make this the topic of the ECD meeting on nov 6.

	-bryan



> 
> -Pete-
> 
> Rich Moeser wrote:
> 
>> Bryan Butler wrote:
>>  
>>
>>> but i will enforce uniformity in those higher layers, however we 
>>> decide is the best way to do it.
>>>
>>> and we haven't really even touched on the higher level organization, 
>>> which, as i mentioned before, is more important in my opinion.  can 
>>> we get rid of the "e2e" that we have now?  what to do about 
>>> "commons"?  etc.
>>>  
>>>   
>> Currently the structure of the higher layers is as follows:
>>
>> NRAO (root directory)
>>            -> COMMONS (this contains reusable classes that can be used 
>> by any project and by non-nrao developers, AngleFormat, AstroDate, 
>> MathLib, and Util)
>>            -> EVLA
>>                           -> OBSERVE
>>                           -> TRANSITION
>>                           -> ARCHIVE
>>                           -> COMMONS (reusable components and static 
>> classes that only EVLA projects would use)
>>                           ....etc, etc, etc
>>            -> VLA
>>                           ->JOBSERVE
>>            -> VLBA
>>                            -> OMS
>>                           -> VLCj
>>            -> E2E (this would be SSS)
>>                            -> PST
>>                            -> VOSERVER
>>
>> I'm quite satisfied with this directory structure. It's simple, 
>> natural and difficult to get lost in. The root directory NRAO might 
>> seem a bit unnecessary but it allows for other roots such as VENDOR, 
>> DRAO, or whatever. I would probably change the COMMONS so that several 
>> types of commons projects can exist. For example the EVLA project 
>> could have COMMONS-UTIL (utility classes used exclusively by evla) and 
>> COMMONS-NET (evla communications and network classes). (And, yes, I 
>> think the term "commons" should be kept, indicating a collection of 
>> general purpose classes.)
>>
>> I think E2E should be replaced with SSS and remain a subdirectory of 
>> NRAO.
>>
>> --Rich
>>
>>
>>
>>
>>
>> _______________________________________________
>> evla-sw-discuss mailing list
>> evla-sw-discuss at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
>>
>>  
>>
> 
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss