<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Asterix Project</title>
  <link>https://asterixproject.tech/</link>
  <description>Open-source infrastructure, built in the open.</description>
  <language>en</language>
  <lastBuildDate>Thu, 22 Oct 2026 08:03:48 GMT</lastBuildDate>
  <atom:link href="https://asterixproject.tech/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Inside the Machine: Six Weeks of Release Engineering Behind Asterix v3.0</title>
    <link>https://asterixproject.tech/inside-the-machine-asterix-v3-release-engineering/</link>
    <guid isPermaLink="true">https://asterixproject.tech/inside-the-machine-asterix-v3-release-engineering/</guid>
    <description>Shipping a major version of an open-source project is less a launch and more a controlled demolition. Here&#039;s the full, unvarnished timeline of how Asterix v3.0 went from a contentious RFC to a signed release tag — and what your team can steal from our pipeline.</description>
    <author>Asterix Project</author>
    <category>Release Engineering</category>
    <pubDate>Thu, 22 Oct 2026 08:03:48 GMT</pubDate>
  </item>
  <item>
    <title>Your README Is an Airlock: Seven Ways Projects Suffocate New Contributors</title>
    <link>https://asterixproject.tech/readme-airlock-seven-contributor-repelling-anti-patterns/</link>
    <guid isPermaLink="true">https://asterixproject.tech/readme-airlock-seven-contributor-repelling-anti-patterns/</guid>
    <description>A README is the airlock between the outside world and your codebase — and most projects weld it shut. We reviewed hundreds of open-source repositories to identify the seven documentation failures that quietly drive contributors away, with before-and-after fixes for each.</description>
    <author>Asterix Project</author>
    <category>Developer Experience</category>
    <pubDate>Thu, 22 Oct 2026 08:03:48 GMT</pubDate>
  </item>
</channel>
</rss>