docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-12-22 12:50:24 +01:00
Code Issues Releases Wiki Activity

First cut at a landing page

Browse Source 
This is a VERY ROUGH take on the landing page. The basic idea is we want
to present 3 licenses on the home page and just enough info for people
to choose one of the three. But we'll provide links for folks who need
to dig deeper and choose a license that better fits their needs.

The design right now is blatantly stolen from KOD. But that's just to
make the early draft look pretty. That's not the intended final design.
This commit is contained in:
Haacked 2012-06-08 17:19:25 +02:00
parent 5dac78ac96
commit cc1b3167b9
4 changed files with 584 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

511
css/style.css Normal file
View File

File diff suppressed because one or more lines are too long

BIN
favicon.ico Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BIN
images/bg-kod.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 30 KiB

73
index.html Normal file
View File

@ -0,0 +1,73 @@
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<!-- Always force latest IE rendering engine (even in intranet) & Chrome Frame -->
<meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible">
<title>KING of Developers</title>
<link href="css/style.css" rel="stylesheet">
<script type="text/javascript" src="https://use.typekit.com/weh4icd.js"></script>
<script type="text/javascript">try{Typekit.load();}catch(e){}</script>
</head>
<body class="cal">
<div class="get-started">
<h1>
So you want to choose an OSS license.
<strong>Now what?</strong>
</h1>
<p>
<strong>This doesn't need to be scary.</strong>
We compiled a list of three licenses that address what most projects need.
You can pick on of these and be on your way, or click the links to dig deeper
into picking a license that meets your unique needs.
</p>
<h2>
<strong>Ready? Which of the following describes you?</strong>
<h3 class="big-intro-link">Do whatever with my code</h3>
<p>
<a href="#mit">The MIT license</a> is a permissive license that is short and to the point.
It lets people do anything with your code with two main stipulations:
</p>
<ul>
<li>- Include proper attribution</li>
<li>- The code is provided without warranty of any kind</li>
</ul>
<p>
<a href="">More like this...</a>
<strong class="projects">Projects that use this: jQuery, Rails</strong>
</p>
</h2>
<h2>
<h3 class="big-intro-link">I&#8217;m concerned about patents</h3>
<p>
<a href="#mit">The Apache license</a> is a permissive license similar to the MIT License,
but it provides a patent license for any code that infringes on a contributor&#8217;s patents.
</p>
<p>
<a href="">More like this...</a>
<strong class="projects">Projects that use this: Apache, SVN, NuGet</strong>
</p>
</h2>
<h2>
<h3 class="big-intro-link">You care about reciprocity</h3>
<p>
The GPL (<a href="#v2">v2</a> or <a href="#v3">v3</a>) requires that folks who modify your
code also license their changes under the GPL. V3 is similar to v2, but adds a restriction
that doesn&#8217;st allow using the software in hardware that doesn&#8217;t allow modifying
the software.
</p>
<p>
<a href="">More like this...</a>
<strong class="projects">Projects that use this: Linux, Git</strong>
</p>
</h2>
</div>
</body>
</html>