docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-12-21 20:30:10 +01:00
Code Issues Releases Wiki Activity

Even dryer templates

Browse Source 
* consolidate breadcrumb logic
* move h1 to header.html
* remove #home div from index.html
This commit is contained in:
Ben Balter 2013-07-13 15:42:46 -04:00
parent 59bd13024d
commit 12f4407bdc
5 changed files with 60 additions and 65 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
_includes/header.html
View File

@ -27,10 +27,18 @@
<body class="{{ page.layout }} {{ page.class }}">
<div class='container'>
{% if page.layout == "default" and page.hide_breadcrumbs != true %}
<ol class='breadcrumbs'>
<li>
<a href="/">Home</a>
</li>
</ol>
{% endif %}
{% unless page.hide_breadcrumbs == true %}
<ol class='breadcrumbs'>
<li>
{% if page.layout == "license" %}
<a href="/">Home</a> / <a href="/licenses/">Licenses</a>
{% else %}
<a href="/">Home</a>
{% endif %}
</li>
</ol>
{% endunless %}
{% if page.title %}
<h1>{{ page.title }}</h1>
{% endif %}

8
_layouts/license.html
View File

@ -1,13 +1,5 @@
{% include header.html %}
<ol class='breadcrumbs'>
<li>
<a href="/">Home</a> / <a href="/licenses/">Licenses</a>
</li>
</ol>
<h1>{{ page.title }}</h1>
<div class="cf">
<div class='license-body'>
<pre id="license-text">

3
about.md
View File

@ -2,10 +2,9 @@
title: About
layout: default
permalink: /about/
title: What&#8217;s this about?
---
# What&#8217;s this about?
We want to help developers choose a license for their source code.
If you already know what you&#8217;re doing and have a license you prefer to use, that&#8217;s great! We&#8217;re not here to change your mind. But if you are bewildered by the large number of OSS license choices, maybe we can help.

89
index.html
View File

@ -2,51 +2,48 @@
layout: default
class: home
hide_breadcrumbs: true
title: Choosing an OSS license doesn’t need to be scary
---
<div id='home'>
<h1>Choosing an OSS license doesn’t need to be scary.</h1>
<h2>
<span>{</span>
Which of the following best describes your situation?
<span>}</span>
</h2>
<ul class="situations cf">
<li class='whatever'>
<a href="licenses/mit"><img height='57' src='images/three-arrows@2x.png' width='72'></a>
<h3><a href="licenses/mit">I want it simple and permissive.</a></h3>
<p>
The <a href="licenses/mit">MIT License</a> is a permissive license that is short and to the point. It lets people do anything they want with your code as long as they provide attribution back to you and don’t hold you liable.
</p>
<p>
<strong>jQuery</strong> and <strong>Rails</strong> use the MIT License.
</p>
</li>
<li class='patents'>
<a href="licenses/apache"><img height='72' src='images/lightbulb@2x.png' width='43'></a>
<h3><a href="licenses/apache">I’m concerned about patents.</a></h3>
<p>
The <a href="licenses/apache/">Apache License</a> is a permissive license similar to the MIT License, but also provides an express grant of patent rights from contributors to users.
</p>
<p>
<strong>Apache</strong>, <strong>SVN</strong>, and <strong>NuGet</strong> use the Apache License.
</p>
</li>
<li class='copyleft'>
<a href="licenses/gpl-v2"><img height='69' src='images/circular@2x.png' width='72'></a>
<h3><a href="licenses/gpl-v3">I care about sharing improvements.</a></h3>
<p>
The GPL (<a href="licenses/gpl-v2">V2</a> or <a href="licenses/gpl-v3">V3</a>) is a copyleft license that requires others who modify your code to disclose their changes if they redistribute it in source or binary form. V3 is similar to V2, but adds a restriction restricting use in hardware that forbids software alterations.
</p>
<p>
<strong>Linux</strong> and <strong>Git</strong> use the GPL.
</p>
</li>
</ul>
<div class="see-more callout">
<p>What if none of these work for me or I want to retain all of my rights? <a href="licenses">More licenses are available</a>.</p>
<p>What if I don't want to choose a license</a>? <a href="no-license">You don't have to</a>.</p>
</div>
</div>
</body>
</html>
<h2>
<span>{</span>
Which of the following best describes your situation?
<span>}</span>
</h2>
<ul class="situations cf">
<li class='whatever'>
<a href="licenses/mit"><img height='57' src='images/three-arrows@2x.png' width='72'></a>
<h3><a href="licenses/mit">I want it simple and permissive.</a></h3>
<p>
The <a href="licenses/mit">MIT License</a> is a permissive license that is short and to the point. It lets people do anything they want with your code as long as they provide attribution back to you and don’t hold you liable.
</p>
<p>
<strong>jQuery</strong> and <strong>Rails</strong> use the MIT License.
</p>
</li>
<li class='patents'>
<a href="licenses/apache"><img height='72' src='images/lightbulb@2x.png' width='43'></a>
<h3><a href="licenses/apache">I’m concerned about patents.</a></h3>
<p>
The <a href="licenses/apache/">Apache License</a> is a permissive license similar to the MIT License, but also provides an express grant of patent rights from contributors to users.
</p>
<p>
<strong>Apache</strong>, <strong>SVN</strong>, and <strong>NuGet</strong> use the Apache License.
</p>
</li>
<li class='copyleft'>
<a href="licenses/gpl-v2"><img height='69' src='images/circular@2x.png' width='72'></a>
<h3><a href="licenses/gpl-v3">I care about sharing improvements.</a></h3>
<p>
The GPL (<a href="licenses/gpl-v2">V2</a> or <a href="licenses/gpl-v3">V3</a>) is a copyleft license that requires others who modify your code to disclose their changes if they redistribute it in source or binary form. V3 is similar to V2, but adds a restriction restricting use in hardware that forbids software alterations.
</p>
<p>
<strong>Linux</strong> and <strong>Git</strong> use the GPL.
</p>
</li>
</ul>
<div class="see-more callout">
<p>What if none of these work for me or I want to retain all of my rights? <a href="licenses">More licenses are available</a>.</p>
<p>What if I don't want to choose a license</a>? <a href="no-license">You don't have to</a>.</p>
</div>

3
no-license.md
View File

@ -1,10 +1,9 @@
---
layout: default
permalink: no-license/
title: No License
---
# No License
You're under no obligation to choose a license and it's your right not to include one with your code or project. But please note that opting out of open source licenses doesn't mean you're opting out of copyright law.
You'll have to check with your own legal counsel regarding your particular project, but generally speaking, the absence of a license means that 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.