Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Architecture Council/Minutes December 16 2008"

m (Attendees)
Line 30: Line 30:
 
| '''Modeling:'''
 
| '''Modeling:'''
 
| Richard Gronback
 
| Richard Gronback
|  
+
| Ed Merks
 
|-
 
|-
 
| '''RT:'''
 
| '''RT:'''
Line 57: Line 57:
 
|}
 
|}
 
* 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.
** '''Signed-up:''' Chris Aniszczyk, Martin Oberhuber, Tom Schindl, Darin Swanson, Tom Watson, Gary Xue
+
** '''Signed-up:''' Chris Aniszczyk, Bjorn Freeman-Benson, Martin Oberhuber, Tom Schindl, Darin Swanson, Mark Vandenbrink, Tom Watson, Gary Xue
** '''Regrets:''' Boris Bokowski, Adrian Colyer, Sven Efftinge, Neil Hauge, Oisin Hurley, Georg Schmidt, Karsten Schmidt, Gunnar Wagenknecht, David Williams, Darin Wright
+
** '''Regrets:''' Boris Bokowski, David Carver, Adrian Colyer, Sven Efftinge, Richard Gronback, Neil Hauge, Oisin Hurley, Georg Schmidt, Karsten Schmidt, Gunnar Wagenknecht, David Williams, Darin Wright
 
<!--
 
<!--
 
* '''Signed-up:''' Martin Oberhuber, Tom Schindl,  
 
* '''Signed-up:''' Martin Oberhuber, Tom Schindl,  
Line 64: Line 64:
 
* '''No-Show:'''  
 
* '''No-Show:'''  
 
* '''Unknown:'''  
 
* '''Unknown:'''  
** John Arthorne, Wayne "Mad Dog" Beaton, David Carver, Eugene Chan, Brian Fitzpatrick, Mik Kersten, Markus Knauer, Ed Merks, Andrew Overholt, Bernd Kolb (to proxy Karsten Schmidt), Michael Scharf
+
** John Arthorne, Wayne "Mad Dog" Beaton, Eugene Chan, Brian Fitzpatrick, Mik Kersten, Markus Knauer, Ed Merks, Andrew Overholt, Bernd Kolb (to proxy Karsten Schmidt), Michael Scharf
** Oliver Cole, Doug Gaff, Richard Gronback, Mike Milinkovich
+
** Oliver Cole, Doug Gaff, Mike Milinkovich
** John Graham, Doug Schaefer, Mike Wilson, Mark Vandenbrink
+
** John Graham, Doug Schaefer, Mike Wilson,  
 
** Doug Clarke, Jochen Krause, Jeff McAffer
 
** Doug Clarke, Jochen Krause, Jeff McAffer
 
** Naci Dai, Bjorn Freeman-Benson, Wenfeng Li, Philippe Mulet, Mary Ruddy, David Williams
 
** Naci Dai, Bjorn Freeman-Benson, Wenfeng Li, Philippe Mulet, Mary Ruddy, David Williams
Line 89: Line 89:
 
=== Administrative ===
 
=== Administrative ===
 
* '''New Members''': Linda Chan, Sven Efftinge (new Strategic Member)
 
* '''New Members''': Linda Chan, Sven Efftinge (new Strategic Member)
 +
** '''RESOLUTION''' - everybody in favor of appointing Linda. '''AI Martin''' ask mike to appoint.
 +
 
* New '''Dormant Members''' - see [[Architecture Council/Members and Mentors]]
 
* New '''Dormant Members''' - see [[Architecture Council/Members and Mentors]]
* Some '''Bio's''' still not filled in: [[Architecture Council/Members and Mentors]] - David Williams
+
* '''Some Bio's''' still not filled in: [[Architecture Council/Members and Mentors]] - David Williams
 
* '''AC Admin via the [http://portal.eclipse.org Portal]'''
 
* '''AC Admin via the [http://portal.eclipse.org Portal]'''
 
** 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
 
** 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
Line 98: Line 100:
 
** {{bug|255383}} - [http://www.eclipse.org/org/foundation/council.php#architecture councils page] doesn't show company affiliation for PMC reps
 
** {{bug|255383}} - [http://www.eclipse.org/org/foundation/council.php#architecture councils page] doesn't show company affiliation for PMC reps
 
** {{bug|255385}} - [http://www.eclipse.org/org/foundation/council.php#architecture councils page] doesn't show PMC reps for Modeling, Birt, Stp
 
** {{bug|255385}} - [http://www.eclipse.org/org/foundation/council.php#architecture councils page] doesn't show PMC reps for Modeling, Birt, Stp
 +
** Karl, Bjorn, Gabe (and sometimes Denis) working on the Portal
 
** 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
 
** 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
* Projects in need of Mentors
+
 
** {{bug|256220}} Silverlight (SLDT), {{bug|256477}} STEM
+
* '''IP/Legal Discussions:''' Janet's [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00695.html E-Mail] asking PMC's and AC to answer IP/Legal related questions:
** Bugs been open for some time, is our process good enough?
+
** IPZilla Infrastructure for "closed group" discussions should be completed soon. '''AI Mike''' inform all when it's in place.
** See [[Architecture Council/Members and Mentors#Projects that need mentors]]: ACTF, Aperi, Apogee (Dave Carver), COSMOS, PDT -- '''AI File a Bug''' (best have the project file one), [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Architecture%20Council use this link] for filing the bug. '''AI Wayne''' contact technology projects telling them to file the bug.
+
 
* Janet's [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00695.html E-Mail] asking PMC's and AC to answer IP/Legal related questions:
+
* '''AC Website Revamp''' needed to make the information that's already there more consumable
** IPZilla update (Mike) ?
+
** Who could revamp the [[Architecture Council]] page? - '''AI Dave Carver''' take a look
* AC Website Revamp needed to make the information that's already there more consumable
+
 
** Who could revamp the [[Architecture Council]] page?
+
* '''PMC Representation''' on the AC
* PMC Representation on the AC
+
 
** Up to now, the AC meetings are totally voluntary, offline interaction is as good as direct interaction
 
** Up to now, the AC meetings are totally voluntary, offline interaction is as good as direct interaction
 
** Martin would like to ask PMC Reps either attend the meetings or send a designated delegate (might be another appointed member), in order to ensure full coverage
 
** Martin would like to ask PMC Reps either attend the meetings or send a designated delegate (might be another appointed member), in order to ensure full coverage
 
** Create a table per PMC on the meeting notes (similar to the Board meetings)
 
** Create a table per PMC on the meeting notes (similar to the Board meetings)
** BIRT, WTP, Tools currently don't have an active official rep
+
** BIRT, WTP, Tools currently don't have an active official rep - '''Dave Carver''' to ask Dave W
 +
** '''RESOLUTION''' everybody OK with requiring PMC attendance
 +
 
 +
== Mentorship ==
 +
* {{bug|256220}} Silverlight (SLDT), {{bug|256477}} STEM
 +
** Bugs been open for some time, is our process good enough?
 +
** Wayne: Projects need to be interesting, so they should be able to attract a mentor...
 +
** Martin: AC should be responsive, each of us should feel responsible for answering requests timely. '''AI Wayne''' volunteers to be the be the initial contact (at least partly)
 +
* See [[Architecture Council/Members and Mentors#Projects that need mentors]] (or were grandfathered) - ACTF, Aperi, Apogee (Dave Carver), COSMOS, PDT - Wayne trying to encourage project find a mentor (by [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Architecture%20Council filing a bug].
 +
** Mass mailing likely won't help... at least as long as we don't have a pool of mentors just waiting to get mentors. So, for now, direct PMC interaction will likely help more.
 +
** '''AI Andrew Overholt''': file bug asking for mentors for linux distros!
 +
* 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)
 +
** '''RESOLUTION:''' 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?
 
** SWOT analysis done -- Don going to post meeting minutes; Board approved an USD 20.000 budget for improving the Release Train
 
** SWOT analysis done -- Don going to post meeting minutes; Board approved an USD 20.000 budget for improving the Release Train
** Don going to call in for a StAC telecon meeting in January (or late february) in order to prioritize items how the money should be spent -- might be for Galileo or probably next year's train
+
** Don going to call in for a StAC telecon meeting in January (or early february) in order to prioritize items how the money should be spent -- might be for Galileo or probably next year's train
 
** If successful, this might become a recurring thing every year
 
** If successful, this might become a recurring thing every year
* Board Meeting Update, based on [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg00772.html Martin's AC update]
+
* '''Board Meeting Update''', based on [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg00772.html Martin's AC update]
 
** Confidential until the Board Meeting minutes are posted on the [http://www.eclipse.org/org/foundation/minutes.php Foundation Minutes page] - navigated from Eclipse homepage by "About us" > "Foundation" > "Meeting Minutes"
 
** Confidential until the Board Meeting minutes are posted on the [http://www.eclipse.org/org/foundation/minutes.php Foundation Minutes page] - navigated from Eclipse homepage by "About us" > "Foundation" > "Meeting Minutes"
 +
** 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
  
 
=== New Topics ===
 
=== New Topics ===
* '''Oisin: Mentorship''' - 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.
 
 
* '''Tom: 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
 
* '''Tom: 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: why cannot leverage the Wiki? - Make a Template Page on the Wiki (used for a couple proposals already) - '''AI Dave, Chris''' add links to template pages
 +
 
* '''Tom: Best practice for picking up I-builds''' - HTTP downloads are slow, installation cumbersome
 
* '''Tom: Best practice for picking up I-builds''' - HTTP downloads are slow, installation cumbersome
 
** Martin tried the [[Eclipse Project Update Sites]] with [[Equinox p2 Repository Mirroring]] and [http://help.eclipse.org/ganymede/topic/org.eclipse.platform.doc.isv/guide/p2_director.html p2 Director] scripts to update, but found {{bug|258865}} (invalid 3.5-I-builds repository), {{bug|258680}} (mirroring) and {{bug|258683}} (install) - currently not usable
 
** Martin tried the [[Eclipse Project Update Sites]] with [[Equinox p2 Repository Mirroring]] and [http://help.eclipse.org/ganymede/topic/org.eclipse.platform.doc.isv/guide/p2_director.html p2 Director] scripts to update, but found {{bug|258865}} (invalid 3.5-I-builds repository), {{bug|258680}} (mirroring) and {{bug|258683}} (install) - currently not usable
 
** Using SSH / SCP with some scripts for installation from the ZIPs right now
 
** Using SSH / SCP with some scripts for installation from the ZIPs right now
 +
** Dave Carver using a script ("custom eclipse") on sourceforge - '''AI Dave''' put a link into meeting notes
 +
** Andrew Overholt: As part of Common Builder (CBI), looking at how to best get the bits
 
** Should the AC host a page with a recommended best practice?
 
** Should the AC host a page with a recommended best practice?
 +
** '''RESOLUTION:''' Wait until we have a best practice (by means of CBI, or p2, or a script)
 +
 
* '''Christian Kurzke (TmL project, DSDP PMC)''' asked:
 
* '''Christian Kurzke (TmL project, DSDP PMC)''' asked:
 
** How do other projects maintain an IP-clean repository? Does anybody perform regular Black Duck scans? Should the Eclipse Foundation do them?
 
** How do other projects maintain an IP-clean repository? Does anybody perform regular Black Duck scans? Should the Eclipse Foundation do them?
 +
*** Bjorn, Wayne: It seems like Foundation does occasionally scan the repository
 
** TmL team does them based on previous Motorola use, but sees lots of effort in sorting out false positives
 
** TmL team does them based on previous Motorola use, but sees lots of effort in sorting out false positives
 +
 
* '''Martin: Duplication''' - [http://www.eclipse.org/m2eclipse m2eclipse] and [http://www.eclipse.org/iam IAM] for Maven
 
* '''Martin: Duplication''' - [http://www.eclipse.org/m2eclipse m2eclipse] and [http://www.eclipse.org/iam IAM] for Maven
 +
** 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.
 +
 
* '''Martin: Architecture Diagrams''' -  
 
* '''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.
 
** 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.
Line 140: Line 169:
 
*** 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?)
 
*** 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).
 
*** 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).
 +
** '''AI Martin''' ask on mailing list
  
 
=== Recent Discussions ===
 
=== Recent Discussions ===
 
* '''Dave Carver:''' [[Architecture Council/Top Ten Project Development Practices]] - Agile Project Management
 
* '''Dave Carver:''' [[Architecture Council/Top Ten Project Development Practices]] - Agile Project Management
* '''Patterns''' idea picked up by 2 Eclipsecon Tutorials -- started [[Architecture Council/Top Ten Recommendations#Design Patterns]]
 
 
* '''Wayne:''' {{bug|252015}} Here is something you should know, [[Architecture Council/Things Committers Should Know/Staging]] more authors needed?
 
* '''Wayne:''' {{bug|252015}} Here is something you should know, [[Architecture Council/Things Committers Should Know/Staging]] more authors needed?
* Martin: [[Architecture Council/F2F ESE 2008]] - thoughts in retrospect
+
** started with IP issues; participation from others wou
 
* Denis' [http://eclipsewebmaster.blogspot.com/2008/11/why-users-dont-bother-to-file-bug.html blog on dead bugzilla's].
 
* Denis' [http://eclipsewebmaster.blogspot.com/2008/11/why-users-dont-bother-to-file-bug.html blog on dead bugzilla's].
 
** {{bug|256660}} What are best practices to keep bugzilla alive and users interested, without taking away too much time from committers?
 
** {{bug|256660}} What are best practices to keep bugzilla alive and users interested, without taking away too much time from committers?
** Should it be added as advice for mentored projects?
+
** Should it be added as advice for mentored projects? Should the AC engage in the public discussion?
** Should the AC engage in the public discussion?
+
* [https://www.eclipsecon.org/submissions/2009/view_talk.php?id=527 EclipseCon panel]
+
** [[Architecture Council/Ask the AC]] ideas for questions to discuss
+
** Who wants to participate on the panel, or be a moderator? - Bjorn, zx, Wayne, Mik, Markus, '''Jeff''', '''Ed'''
+
* [[Architecture Council/F2F EclipseCon 2009]] - Sunday afternoon - sign up and add to the agenda
+
* {{bug|256448}} API Tooling for extensions / How to treat propertyTester properties in ISV docs (best practice searched)
+
* {{bug|167144}} "eclipse.common" bundle -- Bundle / Project granularity?
+
* {{bug|253889}} JIRA vs bugzilla - just close it?
+
* {{bug|249371}} The new [http://www.eclipse.org Eclipse.org homepage]
+
* {{bug|249745}} Repository Best Practices (Subversive vs Subclipse); Mercurial, Git Bazaar -- {{bug|257706}} now requesting git specifically
+
* {{bug|246840}} Jobs and ISchedulingRules - discussion concluded?
+
* Items to move into IPZilla
+
** {{bug|249959}} Copyright Header in checked-in generated artifacts
+
** {{bug|246945}} Interfacing with Libs that are not EPL Compatible (mostly LGPL)
+
  
 
=== Old items ===
 
=== Old items ===
* EMO: {{bug|250317}} How to officially communicate Requirements (as per the board, dev process, IP policy...) to the PMCs, Project Leads, Committers?
 
* '''RC - Roadmap Process''': [[RequirementsCouncilThemesAndPriorities]] - are we happy with it?
 
* '''PC''' - Richard Gronback: '''New [[Galileo]] Requirements''' from the Planning Council?
 
** Must do: Use only Published API by M6
 
** Must do: Provide basic Capability / Activity Definitions by M6
 
** Must do: Use Babel by M6
 
  
* See also [[Architecture Council/Open Issues]] for overflow items
+
* See also [[Architecture Council/Open Issues]] for overflow items that were not discussed
  
 
== Action Items ==
 
== Action Items ==

Revision as of 13:18, 16 December 2008

Meeting Title: Architecture Council Monthly Meeting
Date & Time: Tuesday December 16, 2008 at 1600 UTC / 0800 SFO / 1100 Ottawa / 1600 London / 1700 Berlin
Html.gifHTML | Ical.gifiCal
Dial-in: (+1) 613.287.8000 (Ottawa and international) or
866.362.7064 (toll-free North America)
passcode 464440#

Attendees

BIRT: Wenfeng Li
DTP: Brian Fitzpatrick
DSDP: Doug Gaff
Eclipse: Kevin Haaland
Modeling: Richard Gronback Ed Merks
RT: Jeff McAffer Jochen Krause
STP:
Technology: Gunnar Wagenknecht Wayne Beaton
Tools: John Duimovich
TPTP: Eugene Chan
WTP:
  • Use the Doodle Attendance Tracking Poll to confirm attendance or send regrets for this meeting. See this message for how to use it. All AC Members are invited.
    • Signed-up: Chris Aniszczyk, Bjorn Freeman-Benson, Martin Oberhuber, Tom Schindl, Darin Swanson, Mark Vandenbrink, Tom Watson, Gary Xue
    • Regrets: Boris Bokowski, David Carver, Adrian Colyer, Sven Efftinge, Richard Gronback, Neil Hauge, Oisin Hurley, Georg Schmidt, Karsten Schmidt, Gunnar Wagenknecht, David Williams, Darin Wright

Agenda / Notes

  • Feel free to edit, but not during the call!

Review of Action Items

Administrative

  • New Members: Linda Chan, Sven Efftinge (new Strategic Member)
    • RESOLUTION - everybody in favor of appointing Linda. AI Martin ask mike to appoint.
  • IP/Legal Discussions: Janet's E-Mail asking PMC's and AC to answer IP/Legal related questions:
    • IPZilla Infrastructure for "closed group" discussions should be completed soon. AI Mike inform all when it's in place.
  • AC Website Revamp needed to make the information that's already there more consumable
  • PMC Representation on the AC
    • Up to now, the AC meetings are totally voluntary, offline interaction is as good as direct interaction
    • Martin would like to ask PMC Reps either attend the meetings or send a designated delegate (might be another appointed member), in order to ensure full coverage
    • Create a table per PMC on the meeting notes (similar to the Board meetings)
    • BIRT, WTP, Tools currently don't have an active official rep - Dave Carver to ask Dave W
    • RESOLUTION everybody OK with requiring PMC attendance

Mentorship

  • bug 256220 Silverlight (SLDT), bug 256477 STEM
    • Bugs been open for some time, is our process good enough?
    • Wayne: Projects need to be interesting, so they should be able to attract a mentor...
    • Martin: AC should be responsive, each of us should feel responsible for answering requests timely. AI Wayne volunteers to be the be the initial contact (at least partly)
  • See Architecture Council/Members and Mentors#Projects that need mentors (or were grandfathered) - ACTF, Aperi, Apogee (Dave Carver), COSMOS, PDT - Wayne trying to encourage project find a mentor (by filing a bug.
    • Mass mailing likely won't help... at least as long as we don't have a pool of mentors just waiting to get mentors. So, for now, direct PMC interaction will likely help more.
    • AI Andrew Overholt: file bug asking for mentors for linux distros!
  • 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)
    • RESOLUTION: we agree to keep the 2-mentor requirement

News from the EMO & Councils

  • Don: StAC meeting at Eclipse World -- outcome?
    • SWOT analysis done -- Don going to post meeting minutes; Board approved an USD 20.000 budget for improving the Release Train
    • Don going to call in for a StAC telecon meeting in January (or early february) in order to prioritize items how the money should be spent -- might be for Galileo or probably next year's train
    • If successful, this might become a recurring thing every year
  • Board Meeting Update, based on Martin's AC update
    • Confidential until the Board Meeting minutes are posted on the Foundation Minutes page - navigated from Eclipse homepage by "About us" > "Foundation" > "Meeting Minutes"
    • 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: 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: why cannot leverage the Wiki? - Make a Template Page on the Wiki (used for a couple proposals already) - AI Dave, Chris add links to template pages
  • Tom: Best practice for picking up I-builds - HTTP downloads are slow, installation cumbersome
    • Martin tried the Eclipse Project Update Sites with Equinox p2 Repository Mirroring and p2 Director scripts to update, but found bug 258865 (invalid 3.5-I-builds repository), bug 258680 (mirroring) and bug 258683 (install) - currently not usable
    • Using SSH / SCP with some scripts for installation from the ZIPs right now
    • Dave Carver using a script ("custom eclipse") on sourceforge - AI Dave put a link into meeting notes
    • Andrew Overholt: As part of Common Builder (CBI), looking at how to best get the bits
    • Should the AC host a page with a recommended best practice?
    • RESOLUTION: Wait until we have a best practice (by means of CBI, or p2, or a script)
  • Christian Kurzke (TmL project, DSDP PMC) asked:
    • How do other projects maintain an IP-clean repository? Does anybody perform regular Black Duck scans? Should the Eclipse Foundation do them?
      • Bjorn, Wayne: It seems like Foundation does occasionally scan the repository
    • TmL team does them based on previous Motorola use, but sees lots of effort in sorting out false positives
  • Martin: Duplication - m2eclipse and IAM for Maven
    • 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.
  • 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).
    • AI Martin ask on mailing list

Recent Discussions

Old items

Action Items

Next Meeting

Back to the top