Hi Mathias,
Sorry - didn't notice your summary before posting mine. OTOH - yours
looks rather better than mine, thanks so much for taking the time here.
OTOH - I make some more concrete proposals, so perhaps there is some
value in discussing both in the same thread.
It really helps me to keep at least one of thread-ids or subjects
constant wrt. tracking the discussion.
> Is that a basis for further considerations? Did I miss
> something important?
Nope, seems a good summary; one of the ideas I came up with was of
splitting the work-flow aspects [ step1: create iTeam, step2: design,
step 3: review, step 4: implement ] etc. from the other pieces that are
necessary for QA / docs / i18n etc. ie. providing separate guidelines
for how teams can function, and develop software vs. what information /
approvals are necessary to get changes included in the product.
Anyhow - thanks again,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
