<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>foss &amp;mdash; Matt&#39;s Dev Log</title>
    <link>https://matt.writefreely.dev/tag:foss</link>
    <description></description>
    <pubDate>Sun, 03 May 2026 15:01:41 +0000</pubDate>
    <item>
      <title>Keeping open issues low</title>
      <link>https://matt.writefreely.dev/keeping-open-issues-low</link>
      <description>&lt;![CDATA[I got the number of open issues on WriteFreely down below 10 again today, after reaching its high of 13. After some time maintaining this project, I think keeping this number low is actually kind of important.&#xA;&#xA;We tell everyone that Github is only for reporting bugs, and that we&#39;re very responsive there. Keeping this number low backs this up.&#xA;A low number of issues makes it easy for others to find bugs they might&#39;ve encountered, as well.&#xA;Keeping this number low signals that the project is active and moving forward.&#xA;&#xA;For a #FOSS project like ours, with a strong vision / direction to follow and core developers pushing that forward, I&#39;m finding this setup really works well for us. We gather input on our forum, turn that into long-term plans in Phabricator, and adjust to real world usage on the platform that&#39;s closest to it all, Github.&#xA;&#xA;---&#xD;&#xA;&#xD;&#xA;Get future updates via RSS and ActivityPub: @devlog@matt.writefreely.dev.]]&gt;</description>
      <content:encoded><![CDATA[<p>I got the number of <a href="https://github.com/writeas/writefreely/issues">open issues on WriteFreely</a> down below 10 again today, after reaching its high of 13. After some time maintaining this project, I think keeping this number low is actually kind of important.</p>
<ul><li>We tell everyone that Github is only for reporting bugs, and that we&#39;re very responsive there. Keeping this number low backs this up.</li>
<li>A low number of issues makes it easy for others to find bugs they might&#39;ve encountered, as well.</li>
<li>Keeping this number low signals that the project is active and moving forward.</li></ul>

<p>For a <a href="https://matt.writefreely.dev/tag:FOSS" class="hashtag"><span>#</span><span class="p-category">FOSS</span></a> project like ours, with a strong vision / direction to follow and core developers pushing that forward, I&#39;m finding this setup really works well for us. We gather input on <a href="https://discuss.write.as">our forum</a>, turn that into long-term plans in <a href="https://phabricator.write.as">Phabricator</a>, and adjust to real world usage on the platform that&#39;s closest to it all, Github.</p>

<hr>

<p>Get future updates via <a href="https://matt.writefreely.dev/feed/">RSS</a> and ActivityPub: <a href="https://matt.writefreely.dev/@/devlog@matt.writefreely.dev" class="u-url mention">@<span>devlog@matt.writefreely.dev</span></a>.</p>
]]></content:encoded>
      <guid>https://matt.writefreely.dev/keeping-open-issues-low</guid>
      <pubDate>Mon, 03 Jun 2019 04:05:37 +0000</pubDate>
    </item>
  </channel>
</rss>