<?xml version="1.0"?>
<document>

  <properties>
    <author email="jon@latchkey.com">Jon S. Stevens</author>
    <author email="husted@apache.com">Ted Husted</author>
    <author email="jason@zenplex.com">Jason van Zyl</author>
    <title>Roles and Responsibilities</title>
  </properties>

  <body>

    <section name="Roles and Responsibilities">
      <p>
        The roles and responsibilities that people can assume in the project
        are based on merit. Everybody can help no matter what their role.
        Those who have been long term or valuable contributors to the project
        obtain the right to vote and commit directly to the source repository.
      </p>

      <subsection name="Users">

        <p>
          Users are the people who use the products of the Project. People in
          this role aren't contributing code, but they are using the products,
          reporting bugs, making feature requests, and such. This is by far
          the most important category of people as, without users, there is no
          reason for the Project.
        </p>

        <p>
          When a user starts to contribute code or documentation patches, they
          become a Contributor.
        </p>
      </subsection>

      <subsection name="Contributors">

        <p>
          Contributors are the people who write code or documentation patches or
          contribute positively to the project in other ways. A volunteer's
          contribution is always recognized. In source code, all volunteers
          who contribute to a source file may add their name to the list of
          authors for that file.
        </p>
      </subsection>

      <subsection name="Committers">

        <p>
          Contributors who give frequent and valuable contributions to a
          subproject of the Project can have their status promoted to that of
          a &quot;
          <em>Committer</em>&quot; for that subproject. A Committer
          has write access to the source code repository and gains voting
          rights allowing them to affect the future of the subproject.
        </p>

        <p>
          In order for a Contributor to become a Committer, another Committer
          can nominate that Contributor or the Contributor can ask for it.
        </p>

        <p>
          Once a Contributor is nominated, all of the Committers for a subproject
          will vote. If there are at least 3 positive votes and no negative
          votes, the Contributor is converted into a Committer and given write
          access to the source code repository for that subproject. This is an
          example offer letter that should be sent to the volunteer after
          3 positive votes have been received:
        </p>

        <source><![CDATA[
        Dear Contributor,

        The DB project would like to offer you commit privileges.
        We have been impressed with your contributions up till now, and
        believe that your involvement will improve the quality of the
        libraries we produce.

        It is important that you realize that these commit privileges give
        you access to the specific DB project repository for which you
        are involved with. They do not provide commit access to any other
        Apache based project. Those projects will have to grant you commit
        privileges themselves.

        If you are interested in having commit privileges, please just let us
        know, and we will setup an account on apache.org. It would expedite
        the process if you could provide your preferred account name and
        possibly a public SSH key. This process could take a few days once
        we get this information.

        We all hope that you accept this invitation.

        The DB Project Management Committee.
        ]]></source>

        <p>
          Once there are 3 positive votes and the response to the above letter
          has been received, someone from the project community who already has
          commit access should send email to:
          <strong>root at apache.org</strong>
          that the account should be created. The following information
          must be included in the email:
        </p>

        <ul>
          <li>
            The name and email address of the new user.
            (ie: John Smith &lt;john.smith@foo.com&gt;)
          </li>
          <li>
            Suggested account userid. This is optional.
            (ie: jmsith)
          </li>
          <li>
            The project that the user should be given access to.
            (ie: DB Foo)
          </li>
          <li>
            The results of the votes. In other words, the names and email
            addresses of the committers who approved the addition.
          </li>
        </ul>

        <p>
          The new committer should also send an email to
          <strong>asf at jaguNET.com</strong>
          with the following information (please cut and paste to return format):
        </p>

        <blockquote>
          Name: {your name}
          <br/>
          Email: {your email address on the ASF lists}
          <br/>
          Projects: {comma separated list of ASF projects to which you have commit access}
          <br/>
          Key: {a blank line followed by your key}
        </blockquote>

        <p>For example:</p>

        <blockquote>
          Name: Joe Foobar
          <br/>
          Email: joe@byteme.com
          <br/>
          Projects: Tomcat, httpd
          <br/>
          Key:
          <br/>
          adklajdAL()@ N*@U)U@()@@ @)U@
        </blockquote>

        <p>
          Finally, a new committer should also submit a signed copy of the Contributor
          License Agreement to the ASF. See the
          <a href="http://www.apache.org/licenses/#clas">
            <strong>Licenses page</strong></a> for details.
        </p>

        <p>
          Note 0: If a committer already has an account on the apache.org server
          and the committer needs commit access to additional projects, then all
          that needs to be done is to have the user notify
          pmc@db.apache.org with the results of the voting (as documented
          above) and the user will be given access. In other words, the root
          email address should only be used on the basis of new account
          creation.
        </p>

        <p>
          Note 1: All committers will be given access to the db-site module
          on request. In other words, committers should be able to update the
          main DB website.
        </p>

        <!--

        This may be required shortly. But not currently. jvz.

        <p>
          Note 2: If the module that the committer needs access to is a sub
          module within a project (ie: jakarta-turbine-tdk or
          jakarta-avalon-logkit), it is up to the individual project to
          determine how to deal with giving out access. In other words, access
          may be granted by default to all sub modules or it can be granted by
          vote.
        </p>

        -->

        <p>
          At times, Committers may go inactive for a variety of reasons. A
          Committer that has been inactive for 6 months or more may lose their
          status as a Committer. Getting access back is as simple as
          re-requesting it on the project's Developer mailing list.
        </p>

        <p>
          A list of some of our current Committers can be found in our
          <a
            href="./whoweare.html">Project Credits</a>.
        </p>
      </subsection>

      <subsection name="Management Committee (PMC)">
        <p>
          Committers who frequently participate with valuable contributions may
          have their status promoted to that of a &quot;
          <em>Project Management
            Committee Member</em>&quot;. This committee is the official managing
          body of the DB Project and is responsible for setting overall
          project direction. In order to become a Member, someone on
          the PMC must nominate the Committer. The individual may then be
          approved with a 3/4 majority of the PMC.
        </p>

        <p>
          To view the Project Management Committee bylaws,
          <a href="management.html">
            click here</a>.
        </p>

        <p>
          A list of our current PMC Members can be found in our
          <a
            href="./whoweare.html">Project Credits</a>.
        </p>
      </subsection>
    </section>

  </body>
</document>
