* Kim: I contributed a chapter on Eclipse to the upcoming [http://third-bit.com/blog/archives/3847.html Architecture of Open Source applications] book. The book is in the final stages of editing, and the editor, Greg Wilson, is looking for people to review the beta of the book, and provide feedback and quotes. The book has 24 chapters and each chapter focuses on the architecture of an application produced by different open source project - for instance, Apache Hadoop, Drupal, NoSQL etc. If you are interested in reviewing the beta, let me know and I can send you the information.

+

==== Upcoming Change of Bylaws ====

−

==== Bylaws and EDP Changes ====

+

* Wayne: Proposes getting rid of the "AC responsible for the development, articulation, and maintenance of the Eclipse Platform Architecture"

−

* EMO is proposing changes to the Bylaws and EDP that affect the Architecture Council

+

** Propose adding AC responsible for the EDP (with Wayne being responsible for creating the document)

−

** Remove the part (section 7.2) that makes the AC "responsible for the development, articulation, and maintenance of the Eclipse Platform Architecture" (it's been years since we've even attempted to do this, anyway)

** '''RESOLUTION: AI Wayne''' draft a statement along this lines and bring before Mike

+

+

==== OSS Architecture Book Beta ====

+

+

* Kim: I contributed a chapter on Eclipse to the upcoming [http://third-bit.com/blog/archives/3847.html Architecture of Open Source applications] book. The book is in the final stages of editing, and the editor, Greg Wilson, is looking for people to review the beta of the book, and provide feedback and quotes. The book has 24 chapters and each chapter focuses on the architecture of an application produced by different open source project - for instance, Apache Hadoop, Drupal, NoSQL etc. If you are interested in reviewing the beta, let me know and I can send you the information.

Dave C: Expand the role from "Eclipse Platform" to applying to "Eclipse as a Whole"?

Wayne: AC doesn't have any teeth to impose architectural direction on any of the projects ... people come for advice ... it's poll, not push

AC is becoming increasingly mis-named... we are Mentors, help projects with good advice, drive important technical cross-cutting efforts...

Martin: Bylaws shouldn't just reflect reality but describe the direction and expected state of the system.

Do we acknowledge that in any truly Open system there is no Architecture anyways? Are we going to release Eclipse into chaos?

DougS: Each project controls their own domain

Wayne: AC has influence but no power

Council Charter should reflect reality, it's frustrating to have a statement that can never happen ... maybe rename into "Eclipse Advisory Council" ?

Pascal: Be honest to ourselves, nothing has ever happened in many years - Mentoring is the only realistic

DougS: Had some false hope about good technical discussions, eg good discussion about e4

Wayne: Recent bug about security policy

Martin: Influence is directly related

Wayne: Want to bring a proposal for changing the responsibility to Mike

Project Mentoring; Architectural Monitoring, Guidance and Influence

RESOLUTION: AI Wayne draft a statement along this lines and bring before Mike

OSS Architecture Book Beta

Kim: I contributed a chapter on Eclipse to the upcoming Architecture of Open Source applications book. The book is in the final stages of editing, and the editor, Greg Wilson, is looking for people to review the beta of the book, and provide feedback and quotes. The book has 24 chapters and each chapter focuses on the architecture of an application produced by different open source project - for instance, Apache Hadoop, Drupal, NoSQL etc. If you are interested in reviewing the beta, let me know and I can send you the information.