[Tinyos-alliance] Steering com input

[Ramesh Govindan]

> -------- Original Message --------
> Subject: 	Re: [Tinyos-alliance] Bridge for today's telecon
> Date: 	Sun, 02 Apr 2006 23:41:45 -0700
> From: 	Philip Levis <pal at cs.stanford.edu>
> To: 	David E. Culler <culler at eecs.berkeley.edu>
> References: 	<44295DE5.2010408 at eecs.berkeley.edu> 
> <44296C6C.8 at eecs.berkeley.edu>
> 
> 
> 
> Here's my stab at an adjusted text:

Phil, David,

I missed the meeting where this was discussed. I had just one comment on 
the text below.


> The Steering Committee is also responsible for approval of significant
> architectural steps that are likely to impact the Alliance broadly.

Is there any reason to limit Steering Comm oversight only to 
architectural/BCP TEPs? Initially, at least, I thought it might make 
sense, as a form of peer review, to have *all* TEPs (not drafts, but 
those formally submitted by a WG) be reviewed by the SC. If this becomes 
onerous, we can revisit the decision then?

Also, I don't know if we need to mention this here or not, but it might 
also make sense to require that TEPs that specify changes to the 
organizational structure must be ratified by the Board (in addition to 
the SC).

Regards.

> Initially, this will include BCP TEPs. As the Alliance and set of
> working groups changes, they may include core Documentary TEPs, or
> a TEPs that specify important facets of interoperability. The goal
> of having a second level of review and structure is to provide
> high-level guidance from a broader perspective. Unlike a specific
> working group, which may have a set of members with very narrow
> interests, the Steering Committee represents a broad set of perspectives
> and interests. The expectation is that only a small portion of
> TEPs would fall into this category. As the  Alliance grows, there
> may or may not need be to an additional Architecture Board that
> charts architectural directions, but if so, this would be structure
> that comes out of growth and need.
> 
> Finally, the Steering Commitee will be responsible for determining the
> procedural elements of the Alliance. This includes election procedures,
> membership criteria, selection of venues, oversight of access to code
> repositories and Alliance web sites, and regular Alliance meetings.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Tinyos-alliance mailing list
> Tinyos-alliance at millennium.berkeley.edu
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-alliance

-- 
Ramesh
http://cs.usc.edu/~ramesh/