logo

blog

My website can't be that messy, right? git clone https://anongit.hacktivis.me/git/blog.git/

license-pick.shtml (3849B)

    

  1. <!DOCTYPE html>
  2. <html xmlns="http://www.w3.org/1999/xhtml">
  3. 	<head>
  4. <!--#include file="/templates/head.shtml" -->
  5. 		<title>Picking a License — lanodan’s cyber-home</title>
  6. 	</head>
  7. 	<body>
  8. <!--#include file="/templates/en/nav.shtml" -->
  9. 	<main>
  10. 		<h1>Picking a License</h1>
  11. 		<p>Largely copied from: <a href="gemini://drewdevault.com/2021/05/20/How-I-choose-a-license.gmi">Drew DeVault - How I choose a license</a></p>
  12. 		<p>Similarly: "This is how I choose a license for a new project. It is a reflection of my values and priorities and may not work for your needs."</p>
  14. 		<section id="matters">
  15. 			<h2>matters</h2>
  16. 			<dd>
  17. 				<p>Does it matters at all? Is it even copyrightable? (ie. simple observations without originality)</p>
  18. 				<dl>
  19. 					<dt>Yes</dt><dd><a href="#software">Go to: software</a></dd>
  20. 					<dt>No</dt><dd>Use CC0</dd>
  21. 				</dl>
  22. 				<p>Note: CC0 is one of the rare licences that trully waives as much copyrights as possible, even in jurisdictions where Public Domain cannot simply be assigned to (like in Europe).</p>
  23. 			</dd>
  24. 		</section>
  26. 		<section id="software">
  27. 			<h2>software</h2>
  28. 			<dd>
  29. 				<p>Is it software?</p>
  30. 				<dl>
  31. 					<dt>Yes</dt><dd><a href="#ubiquitous">Go to: ubiquitous</a></dd>
  32. 					<dt>No</dt><dd><a href="#creative">Go to: creative</a></dd>
  33. 				</dl>
  34. 			</dd>
  35. 		</section>
  37. 		<section id="creative">
  38. 			<h2>creative</h2>
  39. 			<dd>
  40. 				<p>See <a href="https://creativecommons.org/choose/">Creative Commons - Choose a License</a>, incomplete version below</p>
  41. 				<p>Do you want it to become ubiquitous, where anyone, including corporations, governments, literally anyone, would have no reservations about using it for any use-case, including making proprietary derivatives and selling them, or reusing the code in another project, proprietary or not?</p>
  42. 				<dl>
  43. 					<dt>Yes</dt><dd>Use CC-BY-4.0</dd>
  44. 					<dt>No, libre-only</dt><dd>Use CC-BY-SA-4.0</dd>
  45. 					<dt>No, non-commercial</dt><dd>Use CC-BY-NC-SA-4.0</dd>
  46. 				</dl>
  47. 			</dd>
  48. 		</section>
  50. 		<section id="ubiquitous">
  51. 			<h2>ubiquitous</h2>
  52. 			<dd>
  53. 				<p>Do you want it to become ubiquitous, where anyone, including corporations, governments, literally anyone, would have no reservations about using it for any use-case, including making proprietary derivatives and selling them, or reusing the code in another project, proprietary or not?</p>
  54. 				<dl>
  55. 					<dt>Yes</dt><dd><a href="#patents">Go to: patents</a></dd>
  56. 					<dt>No</dt><dd><a href="#service">Go to: service</a></dd>
  57. 				</dl>
  58. 			</dd>
  59. 		</section>
  61. 		<section id="patents">
  62. 			<h2>patents</h2>
  63. 			<dd>
  64. 				<p>Is the copyright owned by a company who might have trademarks and patents and other such garbage?</p>
  65. 				<dl>
  66. 					<dt>Yes</dt><dd>Use Apache 2.0</dd>
  67. 					<dt>No</dt><dd>Use MIT or BSD</dd>
  68. 				</dl>
  69. 			</dd>
  70. 		</section>
  72. 		<section id="service">
  73. 			<h2>service</h2>
  74. 			<dd>
  75. 				<p>Is it a networked service or similar software not entirely running directly on the user's machine?</p>
  76. 				<dl>
  77. 					<dt>Yes</dt><dd>Use AGPLv3</dd>
  78. 					<dt>No</dt><dd><a href="#library">Go to: library</a></dd>
  79. 				</dl>
  80. 			</dd>
  81. 		</section>
  83. 		<section id="library">
  84. 			<h2>library</h2>
  85. 			<dd>
  86. 				<p>Is it a library?</p>
  87. 				<dl>
  88. 					<dt>Yes</dt><dd><a href="#vendoring">Go to: vendoring</a></dd>
  89. 					<dt>No</dt><dd>Use <code>GPL-2.0-only OR GPL-3.0-only</code> (because of incompatibilities between both…)</dd>
  90. 				</dl>
  91. 			</dd>
  92. 		</section>
  94. 		<section id="vendoring">
  95. 			<h2>vendoring</h2>
  96. 			<dd>
  97. 				<p>Do you want users to be able to vendor it (copy it into their code), or should they be required to install it and link to it to use it without the viral obligation?</p>
  98. 				<dl>
  99. 					<dt>Yes</dt><dd>Use MPL 2.0</dd>
  100. 					<dt>No</dt><dd>Use LGPLv3</dd>
  101. 				</dl>
  102. 			</dd>
  103. 		</section>
  104. 	</main>
  105. <!--#include file="/templates/en/footer.shtml" -->
  106. 	</body>
  107. </html>