[kepler-dev] Re: [SDM-SPA] RFC new directory structure

[Terence Critchlow]

Hi Chad,

It is a requirement that we (SPA) are able to create a release for the work 
done under the funding we receive. Simply participating in the 
collaboration is not sufficient. And pointing to the Kepler release and 
indicating we contributed to it is also not sufficient. I would expect the 
Kepler release to include this code as well, and I see that as one of the 
major advantages of sharing the CVS repository. From my perspective, the 
goal of participating in the collaboration is to efficiently leverage 
expertise and code across projects - it is not to loose the project identity.

Terence

At 08:59 AM 3/18/2004 -0800, Chad Berkley wrote:
>I don't really like the idea of chopping kepler up into smaller pieces for 
>releases.  I can see doing this if there is some gigantic jar file that's 
>used for only one pipeline or something like that, but in general, I would 
>like to see Kepler packaged and distributed as one product.  I think we 
>run the risk of having a "seek kepler" and a "spa kepler" and a whatever 
>else kepler which is exactly what we were trying to avoid with the 
>collaboration in the first place.  So unless there is a really good reason 
>for doing so, I would like to propose there there only b e one version of 
>kepler per release and that it includes everyones contributions whether 
>they are relevant to everyone who might use kepler or not.
>
>chad
>
>
>>>
>>>Regarding jar files in lib/, yes you're right, we didn't discuss
>>>dividing that up by subproject.  Do you see a need to?
>>We may want to since not all projects may want to have all lib code on 
>>all occasions.
>>Specail