[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse.org-architecture-council] 10-Mar AC meeting notes
- From: Mik Kersten <mik@xxxxxxxxxxx>
- Date: Fri, 11 Mar 2011 11:03:04 -0800
- Delivered-to: email@example.com
- Thread-index: AQJCB4uU+O8kZ3ejLMR1IotdFc3IvgFjirngATjabE8DH/UxgJMOS/fg
Dr. Mik Kersten
Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
Assistant: zoe.jong@xxxxxxxxxxx, +1-778-588-6896, Skype: zoe.e.jong
> -----Original Message-----
> From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf
> Achim Loerke
> Sent: March-10-11 11:52 PM
> To: mike.milinkovich@xxxxxxxxxxx; eclipse.org-architecture-council
> Subject: Re: [eclipse.org-architecture-council] 10-Mar AC meeting notes
> Mike Milinkovich wrote:
> > When I went to paste the proposed revision into the Bylaws, I found it
> > a little ambiguous in places. Remember that the Bylaws need to be very
> > clearly worded and are modified very infrequently.
> > How does this work?
> > The Eclipse Management Organization shall establish an Architecture
> > Council responsible for: (i) project mentoring, (ii) monitoring of,
> > guidance on, and influence over the software architectures used by
> > Projects, and (iii) maintaining and revising the Eclipse Development
> > Process subject to the approval of the Board under Section 3.9(c).
> > The reference to Section 3.9(c) is necessary to reflect the fact the
> > Board has final approval of any revisions made to the EDP.