https://wiki.osgeo.org/w/index.php?action=history&feed=atom&title=Template%3ACode_Provenance_Review_Goals 2026-04-14T12:27:51Z Revision history for this page on the wiki MediaWiki 1.35.9 https://wiki.osgeo.org/w/index.php?title=Template:Code_Provenance_Review_Goals&diff=17389&oldid=prev 2007-08-24T08:59:42Z

<p><span dir="auto"><span class="autocomment">corrected spelling error</span></span></p> <table class="diff diff-contentalign-left diff-editfont-monospace" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 08:59, 24 August 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l5" >Line 5:</td> <td colspan="2" class="diff-lineno">Line 5:</td></tr> <tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>A code provenance review is desirable because it reduces the risk of the foundation, project developers or software users becoming involved in a legal action or having their use of the software disrupted by sudden removal of improperly contributed code.  In particular, many enterprises will not build on open source software projects without some degree of assurance that care is being taken to avoid improper contributions.  </div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>A code provenance review is desirable because it reduces the risk of the foundation, project developers or software users becoming involved in a legal action or having their use of the software disrupted by sudden removal of improperly contributed code.  In particular, many enterprises will not build on open source software projects without some degree of assurance that care is being taken to avoid improper contributions.  </div></td></tr> <tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr> <tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly.  The onus is not on us to prove there are no <del class="diffchange diffchange-inline">problem</del>.  However we want to ensure we do not release code with provenance issues that we could have identified and corrected with a reasonable effort.</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly.  The onus is not on us to prove there are no <ins class="diffchange diffchange-inline">problems</ins>.  However we want to ensure we do not release code with provenance issues that we could have identified and corrected with a reasonable effort.</div></td></tr> </table>

Wiki-Ericjarvies https://wiki.osgeo.org/w/index.php?title=Template:Code_Provenance_Review_Goals&diff=3130&oldid=prev 2006-04-03T17:39:11Z

<p>created a template from the Goals of Code Provenance Review</p> <p><b>New page</b></p><div>= Goal =<br /> <br /> To establish a reasonable comfort level that projects going through incubation do not have improperly contributed code, and that the code is all under the project license.<br /> <br /> A code provenance review is desirable because it reduces the risk of the foundation, project developers or software users becoming involved in a legal action or having their use of the software disrupted by sudden removal of improperly contributed code. In particular, many enterprises will not build on open source software projects without some degree of assurance that care is being taken to avoid improper contributions. <br /> <br /> It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on us to prove there are no problem. However we want to ensure we do not release code with provenance issues that we could have identified and corrected with a reasonable effort.</div>

Arnulf