Jump to: navigation, search

Architecture Council

Revision as of 12:47, 8 May 2008 by Doug.gaff.windriver.com (Talk | contribs) (Meeting Minutes)

Mission

From [1] "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."
From [2] "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.

The membership of the Architecture Council is listed on the councils page of the main website, which also has an index to the meeting minutes of the "old" EAC.

Call Schedule

As of January 2008, the plan is to have a call 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. (For the call-in numbers, please see the MyFoundation Portal page.)

Calls currently on the calendar:

  • Thursday, December 13 -- Cancelled
  • Thursday, January 3 -- Added due to December cancellation
  • Thursday, January 17
  • Thursday, February 14
  • Thursday, March 13
  • Thursday, April 10
  • Thursday, May 8
  • Thursday, June 12
  • Thursday, July 10
  • Thursday, August 14
  • Thursday, September 11
  • Thursday, October 9
  • Thursday, November 13
  • Thursday, December 11

Agenda For Next Call

  • Ganymede build infrastructure - how to achieve continuous integration, unit tests covering the integration of all projects, and consistency across all projects
  • 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 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: New WTP Policy and bug 202711

Meeting Minutes

Resources (from the "old" EAC for now)