<story><title>Exa Is Deprecated</title><url>https://github.com/ogham/exa</url></story><parent_chain><item><author>boxed</author><text>I wish there was a better way for the community to handle this situation without the original author doing what we see here. Sometimes the original author dies unexpectedly for example and it&amp;#x27;s very hard to salvage the work into a maintained fork.&lt;p&gt;I wrote about this in 2018: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;kodare.net&amp;#x2F;2018&amp;#x2F;06&amp;#x2F;25&amp;#x2F;salvaging-abandoned-projects.html&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;kodare.net&amp;#x2F;2018&amp;#x2F;06&amp;#x2F;25&amp;#x2F;salvaging-abandoned-projects.h...&lt;/a&gt;</text></item><item><author>goku12</author><text>I hope that the author Benjamin Sago is alright. It&amp;#x27;s always concerning when FOSS developers disappear for a while - even though it isn&amp;#x27;t uncommon.</text></item></parent_chain><comment><author>nikeee</author><text>You can set a successor in your GitHub settings:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.github.com&amp;#x2F;github&amp;#x2F;setting-up-and-managing-your-github-user-account&amp;#x2F;maintaining-ownership-continuity-of-your-user-accounts-repositories&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.github.com&amp;#x2F;github&amp;#x2F;setting-up-and-managing-your-...&lt;/a&gt;&lt;p&gt;That successor will gain access to the _public_ repos of your account after presenting a death certificate. As it&amp;#x27;s only for public repositories, it&amp;#x27;s a no-brainer for me.</text></comment>
<story><title>Exa Is Deprecated</title><url>https://github.com/ogham/exa</url></story><parent_chain><item><author>boxed</author><text>I wish there was a better way for the community to handle this situation without the original author doing what we see here. Sometimes the original author dies unexpectedly for example and it&amp;#x27;s very hard to salvage the work into a maintained fork.&lt;p&gt;I wrote about this in 2018: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;kodare.net&amp;#x2F;2018&amp;#x2F;06&amp;#x2F;25&amp;#x2F;salvaging-abandoned-projects.html&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;kodare.net&amp;#x2F;2018&amp;#x2F;06&amp;#x2F;25&amp;#x2F;salvaging-abandoned-projects.h...&lt;/a&gt;</text></item><item><author>goku12</author><text>I hope that the author Benjamin Sago is alright. It&amp;#x27;s always concerning when FOSS developers disappear for a while - even though it isn&amp;#x27;t uncommon.</text></item></parent_chain><comment><author>dale_glass</author><text>We&amp;#x27;ve started a non-profit to deal with such issues. It&amp;#x27;s a lot of work, but well worthwhile in the long term because part of the process is clarifying such issues, and the organization keeps on existing regardless of any individual member.&lt;p&gt;Still, even this situation is much better than what we had before. It&amp;#x27;s on github and so the project doesn&amp;#x27;t randomly vanish from existence when the owner isn&amp;#x27;t there to maintain the machine in their closet anymore. Contributors see each other and can realize &amp;quot;Hey, maintainer isn&amp;#x27;t active anymore but there&amp;#x27;s still interest in the project, maybe we should do something about this&amp;quot;.</text></comment>