Jump to: navigation, search

Difference between revisions of "Architecture Council"

(Resources and Recommendations)
(Resources and Recommendations)
Line 19: Line 19:
 
* [[Architecture Council/Top Ten Recommendations|Top Ten Recommendations]] for Architecture (work in progress)
 
* [[Architecture Council/Top Ten Recommendations|Top Ten Recommendations]] for Architecture (work in progress)
 
* [[Architecture Council/Top Ten Project Development Practices|Top Ten Process Practices]] (work in progress)
 
* [[Architecture Council/Top Ten Project Development Practices|Top Ten Process Practices]] (work in progress)
 +
* [[Architecture Council/Metadata File Naming Recommendations|Metadata File Naming Recommendations]]
 
* [[Architecture Council/Bugzilla Best Practices|Bugzilla Best Practices]]
 
* [[Architecture Council/Bugzilla Best Practices|Bugzilla Best Practices]]
 
* [[Architecture Council/Things Committers Should Know | Things Committers Should Know]]
 
* [[Architecture Council/Things Committers Should Know | Things Committers Should Know]]

Revision as of 16:11, 13 May 2011

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