Mathias Bauer <[EMAIL PROTECTED]> writes: > step1 - idea: mandatory ;-) > step2 - create iTeam: optional at this point in time as we can't expect > it for all community work > step3 - design/review/implementation cycles: indispensable :-) > step4 - create iTeam if not done in step2: possible to be done by > project lead; now mandatory as needed for the next steps > step5 - finalize documentation aka "spec" to the necessary degree as > negotiated inside the iTeam; possibly with help from iTeam or Project Lead > step6 - QA, maybe fixing bugs, documentation: how could we do without? ;-) > > Does that make sense? > Hi Mathias,
yes, absolutely makes sense. One remark to step4: this is probably our (established devs/Suns) duty, if a patch or CWS comes in from external, to setup the iTeam. Default role to handle this: project leads. Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
