Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Architecture Council/Minutes September 11 2008

Meeting Title: Architecture Council Monthly Meeting
Date & Time: Thursday September 11, 2008 at 1500 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#


  • Sign up here (alphabetical by last name), since it's hard to catch all names during the call.
  • Signed-up: Chris Aniszczyk, John Arthorne, Wayne "Mad Dog" Beaton, Boris Bokowski, Eugene Chan, Doug Clarke, Brian Fitzpatrick, Neil Hauge, Oisin Hurley, Jeff McAffer, Ed Merks, Philippe Mulet, Martin Oberhuber, Doug Schaefer, Michael Scharf, August Schmidt, Darin Swanson, Thomas Watson, Darin Wright
  • Tentative: John Duimovich, David Williams (will join late, if my conflict ends early)
  • Regrets: Oliver Cole (standing meeting), Bjorn Freeman-Benson (vacation), Doug Gaff (customer visit), John Graham(last minute client mtg), Richard Gronback (travelling), Thomas Hallgren, Mik Kersten (travelling), Markus Knauer (g-Eclipse tutorial), Jochen Krause (conference talk), Mike Milinkovich (conference talk), Andrew Overholt (meeting conflict), Brett Porter, Mary Ruddy (meeting conflict), Gunnar Wagenknecht (city council meeting), John Wiegand (travelling), Mike Wilson, Gary Xue (scheduling conflict)
  • Unknown: Adrian Colyer, Naci Dai, Timothy deBoer, Wenfeng Li, Steve Northover, Mark Vandenbrink

Agenda / Notes

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

Conference Bridge

  • Martin had issues getting the moderator PIN in. Additional PIN holders are Bjorn and Richard Gronback.
  • Oisin wasn't accepted into the call.
  • Anne to follow up

Review of Action Items

  • Last meeting Architecture Council/Minutes August 14 2008#Action Items
  • Ok green.gif Boris to start Architecture Council/Top Ten Recommendations
  • Ok green.gif Martin to draft an E-Mail to for review, inviting to put EAC on CC of bugs
  • Ok green.gif Martin to send E-Mail to EAC list as a reminder for "Architectural Walkthrough".
    • Mik to create initial "architectural walkthrough" material for mylyn. One more to follow before publicly announcing?
  • MichaelS to draft an E-Mail about the "plugin granularity" idea, searching for people to lead the effort
  • Ok green.gif Bjorn or Anne to add a "year of appointment" to members on the councils page
  • Ok green.gif Martin to propose alternate meeting scheme on the mailing list
  • Everyone to think about time commitments that can be made for "architectural things" at Eclipse (3 hours == 1 hr meeting + 2 hrs E-Mail and mentoring). A person who can not spend 3 hours per month on the EAC may want to consider resigning.
  • Everyone to propose new members on the mailing list
  • Ok green.gif Martin to create bugzilla bugs for the ISchedulingRule (bug 246840 and LGPL bug 246945 discussions


  • Meeting Dates - 2nd thurs accepted by everyone
  • EAC and bugzilla, and the E-Mail to Committers
    • Accepted by everyone. There's not so much traffic yet, keep mailing list on for now.
    • Who wants to be a secret-keeper of the EAC user's bugzilla password? MichaelS
  • Architecture Council/Members and Mentors - is it accurate?
    • Who's mentoring Apogee, COSMOS, Aperi?
      • Wayne: There are several mentor-less projects; in the past, projects have picked a mentor themselves - kick them to pick a mentor
    • AI Wayne list mentor-less Technology projects; AI Other PMC's list mentor-less projects from their domain
    • AI Everyone link to their Bio or Blog from the person name on the Architecture Council/Members and Mentors page
  • Dormant Status Proposal:
    • Accepted by everyone. Mike needs to sign off changes in membership.
    • Martin will try to keep track of activity, but can't promise.
  • New Member Proposals:
    • Are we too big a crowd already? New Member Proposals?
    • Some ideas (from E4 mostly): Dave Carver, Tom Schindl, Scott Lewis, Konstantin Kommissarchik, Kevin McGuire, David Orme, Paul Webster, Paul Coltron
      • Michael: Too big a crowd for round tables, but big crowd makes sense for "breakout style" meetings
  • Google Calendar Bugs and Requests -- does anybody know how to report them?
    • Changing an event, "Dont send" does send notifications
    • Response from to mailing list invitation should track attendance of each member separately
    • Ed: It's good, people need reminders
    • Jeff: Meeting invite should have the call-in details in there, AI Martin add
  • Wayne: Welcome Gunnar Wagenknecht as Technology PMC representative to the Architecture Council

News from the Board (EMO)

  • We have board reps and EMO reps on the council (Mike, Bjorn, Jeff, Ed, zx, Mik and Doug Gaff; Wayne)
  • Would like to have a standing "news from the board" topic, since as mentors we should be top informed
  • Other channels (PlanetEclipse, Blog, Committers / Project-leads mailing list, ...) should work but 1st-hand is better
  • Do information channels work well?
    • Ed: told Mike that the information channels are not good enough yet
    • Wayne: Bjorn has been blogging heavily about changes in Dev process
    • Boris: Particularly when new rules are coming into effect, there needs to be an ML announcement
    • Jeff: Dev process change was in mid of vacation season
    • Jeff: Some discussions at the Board are confidential, but will take opportunity of this slot in the future
    • Ed: The IP issue is a good example for sharing discussions with the EAC (IP advisory committee)
    • Jeff: What's people's viewpoint on dual licensing? Where is the EPL not sufficient?
      • TomW: In Equinox Framework, would like to adopt more Apache
      • Martin: Dual-license is largely redundant (weaker license covers all)
      • Jeff: Being able to say that "Everything from is EPL" is helpful
      • If somebody thinks that EPL is not sufficient for any reason, Jeff would like to know about it (and, make a CQ to Janet)

Top Ten Recommendations

  • Architecture Council/Top Ten Recommendations
  • More recommendations?
  • Add links into some code which exposes a recommendation as example?
  • Could easily convert a Recommendation into an article / blog post / ... ("The EAC Series")
    • MichaelS: "Pattern" idea. Example: EMF -- there is "good" usage and "bad" usage, how to share such patterns?
    • Example: Dealing with commands, dealing with Concurrency, dealing with Preferences, separation of UI / Non-UI
    • Pattern is also: Advantages / Disadvantages / When to apply
  • Boris: agree that it's good to flesh out these things, but not sure if Patterns is a good Next Step
    • One next step could be for AC members to blog about something
    • Martin: Just put together existing links to blogs / articles? AI Martin create Architecture Council/Links Collection, AI Everyone link into that page
  • AI Michael flesh out the idea and remind of the Pattern idea
    • Boris: Started a Wiki page called Ninja for advanced debugging tips

Deadlocks, Jobs and Scheduling

  • Examples: bug 245573 comment 12 (Dali JPA Tools Deadlock, John CC'd to EAC); bug 246840 discussion about ISchedulingRule (saving project preferences)
  • What is causing issues?
    • work performed during class loading (Activator.start()) - unknown context, can run at unpredictable times
    • work performed in callbacks - unknown context, avoid synchronous callbacks
    • 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
      • Jeff: Split off e.g. top ten concurrency best practices
      • Boris: Fine with collecting more for now and then work on forking off
  • Martin: Concurrency should be an item for E4. How is EAC related to E4?
    • Michael: Ask the E4 team to present architectural ideas to the AC
    • Ed: There are E4 calls, this would create duplication
    • DougS: There is no "E4 Architecture" per se, it's separate initiatives

LGPL Works-with vs. Requires

bug 246945

Action Items

Next Meeting

Back to the top