Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Architecture Council"

(New page: =Mission= From [http://www.eclipse.org/projects/dev_process/development_process.php#4_5_Councils] "The Architecture Council is responsible for the development, articulation, and maintenanc...)
 
(105 intermediate revisions by 13 users not shown)
Line 1: Line 1:
 +
__NOTOC__
 +
[[Image:BSB Ponte JK Panorama 05_2007 266.jpg|thumb|right|250px|Three arches supporting the Eclipse Community. Click image for full description.]]
 
=Mission=
 
=Mission=
−
From [http://www.eclipse.org/projects/dev_process/development_process.php#4_5_Councils] "The Architecture Council is responsible for the development, articulation, and maintenance of the Eclipse Platform Architecture and ensuring the Principles of the Development Process through mentorship." <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 [http://www.eclipse.org/projects/dev_process/architecture-council.php] "The Architecture Council is involved in both technical and process aspects of the projects in its quest to ensure the long-term technical health of the Eclipse platforms 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."
+
  
−
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/Members and Mentors]]
 +
* [[Architecture Council/Mentorship]]
 +
* [[Architecture Council/Ask the AC|Architecture Council/FAQ]]
 +
* [http://wiki.eclipse.org/Category:Architecture_Council EAC Category Sitemap]
 +
* [[Architecture Council/Meetings]] and minutes of previous meetings
 +
* [[Architecture Council/Open Issues]] lists overflow topics that have been brought up but not yet been discussed
  
−
=Call Schedule=
+
=Getting in Touch=
−
Generally every month on second Thursday at 8am Pacific, 11am Eastern, 5pm European time. A reminder email will be sent to the list in advance of the calls.
+
* [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.
 +
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Community&component=Architecture+Council&resolution=---&cmdtype=doit Open bugs: AC Component] ([https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Community&component=Architecture+Council&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&cmdtype=doit closed])
 +
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&emailcc1=1&emailtype1=exact&email1=eclipse.org-architecture-council%40eclipse.org&resolution=---&cmdtype=doit Open bugs: CC'd to the EAC] ([https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&emailcc1=1&emailtype1=exact&email1=eclipse.org-architecture-council%40eclipse.org&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&cmdtype=doit closed])
  
−
==Agenda For Next Call==
+
=Resources and Recommendations=
−
* Ganymede build infrastructure - how to achieve continuous integration, unit tests covering the integration of all projects, and consistency across all projects
+
* [[Architecture Council/Top Ten Recommendations|Top Ten Recommendations]] for Architecture (work in progress)
−
* UI Consistency - when I'm not mistaken, the UI Guidelines are being reworked; how can we encourage projects to pick them up.
+
* [[Architecture Council/Top Ten Project Development Practices|Top Ten Process Practices]] (work in progress)
−
* 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?
+
* [[Architecture Council/Metadata File Naming Recommendations|Metadata File Naming Recommendations]]
−
* Scripting & Macro Recording - 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.
+
* [[Architecture Council/Bugzilla Best Practices|Bugzilla Best Practices]]
−
* 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?
+
* [[Architecture Council/Things Committers Should Know | Things Committers Should Know]]
 +
* [[Development Resources]], top advice for everyone including [[Community Development for Eclipse Projects]]
 +
* [[Performance Bloopers]]
 +
* [[Architecture Council/Links Collection|Links Collection]] to architecture-related interesting blog posts, articles and the like
 +
* [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/ Architecture Council mailing list]
 +
* (''old [[Eclipse (EMO) Architecture Council Index]]'')
 +
* [http://www.programcreek.com/eclipse-architecture-design/ Eclipse Architecture]
 +
 
 +
=Administrative=
 +
* [[Architecture Council/Templates]] for E-Mail communications
 +
 
 +
[[Category:Architecture Council]]

Revision as of 02: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!

Getting in Touch

Resources and Recommendations

Administrative

Retrieved from "https://wiki.eclipse.org/index.php?title=Architecture_Council&oldid=330088"

Back to the top