[kepler-dev] charter for architecture project

[Shawn Bowers]

A small follow-up:

[>> Feedback and
>> suggestions for major changes to the charter all are welcome; the
>> document is still in rapid flux.

> I agree with your comment that detailed UML diagrams should be an
> internal objective, at least for this particular project.

I meant to say here that I agree with your comment Tim that detailed
UML diagrams should *not* be an internal objective, at least for this
particular project/charter. These may or may not be needed at some
point later.

Shawn

> Similarly,
> while I think it is important to understand the current Kepler
> subsystems -- I think documentation of thie could be done at a high
> level, if needed, as opposed to via detailed UML diagrams.
>
> I am not sure I understand what kind of diagrams the following would be.
>
>  "Diagrams illustrating differences between current architecture and
> proposed new architecture."
>
> Thanks,
> Shawn
>
>>
>> Cheers,
>>
>> Tim
>>
>> On Jun 2, 2008, at 12:01 PM, Aaron Schultz wrote:
>>
>>>
>>> Hi Tim, go for it, it's all yours.
>>>
>>> Timothy McPhillips wrote:
>>>> Hi Aaron,
>>>>
>>>> I see you checked in a draft charter for the Kepler Architecture
>>>> project under kepler-docs/charters/drafts.  May I take the "lock"
>>>> on it (figuratively speaking) and add more detail?
>>>>
>>>> Thanks!
>>>>
>>>> Tim
>>>>
>>>
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>>
>