commit 223c1a9517982057d4395fc06d5a016655aef5e7
parent 9faf6e432279ed78e95140eba31f8651519315a1
Author: Chris Bracken <chris@bracken.jp>
Date: Wed, 22 Jun 2022 09:48:21 -0700
Publish site
Diffstat:
4 files changed, 5 insertions(+), 5 deletions(-)
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>I don&rsquo;t pretend to think that the things I create have a whole ton of value, but I do think it&rsquo;s important to carefully consider the terms under which they&rsquo;re 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 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>
</item>
<item>
@@ -642,7 +642,7 @@ I&rsquo;m a software developer who&rsquo;s been fascinated by computers
<guid>https://chris.bracken.jp/code/</guid>
<description>You can find most of the public code I contribute to hosted at one of the following sites:
- git.bracken.jp: My self-hosted git repos. GitHub: The most popular source code hosting solution and where most of my public contributions lie. GitLab: Better features and UI than GitHub. Significant contributions Flutter: portable, cross-platform app SDK and runtime. Most of my contributions focus on the portable C++ runtime, the platform-specific embedders, and tools.</description>
+git.bracken.jp: My self-hosted git repos. GitHub: The most popular source code hosting solution and where most of my public contributions lie. GitLab: Better features and UI than GitHub. Significant contributions Flutter: portable, cross-platform app SDK and runtime. Most of my contributions focus on the portable C++ runtime, the platform-specific embedders, and tools. Dart SDK/VM: the Dart programming language is a strongly-typed, object-oriented, garbage-collected language with C-like syntax.</description>
</item>
</channel>
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>I don&rsquo;t pretend to think that the things I create have a whole ton of value, but I do think it&rsquo;s important to carefully consider the terms under which they&rsquo;re 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 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>
</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>I don&rsquo;t pretend to think that the things I create have a whole ton of value, but I do think it&rsquo;s important to carefully consider the terms under which they&rsquo;re 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 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>
</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>I don&rsquo;t pretend to think that the things I create have a whole ton of value, but I do think it&rsquo;s important to carefully consider the terms under which they&rsquo;re 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 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>
</item>
<item>
