* Use the [http://www.doodle.com/dr57tu3fxcwm6s79 Doodle Attendance Tracking Poll] to confirm attendance or send regrets for this meeting. See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg00689.html this message] for how to use it. All [[Architecture Council/Members and Mentors|AC Members]] are invited.

* Use the [http://www.doodle.com/dr57tu3fxcwm6s79 Doodle Attendance Tracking Poll] to confirm attendance or send regrets for this meeting. See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg00689.html this message] for how to use it. All [[Architecture Council/Members and Mentors|AC Members]] are invited.

* '''Everyone''' please use [http://www.doodle.com/dr57tu3fxcwm6s79 Doodle Poll] to send regrets for next meeting if you cannot come

+

* [[Image:Ok_green.gif]] '''All PMC's''' to list mentor-less projects in their domain on the [[Architecture Council/Members and Mentors#Projects that need mentors]] page - superseded by using the Portal, will enable us to set up queries

* (''old'') All PMC's to list mentor-less projects in their domain on the [[Architecture Council/Members and Mentors#Projects that need mentors]] page: Wayne for Technology, McQ for Eclipse, Ed for Modeling, Tom for RT; WTP to add ATF to the page

* (''old'') '''Martin''' to start a Wiki page explaining what's good about having a mentor

* (''old'') '''Martin''' to start a Wiki page explaining what's good about having a mentor

=== Administrative ===

=== Administrative ===

−

* New Members: Linda Chan, Sven Efftinge (new Strategic Member)

+

* '''New Members''': Linda Chan, Sven Efftinge (new Strategic Member)

−

* New Dormant Members - see [[Architecture Council/Members and Mentors]]

** '''Just click on your red link''' to create a page -- it can't be simpler!

+

* New '''Dormant Members''' - see [[Architecture Council/Members and Mentors]]

−

** Bjorn (and some others) to become dormant?

+

* '''AC Admin via the [http://portal.eclipse.org Portal]'''

−

* Projects in need of Mentors

+

** '''AI All Mentors''' Enter Mentorship data on the [http://portal.eclipse.org Portal] - new AC component - will show up on the [http://www.eclipse.org/org/foundation/council.php#architecture councils page] as well as project homepages

−

** {{bug|256220}} Silverlight (SLDT), {{bug|256477}} STEM

+

** {{bug|256318}} - Need a page that lists projects and mentors for further processing (query for projects without mentors)

** Should we retire the [[Architecture Council/Members and Mentors]] page? - Not entirely, 'cause the "dormant" status cannot be tracked in foundation DB, and mentorship for proposed projects won't show up; don't want to do double bookkeeping in the long run, but for now please update both pages

** Wayne: Projects need to be interesting, so they should be able to attract a mentor...

−

* '''Enter Mentorship data''' on the [http://portal.eclipse.org Portal] - new AC component - will show up on the [http://www.eclipse.org/org/foundation/council.php#architecture councils page] as well as project homepages

+

** Martin: AC should be responsive, each of us should feel responsible for answering requests timely.

−

** Should we retire the [[Architecture Council/Members and Mentors]] page? - No, 'cause the "dormant" status cannot be tracked in foundation DB

+

** <font color="green">'''RESOLUTION'''</font> '''Wayne''' volunteers to be the be the initial contact (at least partly)

* AC Website Revamp needed to make the information that's already there more consumable

+

* Oisin says: by the time this call happens, I'll be a mentor on the Faceted Framework project, which is Konstantin's move from WTP. It's a little odd, because he has a lot more experience of working in Eclipse than I do :) Would it be useful in some cases to have a rider on the mentorship requirement for old hands starting with new projects? Maybe reduce the mentor count to one? Discuss.

+

** Martin thinks: In my understanding, the idea of mentorship is getting a "second pair of eyes" on some things, as well as to foster communications across PMC / Technology boundaries (by means of the AC). If Kosta is more experienced than yourself, this just means that he won't need you that much to answer questions, and you'll likely not have to monitor his efforts a lot. But it's good to have the cross-project exposure by means of the two-mentor-requirement.

+

** Ed: Reducing mentor count basically comes down to self-mentoring

+

** Mentors are not necessarily ahead in the domain... they should help with the Eclipse Development Process

+

** Workload: mentoring is not necessarily that much work (Ed), demand varies (Rich)

+

** <font color="green">'''RESOLUTION'''</font> we agree to keep the 2-mentor requirement

=== News from the EMO & Councils ===

=== News from the EMO & Councils ===

* Don: '''StAC meeting at Eclipse World''' -- outcome?

* Don: '''StAC meeting at Eclipse World''' -- outcome?

−

* {{bug|252015}} Here is something you should know, [[Architecture Council/Things Committers Should Know/Staging]] more authors needed?

** Doug Gaff: Board been happy with AC revival, less happy with technical items. Doug wants to work on an official response from the Board to the AC report

+

** Bjorn: It might take some time until minutes are posted, but as soon as they are, they now show up on the [http://www.eclipse.org/projects/whatsnew.php Projects What's New] page and [http://www.eclipse.org/projects/dev-process-changes-atom.php RSS Feed]

+

** Doug also going to blog the Board meeting

−

=== Recent Discussions ===

+

=== New Topics ===

−

* '''Tom:''' What can be done to streamline project proposals even more ... we could provide Tooling for it. I started writing a little RCP-Application which defines an Ecore-Model of required information and provides a UI to enter the data and produce the Review Document

+

* '''Tom S: Project Proposals''' - What can be done to streamline project proposals even more ... we could provide Tooling for it. I started writing a little RCP-Application which defines an Ecore-Model of required information and provides a UI to enter the data and produce the Review Document

*** Dave Carver: Here are some examples of project proposals done using the wiki: [[EMF4Net Proposal]], [[XML_Security_Tools_Proposal]], [[WTP/XQuery/Proposal]], and [http://www.mediawiki.org/wiki/Help:Templates information on creating templates]. The other thing to consider is standardizing the source format used for proposals. I know most people use Word, but would prefer a standard like ODT, or [http://www.docbook.org/ DocBook] for the final version.

−

** {{bug|256660}} What are best practices to keep bugzilla alive and users interested, without taking away too much time from committers?

** General recommendations: (e.g. avoid synchronous callbacks, avoid in Activator.start(), static initializers or Singleton getters) - a general recommendation could be to avoid performing work at unpredictable times, but that would recommend against lazy initialization in general

+

*** Analyze the MANIFEST.MF dependencies in each project's repository HEAD, generate a dependency graph out of it and use some graph layout / clustering algorithm (could we allow interactive zooming into clusters?)

−

** Does anybody have a well-working, consistent model on top of the current infrastructure?

+

*** Define some keywords, and ask each project use the Portal to pick keywords that are relevant for their project. Based on keyword association, have some graph auto-generated (clustered by keywords).

** '''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}} (Example: http://wiki.eclipse.org/images/8/86/Mylyn-Bug-Reporting-Example.jpg ). Do we want this for Galileo?

Should we retire the Architecture Council/Members and Mentors page? - Not entirely, 'cause the "dormant" status cannot be tracked in foundation DB, and mentorship for proposed projects won't show up; don't want to do double bookkeeping in the long run, but for now please update both pages

Oisin says: by the time this call happens, I'll be a mentor on the Faceted Framework project, which is Konstantin's move from WTP. It's a little odd, because he has a lot more experience of working in Eclipse than I do :) Would it be useful in some cases to have a rider on the mentorship requirement for old hands starting with new projects? Maybe reduce the mentor count to one? Discuss.

Martin thinks: In my understanding, the idea of mentorship is getting a "second pair of eyes" on some things, as well as to foster communications across PMC / Technology boundaries (by means of the AC). If Kosta is more experienced than yourself, this just means that he won't need you that much to answer questions, and you'll likely not have to monitor his efforts a lot. But it's good to have the cross-project exposure by means of the two-mentor-requirement.

Ed: Reducing mentor count basically comes down to self-mentoring

Mentors are not necessarily ahead in the domain... they should help with the Eclipse Development Process

Workload: mentoring is not necessarily that much work (Ed), demand varies (Rich)

Doug Gaff: Board been happy with AC revival, less happy with technical items. Doug wants to work on an official response from the Board to the AC report

Bjorn: It might take some time until minutes are posted, but as soon as they are, they now show up on the Projects What's New page and RSS Feed

Doug also going to blog the Board meeting

New Topics

Tom S: Project Proposals - What can be done to streamline project proposals even more ... we could provide Tooling for it. I started writing a little RCP-Application which defines an Ecore-Model of required information and provides a UI to enter the data and produce the Review Document

Bjorn: Current philosophy is that it's fine to propose multiple projects -- encourage people to work together, but don't enforce it. When a project matures, there should be only.

AI Martin follow up with Brett Porter and the m2eclipse / iam projects

Martin: Architecture Diagrams -

Eclipse is growing rapidly, and it's getting ever harder to understand what projects are available, how they are interrelated and where there is duplication.

It was the original AC charter to create an architecture plan

Can we auto-generate an architecture diagram? - Some ideas:

Scan the project's web pages and CVS Repository and build a semantic web

Analyze the MANIFEST.MF dependencies in each project's repository HEAD, generate a dependency graph out of it and use some graph layout / clustering algorithm (could we allow interactive zooming into clusters?)

Define some keywords, and ask each project use the Portal to pick keywords that are relevant for their project. Based on keyword association, have some graph auto-generated (clustered by keywords).