Lowering the Maintenance burden of open source projects

First published: 2024-01-27

Last Edited: 2021-03-14

Number of edits: 10

Assuming that attention from a producer is a non-excludable, rivalrous good ¹ , projects must implement methods to optimize the use of the available attention. Some possibilities are:[ @eghbal2020 Working in public: the making and maintenance of open source software ]

Automation: Continuous Integration, Bots
Clear guidelines: Templates, code style, linters
Limiting available attention (for example not accepting pull-requests)
Distributing costs: creating user-supported forums (see: The interaction between Stackoverflow and Github )
Increase available attention: see the role of money in open source

https://en.wikipedia.org/wiki/Excludability ↩

Backlinks

These are the other notes that link to this one.

Freeing short term memory

Maintenance costs of open source projects

Notes on Working in Public - Nadia Eghbal

Comment

Share your thoughts on this note

Aquiles Carattino

This note you are reading is part of my digital garden. Follow the links to learn more, and remember that these notes evolve over time. After all, this website is not a blog.