| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
|
|---|
| 3 | "topic.dtd">
|
|---|
| 4 | <?Pub Inc?>
|
|---|
| 5 | <topic id="projectroles" xml:lang="en-us">
|
|---|
| 6 | <title>Project roles and responsibilities</title>
|
|---|
| 7 | <titlealts>
|
|---|
| 8 | <navtitle>Project roles</navtitle>
|
|---|
| 9 | </titlealts>
|
|---|
| 10 | <shortdesc>The DITA Open Toolkit (DITA-OT) project has the following roles: Project manager,
|
|---|
| 11 | committer, and contributor. Each role has different rights and obligations.</shortdesc>
|
|---|
| 12 | <prolog>
|
|---|
| 13 | <metadata>
|
|---|
| 14 | <keywords>
|
|---|
| 15 | <indexterm>DITA-OT project<indexterm>project roles</indexterm></indexterm>
|
|---|
| 16 | </keywords>
|
|---|
| 17 | </metadata>
|
|---|
| 18 | </prolog>
|
|---|
| 19 | <body>
|
|---|
| 20 | <dl>
|
|---|
| 21 | <dlentry>
|
|---|
| 22 | <dt>Project manager (PM)</dt>
|
|---|
| 23 | <dd>
|
|---|
| 24 | <p>The project manager is responsible for managing the project. The PM provides leadership to guide
|
|---|
| 25 | the overall direction of the project and removes obstacles, solves problems, and resolves conflicts.
|
|---|
| 26 | The PM works to ensure that the following goals are met:<ul>
|
|---|
| 27 | <li>The project operates effectively.</li>
|
|---|
| 28 | <li>All project plans, technical documents, and reports are publicly available.</li>
|
|---|
| 29 | <li>The project operates using the open-source rules of engagement, which stress meritocracy,
|
|---|
| 30 | transparency, and open participation.
|
|---|
| 31 | <!--These principles work together. Anyone can participate in this project. This open interaction, from answering questions to reporting bugs to making code contributions to creating designs, enables everyone to recognize and utilize the contributions.--></li>
|
|---|
| 32 | </ul></p>
|
|---|
| 33 | </dd>
|
|---|
| 34 | </dlentry>
|
|---|
| 35 | <dlentry>
|
|---|
| 36 | <dt>Committer</dt>
|
|---|
| 37 | <dd>Committers oversee the quality and originality of all contributions. Committers influences the
|
|---|
| 38 | development of the project and have write access to the source-code repository. This position
|
|---|
| 39 | reflects a track record of high-quality contributions to the project. </dd>
|
|---|
| 40 | </dlentry>
|
|---|
| 41 | <dlentry>
|
|---|
| 42 | <dt>Contributor</dt>
|
|---|
| 43 | <dd>Contributors contribute code, documentation, fixes, tests, or other work to the project.
|
|---|
| 44 | Contributors do not have write access to the source-code repository. There is no limit to the scope
|
|---|
| 45 | of such contributions, though contributors who expect to donate a large amount of new function to
|
|---|
| 46 | the project are encouraged to work with committers in advance.</dd>
|
|---|
| 47 | </dlentry>
|
|---|
| 48 | </dl>
|
|---|
| 49 | </body>
|
|---|
| 50 | </topic><?Pub Caret -3?>
|
|---|
| 51 | <?Pub *0000002130?>
|
|---|
