docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-11-05 03:08:51 +01:00
Code Issues Releases Wiki Activity

non-software licenses page

Browse Source 
building on https://github.com/github/choosealicense.com/pull/307

non-software rather than non-code because software is eating the
world, the main topic is open source software, and I find
software/non-software slighly less trying than code/non-code if
only because it isn't a
[thing](http://www.adamhyde.net/perhaps-stop-using-non-code-whatayarekin/).

tweak text of page, also addressing #261 and #313
This commit is contained in:
Mike Linksvayer 2016-02-26 12:34:20 -08:00
parent 6df14f2d42
commit 2d4c4a63bd
3 changed files with 17 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
index.html
View File

@ -56,9 +56,9 @@ permalink: /
</h2>
<ul class="triptych see-more clearfix">
<li>
<h3>My project isn’t code.</h3>
<h3>My project isn’t software.</h3>
<p>
<a href="non-code">There are licenses for that</a>.
<a href="non-software">There are licenses for that</a>.
</p>
</li>
<li>

9
non-code.md
View File

@ -1,9 +0,0 @@
---
title: Non-Code
layout: default
permalink: /non-code/
---
While the focus of this site is open source software, there are other licenses more appropriate for projects that aren't code, e.g. [CC0](/licenses/cc0-1.0/) and the [Open Font License](/licenses/ofl-1.1/).
If your project contains a mix of software and content, you can include multiple licenses, as long as you are explicit about which license applies to what segments of the project. See [the license disclaimer for this site](https://github.com/github/choosealicense.com#license) as an example.

15
non-software.md Normal file
View File

@ -0,0 +1,15 @@
---
title: Non-Software Licenses
layout: default
permalink: /non-software/
---
Open source software licenses can be used for non-software works, and often are the best choice. This is particularly the case when the works in question can be edited and versioned as source, e.g., **[open source hardware](http://www.oshwa.org/definition/) designs**. Choose an [open source software license](/licenses/).
[CC0-1.0](/licenses/cc0-1.0/), [CC-BY-4.0](/licenses/cc-by-4.0/), and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are [open](http://opendefinition.org) licenses used for **non-software material ranging from datasets to videos**. Note that Creative Commons licenses should [not be used for software](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software.).
Any open source software license or open Creative Commons license is applicable to **software documentation**. If you use different licenses for your software and its documentation, you may wish to take care that the licenses are compatible, or that source code examples in the documentation is also licensed under the software license.
**Fonts** are software, but are a special case due to how they are used in other works. [SIL Open Font License 1.1](/licenses/ofl-1.1/) accounts for this.
If your project contains a **mix of software and other material**, you can include multiple licenses, as long as you are explicit about which license applies to what parts of the project. See [the license notice for this site](https://github.com/github/choosealicense.com#license) as an example.