[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Wording in the bylaw changes

+1 I like it a lot!

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 

From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Thursday, March 10, 2011 5:49 PM
To: eclipse.org-architecture-council@xxxxxxxxxxx
Subject: [eclipse.org-architecture-council] Wording in the bylaw changes

 

Greetings sage wizards,

In our discussion today, we discussed keeping some aspects of architecture in the council responsibilities as defined in the bylaws.


Current:

The Eclipse Management Organization shall  establish an Architecture Council responsible for the development, articulation, and maintenance   of the Eclipse Platform Architecture (as defined in the then current Eclipse Development  Process).


Proposed:

The Eclipse Management Organization shall  establish an Architecture Council responsible for project mentoring, architectural monitoring, guidance, and influence. The Architecture Council is further responsible for defining and maintaining the Eclipse Development Process.

Some wordsmithing may be required. Your comments/input is required ASAP (EOD today would be best) as it is the intention of EMO(ED) to present this to the StAC (and the board) at EclipseCon.

Wayne