Lowering the Maintenance burden of open source projects

<p> Assuming that attention from a producer is a non-excludable, rivalrous good <sup id="fnref:1"> <a class="footnote-ref" href="#fn:1"> 1 </a> </sup> , projects must implement methods to optimize the use of the available attention. Some possibilities are:[ <a class="litnote tooltip" href="/literature/@eghbal2020"> @eghbal2020 <span class="tooltiptext"> Working in public: the making and maintenance of open source software </span> </a> ] </p> <ul> <li> Automation: Continuous Integration, Bots </li> <li> Clear guidelines: Templates, code style, linters </li> <li> Limiting available attention (for example not accepting pull-requests) </li> <li> Distributing costs: creating user-supported forums (see: <a class="wikilink" href="/the_interaction_between_stackoverflow_and_github/"> The interaction between Stackoverflow and Github </a> ) </li> <li> Increase available attention: see <a class="wikilink" href="/the_role_of_money_in_open_source/"> the role of money in open source </a> </li> </ul> <div class="footnote"> <hr/> <ol> <li id="fn:1"> <p> https://en.wikipedia.org/wiki/Excludability <a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text"> ↩ </a> </p> </li> </ol> </div>