a:3:{s:7:"#markup";O:25:"Drupal\Core\Render\Markup":1:{s:9:"*string";s:3189:"<span property="schema:name">Yaffs Licence FAQs</span>

            <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><h3>Do we need a Licence for Yaffs ?</h3>

<p>Yaffs is and will remain free of charge from <a href="/node/346">our web site</a>.  You can grab the latest version and work and test and play with it without charge.<br /><br />
It comes with a GNU General Public Public Licence, version 2,  : <a href="http://www.gnu.org/licenses/gpl-2.0.html">http://www.gnu.org/licenses/gpl-2.0.html</a>   As usual with GPL work, if you sell or distribute work embodying Yaffs you also have an obligation to disclose your associated Source Code to anyone who asks.</p>

<h3>What if we link other code to Yaffs ?</h3>

<p>The GPL obligation is not affected by the kind of linking between Yaffs and any associated code, nor is it affected by your disclosure of modifications you make to the code and release back into the main line.  For example if you use Yaffs under GPL with Linux you should treat it just the same as Linux code; if you want to publish a patched kernel please do.</p>

<h3>We do not want to disclose Source Code</h3>

<p>Because Aleph One Limited created and owns Yaffs we can sell you a Licence to use Yaffs which does not have the GNU GPLV2 obligations.  Such a licence is always perpetual, world-wide, non-exclusive. and free of any continuing royalty obligations.  It is paid for by a single fee at the time of signing a Licence Agreement between you and Aleph One.</p>

<p>The fee depends on the number of distinct Products in which Yaffs will be used, and there is a base price of GBP £10,000.  If more than one Product is included in the same Licence there is usually a reduction in the second fee.</p>

<h3>What do we do next ?</h3>

<p>Tell us some more about the product you will use Yaffs in.  We like the Agreement to contain a brief description of the hardware involved and the part number or product name and any internal code name.  If you want us to sign a Non-Disclosure Agreement before you give us these details, send it to us; we are used to signing them.  We can send you a standard form if you do not have one.</p>

<p>Then we will send a draft Agreement and price to you, and negotiate until we are both satisfied.  Next we each sign and exchange copies of the Agreement and you pay us.</p>

<h3>What happens when we sign a Licence ?</h3>

<p>When we have both signed a Licence Agreement and you have paid us we provide you with a tarball of files whose headers show that this code is under a proprietary Licence which you have bought from us.  You use these files to create the FS code you embed in your Products.</p>

<h3>Is there more information about licensing?</h3>

<p>Yes there is!</p>

<ul><li>More detail about the <a href="/yaffs-licence-sample">definition of a Product is given </a><a href="/node/32">i</a><a href="/yaffs-licence-sample">n our sample commercial licence</a>. </li>
	<li>Notes which give <a href="/licences-more-background-and-detail">further background and detail about our licensing</a>.</li>
</ul><p> </p>

<p> </p></div>
      ";}s:9:"#attached";a:0:{}s:6:"#cache";a:3:{s:8:"contexts";a:4:{i:0;s:28:"languages:language_interface";i:1;s:5:"theme";i:2;s:17:"url.path.is_front";i:3;s:16:"user.permissions";}s:4:"tags";a:3:{i:0;s:31:"config:filter.format.basic_html";i:1;s:8:"node:353";i:2;s:9:"node_view";}s:7:"max-age";i:-1;}}