Who We Are
Lucene Project Management Committee (PMC)
Like all Apache projects Lucene has a PMC that is responsible for the oversight and management the Lucene project. Lucene consists of several sub-projects, each of which have their own diverse communities and distinct groups of committers. The PMC relies on the guidance of the committers from each sub-project, particularly in regards to voting on releases, and in nominating new committers.
PMC members have karma for the all Lucene code, but as a general rule avoid making changes to sub-projects unless they have explicitly been made a committer of that sub-project by a vote of the PMC.
PMC Members
(in alphabetical order):
- Andrzej Bialecki <ab>
- Michael Busch <buschmi>
- Doug Cutting <cutting>
- Ted Dunning <tdunning>
- Scott Ganyo <scottganyo>
- Otis Gospodnetic <otis>
- Mark Harwood <mharwood>
- Erik Hatcher <ehatcher>
- Chris Hostetter <hossman>
- Grant Ingersoll <gsingers>
- Mike Klaas <klaas>
- Dennis Kubes <kubes>
- Chris A. Mattmann <mattmann>
- Mike McCandless <mikemccand>
- Ryan McKinley <ryan>
- Daniel Naber <dnaber>
- Sean Owen <srowen>
- Yonik Seeley <yonik>
- Sami Siren <siren>
- Andi Vajda <vajda>
- Jukka Zitting <jukka>
Emeritus PMC Members
- Christoph Goller
Lucene Committers
Please see individual sub-projects for lists of their committers.
Lucene PMC Guide
Here we document any specific processes or rules that the Lucene PMC has adopted. In general the Lucene PMC defaults to follow Apache's Project Management Committee Guide.
- New Lucene committers and PMC members shall require majority approval among the existing Lucene PMC members.