Eclipse Project PMC
Who's running this project?
This page lists the people that are currently playing the PMC and subproject
leadership roles described in the project
charter. You will notice that there are many IBM people listed...
it's not because we want to do all the work (believe us!) - its just because
we built the first release of Eclipse before it became an open source
project, and others haven't had enough time yet to get involved in key
roles. We welcome new people who want to get involved and can make a contribution.
The Eclipse Project is a meritocracy. The more you contribute the more
responsibility you will earn.
We ask that you do not email us directly. Instead - use the mailing
lists. Mailing lists have been set up for each area of work, and are
the best way to get involved.
The Eclipse Project is managed by a small group known as the Eclipse
Project Management Committee (PMC).
The work of the project is organized into subprojects. Each subproject
has a leader who has overall responsibility for its success. Large subprojects
are further divided into component teams, each of who has a leader that
is responsible for its overall success. We have listed just the PMC and
subproject leaders here but you will encounter many dedicated Eclipse
Project committers and developers in the newsgroup
and mailing lists.
Project Management Committee Members
Mike ("McQ") Wilson, IBM Ottawa
McQ is the overall lead for the Eclipse Project aka PMC Lead.
He is a senior architect of the Eclipse SDK, a member of the Eclipse
Architecture Council and one of the original Eclipse Founders. His interests include computer
language design and implementation, semantic content publishing, web development,
and playing the cello. Mike leads the Platform and
Martin Oberhuber, Wind River
Martin is on the PMC representing the Community aspect of Eclipse and
the e4 project. He is a Platform Core Resources and e4 committer,
co-leading the e4 Resources work. Martin also serves on the
DSDP PMC and as
Target Management Project lead, and revitalized
Architecture Council as its chair. His interests include programming
languages, patterns and paradigms, optimizing development processes,
skiing, hiking, and playing all sorts of musical instruments.
Dani Megert, IBM Zurich
Dani leads the JDT subproject and
leads the Platform Search, Platform Text and JDT Text components. Dani worked at OTI and is one of the initial Eclipse Project committers.
His interests include user interface and API design, editors, performance and DJing.
John Arthorne, IBM Ottawa
John has worked on the Eclipse and Equinox
projects for the past decade in many different areas. He was the main developer on the resource model for many years,
and designed the platform's concurrency infrastructure. In recent years he has focused on the Orion project, provisioning (p2),
e4, and overall platform API quality. John is a member of the Eclipse
Architecture and Planning Councils, and the Eclipse Board of Directors.
John has authored numerous articles
book on Eclipse.
Andrew Overholt, Mozilla
Andrew works on open source technologies at Mozilla in Toronto.
He has been involved with the Eclipse community since 2005
and is a member of the Eclipse Architecture Council.
Andrew also leads the Linux Tools project. He is very interested in continuing to grow the
Eclipse community and to improve native platform integration.
Past PMC members
The following are Eclipse Project PMC Emeriti:
Erich is the original lead of the Eclipse Java development environment.
Prior to working on Eclipse he contributed to VA/Micro Edition (part
of IBM's Java solution for embedded device programming). Erich is well known for
his work on Design Patterns and JUnit.
Kevin was a key contributor to the design and implementation of the
Platform UI. He was previously component lead for the Platform UI, and
has a long history of building user interface technology at OTI. In a past
life he was the lead for the SWT team. Kevin also played a key role in
the IBM VA/Java project.
Jeff McAffer co-led the RT Equinox project and is the Founder of Code 9.
He is one of the architects of the Eclipse Platform and a co-author of
The Eclipse Rich Client Platform (Addison-Wesley).
Previous lives include being a Senior Technical Staff
Member at IBM and work in distributed/parallel OO computing (Server Smalltalk,
massively parallel Smalltalk, etc) as well as expert systems, meta-level architectures
and a PhD at the University of Tokyo.
Philippe is a former PMC and JDT project lead. Prior to Eclipse,
Philippe was responsible for the compiler and codeassist in IBM VA/Java
and VA/Micro Edition. Philippe was a member of the expert group on compiler
API (JSR199), representing IBM. His main interests are in compilation,
performance, scalability and meta-level architectures.
Steve Northover is the father of SWT (the Standard Widget Toolkit). Prior to
working on Eclipse, he worked on IBM Smalltalk, VA/Java, VA/Micro Edition.
His interests include programming languages, API design, operating systems,
user intefaces and code optimization.
John was a principal architect for the platform infrastructure. John played
a central role in the development of IBM VA/Java, VA/Micro Edition, and
Eclipse. His interests are in the areas of performance, scalability,
compilers, and just about anything that's hard.