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="How to participate in the DITA Open Toolkit"/>
|
---|
11 | <meta name="abstract" content="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."/>
|
---|
12 | <meta name="description" content="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."/>
|
---|
13 | <meta name="DC.Relation" scheme="URI" content="../admin/DITA-OTProjectManagement.html"/>
|
---|
14 | <meta name="DC.Relation" scheme="URI" content="../admin/BugFixGuidelines-NoCLA.html"/>
|
---|
15 | <meta name="DC.Relation" scheme="URI" content="../admin/ContributionPolicy.html"/>
|
---|
16 | <meta name="DC.Relation" scheme="URI" content="../admin/ContributionForm.html"/>
|
---|
17 | <meta name="DC.Relation" scheme="URI" content="https://github.com/dita-ot/dita-ot/issues"/>
|
---|
18 | <meta name="DC.Relation" scheme="URI" content="https://lists.sourceforge.net/lists/listinfo/dita-ot-developer"/>
|
---|
19 | <meta name="DC.Relation" scheme="URI" content="https://help.github.com/articles/set-up-git"/>
|
---|
20 | <meta name="DC.Format" content="XHTML"/>
|
---|
21 | <meta name="DC.Identifier" content="howtoparticipate"/>
|
---|
22 | <meta name="DC.Language" content="en-us"/>
|
---|
23 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
---|
24 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
---|
25 | <title>How to participate in the DITA Open Toolkit</title>
|
---|
26 | </head>
|
---|
27 | <body id="howtoparticipate">
|
---|
28 |
|
---|
29 |
|
---|
30 | <h1 class="title topictitle1">How to participate in the DITA Open Toolkit</h1>
|
---|
31 |
|
---|
32 |
|
---|
33 | <div class="body"><p class="shortdesc">Any individual or any organization can contribute to the
|
---|
34 | project; contributions must adhere to the existing toolkit license(s)
|
---|
35 | and should fit in with the general goals of the project. All major
|
---|
36 | contributors will get appropriate recognition in release announcements
|
---|
37 | and on the project home page.</p>
|
---|
38 |
|
---|
39 | <p class="p">Contributors can submit new features, patches, and bug fixes using
|
---|
40 | existing github facilities (this is done by creating a "pull request"
|
---|
41 | within github). The Committer(s) who owns the relevant components
|
---|
42 | will first do due diligence to check code originality and licensing
|
---|
43 | according to the <a class="xref" href="ContributionPolicy.html" title="The purpose of the DITA Open Toolkit Contribution Policy is to set forth the general principles under which the DITA Open Toolkit project shall accept contributions, license contributions, license materials owned by this project, and manage other intellectual property matters.">DITA Open Toolkit Contribution Policy</a>. After
|
---|
44 | due diligence, the Committer(s) will use his/her own judgment on whether
|
---|
45 | to accept the code into the original code base, request updates to
|
---|
46 | the code, or suggest that the code be maintained as an external patch
|
---|
47 | or plug-in.</p>
|
---|
48 |
|
---|
49 | <div class="p">Contributions are always encouraged, and generally fall into one
|
---|
50 | of two groups, as determined by project Committers:<ul class="ul">
|
---|
51 | <li class="li">Bug fixes and minor patches are accepted with little overhead.</li>
|
---|
52 |
|
---|
53 | <li class="li">Major contributions require the contributor to sign a form stating
|
---|
54 | that the submitter is free to commit the code (individually or on
|
---|
55 | behalf of an employer), and that the code complies with the current
|
---|
56 | toolkit license terms.</li>
|
---|
57 |
|
---|
58 | </ul>
|
---|
59 | </div>
|
---|
60 |
|
---|
61 | </div>
|
---|
62 |
|
---|
63 | <div class="related-links">
|
---|
64 | <ul class="ullinks">
|
---|
65 | <li class="link ulchildlink"><strong><a href="../admin/BugFixGuidelines-NoCLA.html">Due diligence for submission of bug fixes and patches from non-committers</a></strong><br/>
|
---|
66 | Any organization or individual may submit bug fixes using a github "pull request", generally tied to a specific report in the project's issue tracker.</li>
|
---|
67 | <li class="link ulchildlink"><strong><a href="../admin/ContributionPolicy.html">DITA Open Toolkit Contribution Policy</a></strong><br/>
|
---|
68 | The purpose of the DITA Open Toolkit Contribution Policy is to set forth the general principles under which the DITA Open Toolkit project shall accept contributions, license contributions, license materials owned by this project, and manage other intellectual property matters.</li>
|
---|
69 | <li class="link ulchildlink"><strong><a href="../admin/ContributionForm.html">DITA-OT Contribution Questionnaire Form 1.2</a></strong><br/>
|
---|
70 | </li>
|
---|
71 | </ul>
|
---|
72 |
|
---|
73 | <div class="familylinks">
|
---|
74 | <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../admin/DITA-OTProjectManagement.html" title="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.">DITA Open Toolkit Project Management Guidelines</a></div>
|
---|
75 | </div>
|
---|
76 | <div class="relinfo"><strong>Related information</strong><br/>
|
---|
77 | <div><a class="link" href="https://github.com/dita-ot/dita-ot/issues" target="_blank">DITA-OT Bug and Feature tracker at GitHub</a></div>
|
---|
78 | <div><a class="link" href="https://lists.sourceforge.net/lists/listinfo/dita-ot-developer" target="_blank">Sign up for toolkit developer mailing list</a></div>
|
---|
79 | <div><a class="link" href="https://help.github.com/articles/set-up-git" target="_blank">Help with getting started at GitHub</a></div>
|
---|
80 | </div>
|
---|
81 | </div>
|
---|
82 |
|
---|
83 | </body>
|
---|
84 | </html>
|
---|