| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE html
|
|---|
| 3 | PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|---|
| 4 | <html xml:lang="en-us" lang="en-us">
|
|---|
| 5 | <head>
|
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|---|
| 7 | <meta name="copyright" content="(C) Copyright 2005"/>
|
|---|
| 8 | <meta name="DC.rights.owner" content="(C) Copyright 2005"/>
|
|---|
| 9 | <meta name="DC.Type" content="topic"/>
|
|---|
| 10 | <meta name="DC.Title" content="DITA Open Toolkit Project Management Guidelines"/>
|
|---|
| 11 | <meta name="abstract" content="The DITA Open Toolkit Project Management Guidelines are designed to provide information about how the project is managed. These guidelines are geared to an audience that needs information about how to participate in the development of the DITA-OT."/>
|
|---|
| 12 | <meta name="description" content="The DITA Open Toolkit Project Management Guidelines are designed to provide information about how the project is managed. These guidelines are geared to an audience that needs information about how to participate in the development of the DITA-OT."/>
|
|---|
| 13 | <meta name="DC.Relation" scheme="URI" content="../admin/DITA-OTProjectGoals.html"/>
|
|---|
| 14 | <meta name="DC.Relation" scheme="URI" content="../admin/DevelopmentProcess.html"/>
|
|---|
| 15 | <meta name="DC.Relation" scheme="URI" content="../admin/HowToParticipate.html"/>
|
|---|
| 16 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 17 | <meta name="DC.Identifier" content="ditaopentoolkitprojectmanagement"/>
|
|---|
| 18 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 19 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 20 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 21 | <title>DITA Open Toolkit Project Management Guidelines</title>
|
|---|
| 22 | </head>
|
|---|
| 23 | <body id="ditaopentoolkitprojectmanagement">
|
|---|
| 24 |
|
|---|
| 25 |
|
|---|
| 26 | <h1 class="title topictitle1">DITA Open Toolkit Project Management Guidelines</h1>
|
|---|
| 27 |
|
|---|
| 28 |
|
|---|
| 29 |
|
|---|
| 30 | <div class="body"><p class="shortdesc">The<span class="ph"><cite class="cite"> DITA Open Toolkit Project Management Guidelines</cite></span> are designed to
|
|---|
| 31 | provide information about how the project is managed. These guidelines are geared to an audience
|
|---|
| 32 | that needs information about how to participate in the development of the DITA-OT.</p>
|
|---|
| 33 |
|
|---|
| 34 | <p class="p">The project is managed similarly to commercial software-development projects; it uses
|
|---|
| 35 | requirements gathering, plan validation with stakeholders and contributors, scheduled activities,
|
|---|
| 36 | tests, reviews, and builds. Quality is strongly emphasized.</p>
|
|---|
| 37 |
|
|---|
| 38 | </div>
|
|---|
| 39 |
|
|---|
| 40 | <div class="related-links">
|
|---|
| 41 | <ul class="ullinks">
|
|---|
| 42 | <li class="link ulchildlink"><strong><a href="../admin/DITA-OTProjectGoals.html">Goals and objectives of the DITA Open Toolkit</a></strong><br/>
|
|---|
| 43 | The goal of the DITA Open Toolkit (DITA-OT) is to provide a high-quality implementation for production-level output of DITA content, built in a professionally-managed project environment by vetted contributors, and tested thoroughly for each release.</li>
|
|---|
| 44 | <li class="link ulchildlink"><strong><a href="../admin/DevelopmentProcess.html">DITA Open Toolkit development process</a></strong><br/>
|
|---|
| 45 | The DITA Open Toolkit (DITA-OT) development process is modeled after development processes for other popular and successful open-source projects, most notably Eclipse.</li>
|
|---|
| 46 | <li class="link ulchildlink"><strong><a href="../admin/HowToParticipate.html">How to participate in the DITA Open Toolkit</a></strong><br/>
|
|---|
| 47 | Any individual or any organization can contribute to the project; contributions must adhere to the existing toolkit license(s) and should fit in with the general goals of the project. All major contributors will get appropriate recognition in release announcements and on the project home page.</li>
|
|---|
| 48 | </ul>
|
|---|
| 49 | </div>
|
|---|
| 50 |
|
|---|
| 51 | </body>
|
|---|
| 52 | </html>
|
|---|
