First cut at adding a no-license description

I have no idea if this looks good. We may want to get a designer to
figure out the layout here. :)

index.html

@@ -42,7 +42,8 @@ class: home
     </li>
   </ul>
   <p class="see-more callout">
-    None of these work for me. <a href="licenses">Show me more licenses »</a>
+     <em>None of these work for me.</em> What if I want to retain all my rights or <a href="no-license">I don’t want to choose a license?</a> 
+     <a href="licenses">Show me more licenses »</a>
   </p>
     </div>
   </body>

licenses/no-license.html

@@ -0,0 +1,25 @@
+---
+layout: license
+permalink: no-license/
+class: license-types
+
+description: By not choosing a license, you retain all rights and do not permit distribution, reproduction, or derivative works under applicable copyright law. You may be giving others some rights in cases where you publish your source code to a site that requires accepting terms of service to that affect. For example, publishing to GitHub requires you allow others to view and fork your code.
+
+note: This option may be subject to the Terms Of Use of the site where you publish your source code.
+
+how: Simply do nothing, though including a copyright notice is recommended.
+
+Required: 
+* include-copyright (if there is one)
+
+Permitted:
+* private-use
+* commercial-use
+
+Forbidden:
+* modifications
+* distribution
+* sublicense
+---
+
+Copyright [yyyy] [name of copyright owner]

no-license.html

@@ -0,0 +1,21 @@
+---
+layout: default
+permalink: no-license/
+---
+
+Copyright [yyyy] [name of copyright owner]
+
+<h1>No License</h1>
+<p>
+  It is your right to choose to not include a license with your source code. However a lot of people have the mistaken belief that not including a license is an easy way to let anyone do whatever they want with the source code. This is incorrect.
+</p>
+</p>
+  In the absence of a license file, the default copyright laws apply. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work. This might not be what you intend.
+</p>
+<p>
+  However, even in the absence of a license file, if you publish your source code in a public repository on GitHub, you have accepted the Terms of Service which do allow others some rights. Specifically, you allow others to view and fork your repository. But they still don’t have the rights to reproduce, distribute, or create derivative works.
+</p>
+<p>
+  So if you do want to share your work with others, please do consider choosing an open source license such as one of the ones featured on this site.
+</p>
+