Difference between revisions of "Architecture Council"

From Eclipsepedia

Jump to: navigation, search
Line 1: Line 1:
 
=Mission=
 
=Mission=
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/>
+
* 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>."''<br/>
+
* 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/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.
+
* 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>."''
  
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.
+
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. [http://www.eclipse.org/org/foundation/membersminutes/20081117EuropeanMembersMeeting/EAC_Update.pdf Here is a recent presentation (PDF, 120K)] about what the AC is and what it does in practice.
  
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.
+
=Membership=
 +
* [[Architecture Council/Membership]] Qualifications for members, and how to become a member
 +
* [http://www.eclipse.org/org/foundation/council.php#architecture The councils page] has the official members list
 +
* The [[Architecture Council/Members and Mentors|Members and Mentors]] includes information about dormant members and proposed mentors of new projects
  
 
=Discussions and Recommendations=
 
=Discussions and Recommendations=
Line 15: Line 18:
 
* [[Performance Bloopers]]
 
* [[Performance Bloopers]]
 
* [[Architecture Council/Links Collection|Links Collection]] to architecture-related interesting blog posts, articles and the like
 
* [[Architecture Council/Links Collection|Links Collection]] to architecture-related interesting blog posts, articles and the like
* 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]
+
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Community&component=Architecture+Council&cmdtype=doit Bugs on the AC 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]
<hr/>
+
==Getting Involved==
* '''Get involved!''' [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Architecture%20Council File a bug] for discussion on the EAC. ''We welcome your input!'' - See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00598.html this E-Mail].
+
* [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Architecture%20Council File a bug] for discussion on the EAC. ''We welcome your input!'' - See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00598.html this E-Mail].
<hr/>
+
==Open Issues==
 +
* [[Architecture Council/Open Issues]] lists overflow topics that have been brought up but not yet been discussed
  
 
=Call Schedule=
 
=Call Schedule=
Line 36: Line 40:
 
* <strike>Thursday, August 14</strike> -- [[Architecture Council/Minutes August 14 2008|Notes Aug 14]]
 
* <strike>Thursday, August 14</strike> -- [[Architecture Council/Minutes August 14 2008|Notes Aug 14]]
  
 +
==Archive==
 
* [[Architecture Council/Archive]] of previous meeting minutes
 
* [[Architecture Council/Archive]] of previous meeting minutes
 +
 
</td><td width="400">
 
</td><td width="400">
 
The calendar is available in the following formats:<br>
 
The calendar is available in the following formats:<br>
Line 43: Line 49:
 
<googlecalendar width="100%" height="400" title="EAC Conference Calls" mode="AGENDA">g30r6idsq3rsufe2j3t6k0l0g4%40group.calendar.google.com</googlecalendar>
 
<googlecalendar width="100%" height="400" title="EAC Conference Calls" mode="AGENDA">g30r6idsq3rsufe2j3t6k0l0g4%40group.calendar.google.com</googlecalendar>
 
</td></tr></table>
 
</td></tr></table>
 
== Some interesting Items to Discuss at the EAC Calls ==
 
* '''Ganymede build''' infrastructure - how to achieve continuous integration, unit tests covering the integration of all projects, and consistency across all projects
 
** Early integration tests, [http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg00808.html Automated JUnit API conformance tests]
 
* '''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 )
 
* '''Package visibility policies''': [[WTP_Policy_on_Package_Visibility|New WTP Policy]] and {{bug|202711}}
 
* [[Community Development for Eclipse Projects]]
 
  
 
=Resources (from the "old" EAC for now)=
 
=Resources (from the "old" EAC for now)=
Line 64: Line 58:
 
=Administrative=
 
=Administrative=
 
* [[Architecture Council/Bylaws]]
 
* [[Architecture Council/Bylaws]]
* [[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
 
* [[Architecture Council/Dormant Status]] charter
 
* [[Architecture Council/Archive]] of previous meeting minutes
 
* [[Architecture Council/Archive]] of previous meeting minutes

Revision as of 11:54, 16 December 2008

Contents

Mission

  • From the 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 Development Process: "... and ensuring the Principles of the Development Process through mentorship."
  • From the EAC charter: "responsible for the long-term technical health of the Eclipse platforms and frameworks (...) involves itself in inter- and intra-project architecture (...) and open source process (...) through discussion during its meetings, mentoring and consultation."

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

Membership

Discussions and Recommendations

Getting Involved

Open Issues

Call Schedule

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 MyFoundation Portal page).

Archive

The calendar is available in the following formats:
Ical.gifiCal,Xml.gifATOM News Feed,Html.gifHTML

Resources (from the "old" EAC for now)

Administrative