| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
|
|---|
| 3 | "topic.dtd">
|
|---|
| 4 | <?Pub Sty _display FontColor="red"?>
|
|---|
| 5 | <topic id="contribution_policy" xml:lang="en-us">
|
|---|
| 6 | <title>DITA Open Toolkit Contribution Policy</title>
|
|---|
| 7 | <titlealts>
|
|---|
| 8 | <navtitle>Contribution policy</navtitle>
|
|---|
| 9 | </titlealts>
|
|---|
| 10 | <shortdesc>The purpose of the DITA Open Toolkit Contribution Policy
|
|---|
| 11 | is to set forth the general principles under which the DITA Open
|
|---|
| 12 | Toolkit project shall accept contributions, license contributions,
|
|---|
| 13 | license materials owned by this project, and manage other intellectual
|
|---|
| 14 | property matters.</shortdesc>
|
|---|
| 15 | <body>
|
|---|
| 16 | <section><title>Overview</title><p>The <xref keyref="license-CPL"></xref> (CPL)
|
|---|
| 17 | and <xref keyref="license-Apache2.0"></xref>, which are incorporated
|
|---|
| 18 | herein by reference, will serve as the primary licenses under
|
|---|
| 19 | which the Committer will accept contributions of software,
|
|---|
| 20 | documentation, information (including, but not limited to,
|
|---|
| 21 | ideas, concepts, know-how and techniques) and/or other materials
|
|---|
| 22 | (collectively "Content") to the project from Contributors.
|
|---|
| 23 | A copy of the CPL and Apache License 2.0 can be found at
|
|---|
| 24 | the root directory of the DITA Open Toolkit deliverable package.</p>
|
|---|
| 25 | <p>This Contribution Policy should at all times be interpreted
|
|---|
| 26 | in a manner that is consistent with the Purposes of the this
|
|---|
| 27 | project as set forth in the <xref href="DevelopmentProcess.xml">DITA
|
|---|
| 28 | Open Toolkit Development Process</xref> goals and objectives.
|
|---|
| 29 | This Contribution Policy shall serve as the basis for how
|
|---|
| 30 | non-Committers interact with this project through participation
|
|---|
| 31 | in this project, web-sites owned, controlled, published and/or
|
|---|
| 32 | managed under the auspices of the this project, or otherwise.</p>
|
|---|
| 33 | <p>The Common Public License and Apache License 2.0 shall serve
|
|---|
| 34 | as the primary licenses under which the Committer(s) shall
|
|---|
| 35 | accept software, documentation, information (including, but
|
|---|
| 36 | not limited to, ideas, concepts, know-how and techniques)
|
|---|
| 37 | and/or other materials (collectively "Content")
|
|---|
| 38 | from contributors including, but not limited to, Contributors
|
|---|
| 39 | and Committers.</p> <p>The DITA Open Toolkit project provides
|
|---|
| 40 | a process for accepting bug fixes and contributions from
|
|---|
| 41 | parties who have not accepted the license to be Contributors.
|
|---|
| 42 | See <xref href="BugFixGuidelines-NoCLA.xml">Due Diligence
|
|---|
| 43 | for Submission of Bug Fixes and Patches from Non-Committers</xref></p>
|
|---|
| 44 | </section>
|
|---|
| 45 | <section> <title>DUE DILIGENCE AND RECORD KEEPING</title>
|
|---|
| 46 | <p>The Committer(s), shall be responsible for scrutinizing all
|
|---|
| 47 | Content contributed to the DITA Open Toolkit project and
|
|---|
| 48 | help ensure that the Contribution Policy licensing requirements
|
|---|
| 49 | set forth above are met. Except as set forth below, the applicable
|
|---|
| 50 | Committer shall conduct the following activities prior to
|
|---|
| 51 | uploading any Content into the repository or otherwise making
|
|---|
| 52 | the Content available for distribution: </p> <ol>
|
|---|
| 53 | <li>Contact the potential contributor of the Content through an
|
|---|
| 54 | appropriate channel of communication and collect/confirm
|
|---|
| 55 | the following: <ul>
|
|---|
| 56 | <li>Contributor's name, current address, phone number
|
|---|
| 57 | and e-mail address;</li>
|
|---|
| 58 | <li>Name and contact information of the contributor's
|
|---|
| 59 | current employer, if any;</li>
|
|---|
| 60 | <li>If the contributor is not self-employed, the Committer
|
|---|
| 61 | must request and receive a signed <xref
|
|---|
| 62 | href="ContributionForm.xml">consent form</xref> (to be provided by
|
|---|
| 63 | the Committer) from the contributor's employer confirming
|
|---|
| 64 | that the employer does not object to the employee contributing
|
|---|
| 65 | the Content. </li>
|
|---|
| 66 | <li>Determine if the Content can be contributed under the
|
|---|
| 67 | terms of the CPL and Apache License 2.0 or the
|
|---|
| 68 | alternative terms and conditions supplied by the Contributor. This
|
|---|
| 69 | can be done by asking the contributor questions such as; <ol>
|
|---|
| 70 | <li>Did you develop all of the Content from scratch;</li>
|
|---|
| 71 | <li>If not, what materials did you use to develop the Content?</li>
|
|---|
| 72 | <li>Did you reference any confidential information of any
|
|---|
| 73 | third party? </li>
|
|---|
| 74 | <li>If you referenced third party materials, under what terms did
|
|---|
| 75 | you receive such materials? </li>
|
|---|
| 76 | </ol></li>
|
|---|
| 77 | <li>If it is determined by the Committer that the Content
|
|---|
| 78 | is not the original work of the Contributor, collect the
|
|---|
| 79 | contact information of the copyright holder of the original
|
|---|
| 80 | or underlying work. The copyright holder of the Content
|
|---|
| 81 | or the underlying work may then need to be contacted to
|
|---|
| 82 | collect additional information.</li>
|
|---|
| 83 | </ul> </li>
|
|---|
| 84 | <li>The <draft-comment>was "Committer(s)"</draft-comment>Contributor(s)
|
|---|
| 85 | shall document all information requested in (1) above and
|
|---|
| 86 | fill in Contribution Questionnaire (to be provided by the
|
|---|
| 87 | Committer) and provide the completed Contribution Questionnaire
|
|---|
| 88 | to the Committer.</li>
|
|---|
| 89 | <li>The Committer shall also be responsible for running a scan tool
|
|---|
| 90 | to help ensure that the Content does not include any code
|
|---|
| 91 | not identified by the contributor.</li>
|
|---|
| 92 | <li> Based on the information collected, the Committer shall use
|
|---|
| 93 | his/her reasonable judgment to determine if the Content
|
|---|
| 94 | can be contributed under terms and conditions that are
|
|---|
| 95 | consistent with the licensing requirements of this IP Policy. </li>
|
|---|
| 96 | </ol> <p>If the applicable Committer has any doubts about the
|
|---|
| 97 | ability to distribute the Content under terms and conditions
|
|---|
| 98 | that are consistent with the CPL and Apache License 2.0 or
|
|---|
| 99 | the proposed alternative terms and conditions, the Committer
|
|---|
| 100 | may not upload the code to the repository or otherwise distribute
|
|---|
| 101 | the Content. The Committer(s) shall be responsible for filing/maintaining
|
|---|
| 102 | the information collected for future reference as needed.</p>
|
|---|
| 103 | <p>The above record keeping requirements shall not apply to</p>
|
|---|
| 104 | <ul>
|
|---|
| 105 | <li>Minor modifications to Content previously contributed to and
|
|---|
| 106 | accepted by the Committer(s).</li>
|
|---|
| 107 | <li>Articles and White Papers</li>
|
|---|
| 108 | <li>Information or minor Content modifications provided through bug
|
|---|
| 109 | reports, mailing lists and news groups </li>
|
|---|
| 110 | </ul> <p>While the record keeping requirements do not apply
|
|---|
| 111 | to the items listed above, Committers must conduct reasonable
|
|---|
| 112 | due diligence to satisfy themselves that proposed Contributions
|
|---|
| 113 | can be licensed under the terms of the CPL and Apache License
|
|---|
| 114 | 2.0.</p> </section>
|
|---|
| 115 | </body>
|
|---|
| 116 | </topic>
|
|---|
