Jimmy,
I think that it is
appropriate to discuss design issues that only affect the DC component on
these calls. The important thing is to avoid making fundamental
architectural decisions that have an impact on the broader COSMOS community
without their input.
Perhaps a good
compromise would be to discuss details in the DC meeting and follow up with a
brief discussion of a focused set of issues or recommendations in the
architecture meetings. This might help to avoid getting bogged down in a
lot of open-ended discussion in the architecture meetings.
Regards,
Don
The contents of this e-mail are intended
for the named addressee only. It contains information that may be confidential.
Unless you are the named addressee or an authorized designee, you may not copy
or use it, or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Mohsin, Jimmy
Sent: Tuesday, June 03, 2008 12:24 PM
To: Cosmos Dev
Subject: [cosmos-dev] Question of sub team meeting contents / format -
DataCollection
Mark / Don / et al…
For the first few DC meetings, we have discussed the gory
details of some of the DC ERs, in addition to DC status. It is not clear
if the “gory details of the DC ERs” belongs to the DC calls or the
Arch calls. That said, I would like to propose the following alteration
to the DC meeting format:
Increase the duration of the DC call to 45 minutes and
broken down as follows:
·
Initial 15 minutes: Overall DC status
·
Subsequent 30 minutes: DC ER and other low level DC issues…
Any dissenters to this proposal? If so, what is your counter
offer J ???
Thanks,
Jimmy Mohsin
Cell +1-609-635-1703