[cosmos-dev] RE: Design process

[Mark Mccraw <Mark.Mccraw@xxxxxxx>]

I think that the idea of a formal signoff procedure makes very good sense, but have a few questions regarding what constitutes a thumbs up or thumbs down for the design.  Is the signoff given by a team lead, or the community at large?  If the latter, is there a vote?  Can the developer specify the date of the vote during a regularly scheduled meeting, for example, or would the vote be conducted via email much like the approval for a new committer?  The latter suggestion is a bit complicated, because the developer would have to specify a deadline for voting, and there's no guarantee that anyone would vote (in which case I guess it would be accepted by default).

Any of these would be fine options by me, but I think it might be helpful to post specifically how signoff is achieved when we're describing the procedure.

Thanks,
Mark

-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Jason Losh
Sent: Friday, May 16, 2008 4:04 PM
To: 'Cosmos Dev'
Subject: [cosmos-dev] Design process

Hi team,

I took as an action from this morning's summit call to review the COSMOS dev process on design documents and offer feedback.

http://wiki.eclipse.org/COSMOS_dev_process#2.__Complete_Designs

I believe the information in this section could be beefed up a bit.  In particular, the nature of my questions regarding the SDD runtime design were surrounding whether there is a signoff procedure for designs.  The answer to my question was not clear from reviewing the section above.

I would like to suggest the following re-wording ...

"Assigned developer(s) should create designs and post them on the COSMOS wiki<http://wiki.eclipse.org/Category:COSMOS_Bugzilla_Designs> for Community review.  For complex designs, the assigned developer(s) or sub-project lead may request that the community review and formally signoff on the design."

I believe in many circumstances designs are straight forward enough to not warrant further review in the community.  We should not place undue burden on ourselves with formally reviewing all designs.  However, when designs are complicated and/or interface with other areas of the overall project I believe we should have a more formal signoff procedure that the assigned developer(s) or sub-project lead may request.

Thoughts?  I'll be glad to update the wiki.

Thanks,
-Jason

_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev