<?xml version="1.0" encoding="UTF-8"?>
<!--
   ====================================================================
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
   ====================================================================
-->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd">

<document>
 <header>
  <title>Apache POI - Who We Are</title>
  <authors>
   <person name="Apache POI Developers" email="dev@poi.apache.org"/>
   </authors>
 </header>

 <body>

 <section><title>Apache POI - Who we are</title>
  <p>
    The Apache POI Project operates on a meritocracy: the more you do, the more
    responsibility you will obtain. This page lists all of the people who have
    gone the extra mile and are Committers. If you would like to get involved,
    the first step is to join the <a href="site:mailinglists">mailing lists</a>.
  </p>

  <p>
    We ask that you please do not send us emails privately asking for support.
    We are non-paid volunteers who help out with the project and we do not
    necessarily have the time or energy to help people on an individual basis.
    The <a href="site:mailinglists">mailing lists</a> have many individuals
    who will help answer detailed requests for help. The benefit of
    using mailing lists over private communication is that they are a shared
    resource where others can also learn from common questions.
  </p>
  <p>
    POI Developers count on feedback from the mailing lists. Many developers do take
    an active role on the lists.
  </p>

<!--  <section><title>Advisors</title>-->
<!--    <ul>-->
<!--       <li><a href="http://www.betaversion.org/~stefano/">Stefano Mazzocchi</a> (stefano at apache dot org)-->
<!--       </li>-->
<!--    </ul>-->
<!--  </section>-->

  <section><title>Project Chair</title>
    <ul>
      <li>Dominik Stadler (centic at apache dot org)</li>
    </ul>
  </section>
  <section><title>Committers</title>
    <ul>
      <!-- Alphabetical by surname -->
      <li>Tim Allison (tallison at apache dot org)</li>
      <li><a href="https://people.apache.org/list_B.html#kiwiwings">Andreas Beeker</a> (kiwiwings at apache dot org)</li>
      <li>Nick Burch (nick at apache dot org)</li>
      <li>Amol S Deshmukh (amol at apache dot org)</li>
      <li>David Fisher (wave at apache dot org)</li>
      <li>Jason Height (jheight at apache dot org)</li>
      <li>Marc Johnson (mjohnson at apache dot org)</li>
      <li><a href="http://www.rainer-klute.de/">Rainer Klute</a> (klute at apache dot org)</li>
      <li>Yegor Kozlov (yegor at apache dot org)</li>
      <li>Shawn Laubach (slaubach at apache dot org)</li>
      <li>Josh Micich (josh at apache dot org)</li>
      <li>Mark Murphy (jmarkmurphy at apache dot org)</li>
      <li>Danny Mui (dmui at apache dot org)</li>
      <li><a href="https://people.apache.org/~dnorth/">David North</a> (dnorth at apache dot org)</li>
      <li>Javen O'Neal (onealj at apache dot org)</li>
      <li>Uwe Schindler (uschindler at apache dot org)</li>
      <li>Avik Sengupta (avik at apache dot org)</li>
      <li>Dominik Stadler (centic at apache dot org)</li>
      <li><a href="http://members.iinet.net.au/~gstamp/glen/">Glen Stampoultzis</a> (glens at apache.org)</li>
      <li>Jon Svede (jsvede at apache dot org)</li>
      <li>Maxim Valyanskiy (maxcom at apache dot org)</li>
      <li>Sergey Vladimirov (sergey at apache dot org)</li>
      <li>Greg Woolsey (gwoolsey at apache dot org)</li>
    </ul>
  </section>

  <section><title>Emeritus Committers</title>
    <ul>
      <li>Andrew C. Oliver (acoliver at gmail dot com)</li>
      <li>Nicola Ken Barozzi (barozzi at nicolaken dot com)</li>
      <li>Ryan Ackley (sackley at apache dot org)</li>
      <li>Tetsuya Kitahata (ai at spa dot nifty dot com)</li>
    </ul>
  </section>
 </section>

 <section><title>I want some progress on a bug report!</title>
  <p>
      So you took the time to report a bug, provided information that should make
      it possible to reproduce the problem and fix it. Surely the fix is easy and
      should take a seasoned developer a few minutes at max to fix!

      So why is there no progress on your bug report? Is there nobody
      taking care when your problem is clearly stopping nearly everybody
      from using POI?

      We know that the absence of responses on bug-reports can be frustrating,
      sometimes bugs lie dormant for a long time for no apparent reason.

      Please always remember: <em>nobody is paid to work on POI</em>, the team is
      a bunch of volunteers who look at things in their free time.

      Because of that developers might choose to work on things based on a
      different priority than yours! Especially the quality and maturity of
      bug reports will affect if somebody decides to look at it.

      So the best way to help a bug report see progress is to provide more information
      if available or supply patches together with unit-tests.

      If you can, look at <a href="site:guidelines">Contribution Guidelines</a>
      for more information about providing patches.
  </p>
</section>

</body>
</document>
