commit 7f41a1547a02563f2f2d2906d46837c6ffca2ab1
parent 9e4cc0e2854f196354353a799bbd6d5cc509ed8c
Author: Chris Bracken <chris@bracken.jp>
Date: Wed, 22 Jun 2022 11:51:11 -0700
Publish site
Diffstat:
5 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/2020/05/thoughts-on-licences/index.html b/2020/05/thoughts-on-licences/index.html
@@ -35,11 +35,11 @@
<h2 class="post-title"><a href="https://chris.bracken.jp/2020/05/thoughts-on-licences/">Thoughts on Licences</a></h2>
22 May 2020
<p>Software licences are probably the single most boring aspect of software
-development, but I it’s important to carefully consider the terms under which
-the stuff I hack on is shared to ensure they’re consistent with my values.
-Despite my general dislike for all things legalistic, the most unambiguous way
-to state those terms is through a licence. So a couple days ago, I tossed
-LICENSE files into any of my public <a href="/code">repos</a> that didn’t already have one.</p>
+development, but it’s important to carefully consider the terms under which the
+stuff I hack on is shared to ensure they’re consistent with my values. Despite
+my general dislike for all things legalistic, the most unambiguous way to state
+those terms is through a licence. So a couple days ago, I tossed LICENSE files
+into any of my public <a href="/code">repos</a> that didn’t already have one.</p>
<p>So how did I settle on which licences to apply? Jump on into the DeLorean and
let’s set the dial back to the late 1980s.</p>
<p>It’s 1986 and I’ve got a 1200 baud modem wired up to a beat-up 286 with a steel
diff --git a/index.xml b/index.xml
@@ -13,7 +13,7 @@
<pubDate>Fri, 22 May 2020 14:55:23 -0700</pubDate>
<guid>https://chris.bracken.jp/2020/05/thoughts-on-licences/</guid>
- <description>Software licences are probably the single most boring aspect of software development, but I it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
+ <description>Software licences are probably the single most boring aspect of software development, but it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
</item>
<item>
diff --git a/post/index.xml b/post/index.xml
@@ -13,7 +13,7 @@
<pubDate>Fri, 22 May 2020 14:55:23 -0700</pubDate>
<guid>https://chris.bracken.jp/2020/05/thoughts-on-licences/</guid>
- <description>Software licences are probably the single most boring aspect of software development, but I it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
+ <description>Software licences are probably the single most boring aspect of software development, but it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
</item>
<item>
diff --git a/tags/meta/index.xml b/tags/meta/index.xml
@@ -13,7 +13,7 @@
<pubDate>Fri, 22 May 2020 14:55:23 -0700</pubDate>
<guid>https://chris.bracken.jp/2020/05/thoughts-on-licences/</guid>
- <description>Software licences are probably the single most boring aspect of software development, but I it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
+ <description>Software licences are probably the single most boring aspect of software development, but it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
</item>
<item>
diff --git a/tags/software/index.xml b/tags/software/index.xml
@@ -13,7 +13,7 @@
<pubDate>Fri, 22 May 2020 14:55:23 -0700</pubDate>
<guid>https://chris.bracken.jp/2020/05/thoughts-on-licences/</guid>
- <description>Software licences are probably the single most boring aspect of software development, but I it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
+ <description>Software licences are probably the single most boring aspect of software development, but it&rsquo;s important to carefully consider the terms under which the stuff I hack on is shared to ensure they&rsquo;re consistent with my values. Despite my general dislike for all things legalistic, the most unambiguous way to state those terms is through a licence. So a couple days ago, I tossed LICENSE files into any of my public repos that didn&rsquo;t already have one.</description>
</item>
<item>
