<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Authors on SOW</title>
    <link>https://sow.pgsty.com/authors/</link>
    <description>Recent content in Authors on SOW</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Fri, 28 Aug 2026 18:32:04 +0800</lastBuildDate>
    
    
      <atom:link href="https://sow.pgsty.com/authors/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Ruohang Feng</title>
        <link>https://sow.pgsty.com/authors/vonng/</link>
        <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
        
        <guid>https://sow.pgsty.com/authors/vonng/</guid>
        <description>&lt;p&gt;Ruohang Feng (&lt;a href=&#34;https://github.com/Vonng&#34;&gt;@Vonng&lt;/a&gt;) writes &lt;strong&gt;SOW&lt;/strong&gt; and&#xA;&lt;a href=&#34;https://pigsty.io/&#34;&gt;Pigsty&lt;/a&gt;, the PostgreSQL distribution it builds repositories for.&lt;/p&gt;&#xA;&lt;p&gt;SOW started from a delivery problem rather than a packaging one. Pigsty ships&#xA;hundreds of RPM and DEB packages across Enterprise Linux, Debian, and Ubuntu, and&#xA;the honest answer to &lt;em&gt;what exactly is in the repository right now, and who put it&#xA;there&lt;/em&gt; was a directory listing and a shell history. Making membership, immutable&#xA;generations, signing, and publication explicit turned that answer into state that a&#xA;tool can show you — and turned a repository rebuild into an auditable release&#xA;boundary instead of a batch of files that appeared overnight.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
