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.
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Boris Bokowski
Sent: March-10-11 2:46 PM
Subject: Re: [eclipse.org-architecture-council] 10-Mar AC meeting notes
My apologies for not joining the call today, I had written a note about having a conflict but forgot to hit the Send button.
I think the proposed change to the bylaws is a good one, especially after the tweaks you discussed on the call today.
"Oberhuber, Martin" ---2011/03/10 13:25:18---Hi all, Notes of today's meeting are now online:
"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
[eclipse.org-architecture-council] 10-Mar AC meeting notes
Notes of today’s meeting are now online:
Remember to ask Kim for the “OSS Architectures” book beta if you are interested.
Please vote for the wording change of the Bylaws as asked by Wayne – it’s important.
Hope to see many of you at EclipseCon.
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
eclipse.org-architecture-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.