<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>None on Your License</title><link>https://pick.yourlicense.ca/copyleft/none/</link><description>Recent content in None on Your License</description><generator>Hugo</generator><language>en-ca</language><atom:link href="https://pick.yourlicense.ca/copyleft/none/index.xml" rel="self" type="application/rss+xml"/><item><title>Apache License 2.0</title><link>https://pick.yourlicense.ca/licenses/apache-2.0/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pick.yourlicense.ca/licenses/apache-2.0/</guid><description>&lt;p&gt;Apache 2.0 is a permissive license similar in spirit to MIT but with two key additions: an explicit patent grant from contributors, and an explicit requirement to document significant changes. It does not grant trademark rights.&lt;/p&gt;
&lt;p&gt;The patent grant makes Apache 2.0 preferable for projects with many contributors or corporate sponsors — it reduces the risk of patent lawsuits against downstream users. Apache 2.0 is not compatible with GPL-2.0, but is compatible with GPL-3.0 and later.&lt;/p&gt;</description></item><item><title>BSD 3-Clause License</title><link>https://pick.yourlicense.ca/licenses/bsd-3-clause/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pick.yourlicense.ca/licenses/bsd-3-clause/</guid><description>&lt;p&gt;BSD 3-Clause is a short, permissive license that adds one constraint MIT does not: you cannot use the names of the original authors or contributors to endorse or promote products derived from the software without specific written permission.&lt;/p&gt;
&lt;p&gt;In practice, the rules are nearly identical to MIT. Choose BSD-3-Clause if the no-endorsement clause is important to you or your project has historical BSD heritage.&lt;/p&gt;
&lt;h2 id="how-to-apply"&gt;How to apply&lt;/h2&gt;
&lt;p&gt;Add a &lt;code&gt;LICENSE&lt;/code&gt; file with the full BSD 3-Clause text at the root of your project, filling in the copyright owner and year. Per-file SPDX headers are optional but common:&lt;/p&gt;</description></item><item><title>Creative Commons Attribution 4.0</title><link>https://pick.yourlicense.ca/licenses/cc-by-4.0/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pick.yourlicense.ca/licenses/cc-by-4.0/</guid><description>&lt;p&gt;CC BY 4.0 is Creative Commons&amp;rsquo; most permissive licence that still requires attribution. Anyone may share, remix, adapt, and build on the material for any purpose, including commercial, provided they give appropriate credit, link to the licence, and indicate if changes were made.&lt;/p&gt;
&lt;p&gt;It is a good default for text, images, video, and datasets when you want the widest possible reuse but still want recognition. For pure databases in the EU, ODbL-1.0 addresses sui generis rights CC BY does not fully cover.&lt;/p&gt;</description></item><item><title>ISC License</title><link>https://pick.yourlicense.ca/licenses/isc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pick.yourlicense.ca/licenses/isc/</guid><description>&lt;p&gt;ISC is a permissive license produced by the Internet Systems Consortium. It is functionally identical to the simplified BSD license and the MIT license — use, modify, distribute, include the copyright notice — but uses even fewer words.&lt;/p&gt;
&lt;p&gt;It is npm&amp;rsquo;s default license for new packages, which is why you&amp;rsquo;ll see it on a lot of small JavaScript libraries.&lt;/p&gt;
&lt;h2 id="how-to-apply"&gt;How to apply&lt;/h2&gt;
&lt;p&gt;Add a &lt;code&gt;LICENSE&lt;/code&gt; file with the full ISC text, filling in the copyright year and holder. Per-file headers are optional but many projects add:&lt;/p&gt;</description></item><item><title>MIT License</title><link>https://pick.yourlicense.ca/licenses/mit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pick.yourlicense.ca/licenses/mit/</guid><description>&lt;p&gt;The MIT License is one of the shortest and most permissive open-source licenses. It lets anyone use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software, provided they include the original copyright notice and license text.&lt;/p&gt;
&lt;p&gt;It is a good default for libraries and frameworks you want adopted as widely as possible. If you care about protecting against patent claims from contributors, consider Apache-2.0 instead — the patent grant is the main difference.&lt;/p&gt;</description></item></channel></rss>