<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Fork (software development) - Page 8 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Fork_(software_development)&amp;p=7">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Fork_%28software_development%29&amp;p=9">3.Next</a>
</p>
<p>stated that "The most important characteristic of a fork is that it spawns competing projects that cannot later exchange code, splitting the potential developer community". He notes in the <a href="page.php?w=Jargon_File">Jargon File</a>:</p>

<p>David A. Wheeler notes four possible outcomes of a fork, with examples:</p>

<p>
# The death of the fork. This is by far the most common case. It is easy to declare a fork, but considerable effort to continue independent development and support.<br/>
# A re-merging of the fork (e.g., <a href="page.php?w=egcs">egcs</a></p><p>
<a accesskey="1" href="page.php?w=Fork_(software_development)&amp;p=7">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Fork_%28software_development%29&amp;p=9">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
