<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Open Source on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/open-source/</link>
    <description>Recent content in Open Source on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/open-source/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bootstrapping Launches as Open Source Seed Data Reconciler for SQLite</title>
      <link>https://bootstrapping.org/bootstrapping-launches-as-open-source-seed-data-reconciler-for-sqlite/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/bootstrapping-launches-as-open-source-seed-data-reconciler-for-sqlite/</guid>
      <description>&lt;p&gt;Bootstrapping 0.1 is out, open source under the Apache License 2.0. It keeps the reference data an application ships with, roles, permissions, plan tiers and the like, in step with its SQLite database on every release, without undoing what admins changed. The code is on &lt;a href=&#34;https://github.com/bootstrapping-engine/bootstrapping&#34;&gt;GitHub&lt;/a&gt;, and ready-built binaries for Linux, macOS and Windows are on the &lt;a href=&#34;https://bootstrapping.org/download/&#34;&gt;download page&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;It works by remembering. A small ledger in the database records what each apply wrote, so the next apply can compare every value three ways: the new seed, the live row and what was last applied. Values only the seed changed get updated. Values only an admin changed stay. Values both changed differently stop the apply until someone decides. The &lt;a href=&#34;https://bootstrapping.org/three-way-merge-for-seed-data-keeps-admin-edits-through-every-upgrade/&#34;&gt;explainer&lt;/a&gt; goes through why that third version is the whole trick.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
