Difference between revisions of "Architecture Council/About the AC"

From Eclipsepedia

Jump to: navigation, search
(How does the AC work?)
(What does the AC?)
(4 intermediate revisions by one user not shown)
Line 2: Line 2:
 
* 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).
 
* 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).
 
* 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>."''
 
* 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>."''
 +
* The role of the AC has evolved since the original [http://www.eclipse.org/org/documents/Eclipse%20Development%20Process%202003_11_09%20FINAL_old.pdf 2003 Development Process] and the [[Development Process 2006 Revision Final]] to mostly focus on Mentorship.
  
= What does the AC? =
+
= What does the AC do? =
 
The EAC is responsible for the '''long-term technical health''' of the Eclipse platforms and frameworks. It involves itself in inter- and intra-project architecture and open source process through discussion during its '''meetings, mentoring and consultation'''. The AC 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.
 
The EAC is responsible for the '''long-term technical health''' of the Eclipse platforms and frameworks. It involves itself in inter- and intra-project architecture and open source process through discussion during its '''meetings, mentoring and consultation'''. The AC 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.
  
Line 16: Line 17:
 
* [http://www.eclipse.org/org/foundation/council.php#architecture The councils page] has the official members list (driven from EMO database)
 
* [http://www.eclipse.org/org/foundation/council.php#architecture The councils page] has the official members list (driven from EMO database)
 
* The [[Architecture Council/Members and Mentors|Members and Mentors]] page includes information about dormant members and proposed mentors of new projects
 
* The [[Architecture Council/Members and Mentors|Members and Mentors]] page includes information about dormant members and proposed mentors of new projects
 +
* [[Architecture Council/Dormant Status]] charter
  
 
= How does the AC work? =
 
= How does the AC work? =
Line 22: Line 24:
 
* [https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council AC Mailing List] for ideas and organisational messages ([http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/maillist.html Archives], [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/maillist.rss RSS Feed])
 
* [https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council AC Mailing List] for ideas and organisational messages ([http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/maillist.html Archives], [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/maillist.rss RSS Feed])
 
* Personal [[Architecture Council/Mentorship]] for guiding projects adopting the development process and being successful
 
* Personal [[Architecture Council/Mentorship]] for guiding projects adopting the development process and being successful
 +
 +
= What do AC members gain from their efforts? =
 +
* Being in touch with other leaders
 +
* First-hand information about interesting trends
 +
* Networking to re-use common efforts
 +
* Stronger Eclipse community == stronger own products on top of it
 +
* Strong base for influencing the future of Eclipse
 +
 +
The cost of this is that it does take some time. We typically talk about at least 4 hours each month for active members: 1 hour for the monthly phone call, 1 hour for organization and E-mail reading to keep up, 1 hour for working on incoming issues and bugs, and 1 hour for interacting with mentored projects.
  
 
= Any other questions? =
 
= Any other questions? =

Revision as of 16:27, 8 November 2012

Contents

What is the AC?

What does the AC do?

The EAC is responsible for the long-term technical health of the Eclipse platforms and frameworks. It involves itself in inter- and intra-project architecture and open source process through discussion during its meetings, mentoring and consultation. The AC 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.

From Darin Swanson's Blog about the AC: We all have varied reasons for being involved with Eclipse but we all share a common goal: the desire to see continued technological success and innovation occur at Eclipse fostered by a healthy and vibrant Committer community. The job of the Council is to look out beyond the current work and ensure that our processes and environment foster success rather than impede progress. Instead of just listing the problems (which is always the easiest path), we need to tackle head-on the issues that impact Eclipse, including but definitely not limited to release trains, UI consistency and project diversity. To be successful on our mission the council needs to react to the current and future successes and challenges to Eclipse and to keep informed of developments from the committers. As well, we are tasked to lead by example within our own projects and within the role of mentor.

The AC is a facilitator that helps projects to be successful.

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. Here is a recent presentation (PDF, 120K) about what the AC is and what it does in practice.

Who is on the AC?

How does the AC work?

What do AC members gain from their efforts?

  • Being in touch with other leaders
  • First-hand information about interesting trends
  • Networking to re-use common efforts
  • Stronger Eclipse community == stronger own products on top of it
  • Strong base for influencing the future of Eclipse

The cost of this is that it does take some time. We typically talk about at least 4 hours each month for active members: 1 hour for the monthly phone call, 1 hour for organization and E-mail reading to keep up, 1 hour for working on incoming issues and bugs, and 1 hour for interacting with mentored projects.

Any other questions?