# Maintenance and responsibility

2018-10-08

> To distill a maintainer’s responsibilities into core facets, I have borrowed from Asimov’s Three Laws. Perhaps it feels like a dramatic summary of the rather mundane task of pushing to a public git remote. But if you feel that way, I’ve likely already lost you. That’s fine. These laws have my name on them, not yours.

> 1. A maintainer may not harm a user or, through inaction, allow users to come to harm
> 2. A maintainer must shepherd their project and empower the community to do the same
> 3. A maintainer must protect their own existence as long as such protection does not conflict with the First or Second Laws

> I, Maintainer (cache)

Something to remember before pushing the first lines of open-source code out there.

Been there, felt that.

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.