From the [[Architecture Council/Bylaws|Eclipse Bylaws]] section 7.2: ''"responsible for the development, articulation, and maintenance of the Eclipse Platform Architecture"'' (as defined in the then current Eclipse Development Process)<br/>

+

The Eclipse Architecture Council (EAC) serves the Community by identifying and tackling any issues that hinder Eclipse's '''continued technological success and innovation, widespread adoption, and future growth'''. This involves technical architecture as well as open source processes and social aspects. Comprising the finest technical leaders from all community stakeholders, it is the council's goal to keep the '''projects''' successful and healthy, the '''processes''' simple and smooth, and the '''communities''' vibrant and cohesive because this will benefit us all. '''[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Architecture%20Council Approach us]''' to ask for personal '''Mentorship for your project''', to raise important issues, to suggest improvements, or just to ask questions. <b><i>We welcome your input!</i></b>

−

From the [http://www.eclipse.org/projects/dev_process/development_process.php#4_8_Councils Development Process]: ''"... and ensuring the Principles of the Development Process <b>through mentorship</b>."''<br/>

+

−

From the [http://www.eclipse.org/projects/dev_process/architecture-council.php EAC charter]: ''"responsible for the long-term technical health of the Eclipse platforms and frameworks (...) involves itself in inter- and intra-project architecture (...) <b>and open source process</b> (...) <b>through discussion during its meetings, mentoring and consultation</b>."'', so the EAC is involved in both technical and process aspects because the social and process structure of a project has been shown to have a direct impact on the technical quality of its extensible frameworks and exemplary tools. See also [http://runnerwhocodes.blogspot.com/2008/01/introducing-eclipse-architecture.html Darin Swanson's Blog] about the EAC.

+

−

This role for the Architecture Council represents a new (revitalized?) role for the Architecture Council and thus there is not a lot of history to build on. The Council will be as effective and useful as we make it.

+

* [[Architecture Council/About the AC]] and a recent [http://www.eclipse.org/org/foundation/membersminutes/20081117EuropeanMembersMeeting/EAC_Update.pdf presentation (PDF, 120K)] with details about what the AC is and does in practice.

* [[Architecture Council/Open Issues]] lists overflow topics that have been brought up but not yet been discussed

−

The membership of the Architecture Council is listed on [http://www.eclipse.org/org/foundation/council.php#architecture the councils page] of the main website, which also has an index to the meeting minutes of the "old" EAC. Mentoring assignments as well as links to member Bio's can be found on the [[Architecture Council/Members and Mentors|Members and Mentors]] page.

+

=Getting in Touch=

+

* [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Architecture%20Council File a bug] for discussion on the EAC, or requesting a mentor. ''We welcome your input!'' - See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00598.html this E-Mail], which was sent to the eclipse.org-committers list in September 2008.

* Bugs on the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Community&component=Architecture+Council&cmdtype=doit Architecture Council component], or [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&emailcc1=1&emailtype1=exact&email1=eclipse.org-architecture-council%40eclipse.org&cmdtype=doit CC'd to the EAC]

EAC conference calls are every month on the second Thursday at 8am Pacific, 11am Eastern, 5pm European time. A reminder email will be sent to the list in advance of the calls. The '''call-in number''' is on each Agenda page (usually the standard Eclipse Foundation Conference Bridge for Project Reviews, as per the [https://dev.eclipse.org/portal/myfoundation/portal/portal.php MyFoundation Portal] page).

* '''UI Consistency''' - when I'm not mistaken, the UI Guidelines are being reworked; how can we encourage projects to pick them up.

+

−

* '''Remote Development''' - Theoretically, EFS should be the foundation on which workspaces can be put on remote machines, and I do see a lot of interest in this -- but practically, there are some roadblocks. It's a pervasive topic since most projects are not really EFS-aware yet. How to improve the situation?

+

−

* '''Scripting, Macro Recording, DOMs''' - Another pervasive theme, if macro recording & playback is to be supported across an entire Eclipse based product, there need to be guidelines and APIs for projects to follow. It may be a multi-year multi-project effort but it may be worth getting it started.

+

−

* '''Security''' - With the number of plugins aver growing, is there a threat of trojans nesting themselves inside Eclipse? Getting a trojan or virus-like plugin into Eclipse can be extremely malicious - from spying to impersonation up to data destruction. Is it a real threat, and is there something that could / should be done?

+

−

* '''Project Model and Nested Projects''' - when developers lay out the directory structure on non-eclipse projects, they often use a tree where some directories represent projects. Those projects are "nested". This is also often related to the way the files are stored in a configuration management system. Unfortunately eclipse does not really support this real-world setup {{Bug|35973}}, and this [http://www.eclipsezone.com/eclipse/forums/t99991.rhtml Blog by Alex Blewitt]

+

−

* '''Integrated bug reporting''': Mylyn is providing a bug/error/enhancement reporting facility that will provide a flexible and product-configurable mapping between features, bundles and bug trackers {{bug|212209}}. Once done it would be good to discuss how best for EPP and other products to consume this (Example: http://wiki.eclipse.org/images/8/86/Mylyn-Bug-Reporting-Example.jpg )

* [[Architecture Council/Membership]] Qualifications for members, and how to become a member

* [[Architecture Council/Templates]] for E-Mail communications

* [[Architecture Council/Templates]] for E-Mail communications

−

* [[Architecture Council/Dormant Status]] charter

+

+

[[Category:Architecture Council]]

Revision as of 01:26, 2 March 2013

Three arches supporting the Eclipse Community. Click image for full description.

Mission

The Eclipse Architecture Council (EAC) serves the Community by identifying and tackling any issues that hinder Eclipse's continued technological success and innovation, widespread adoption, and future growth. This involves technical architecture as well as open source processes and social aspects. Comprising the finest technical leaders from all community stakeholders, it is the council's goal to keep the projects successful and healthy, the processes simple and smooth, and the communities vibrant and cohesive because this will benefit us all. Approach us to ask for personal Mentorship for your project, to raise important issues, to suggest improvements, or just to ask questions. We welcome your input!