About maintenance
This post sets some clear expectations regarding projects I develop and maintain.
Let's call it Commitment Pledge.
In short, I don't abandon shit easily and appreciate people's trust.
Lifecycle & Exit Policy
Transparent Status
The repository will clearly display its maintenance state via standard badges (e.g., "Maintained", "Archived", "Open For Adoption", "Sundown").
Graceful Exit
If I reach burnout, lose interest, or can no longer maintain the codebase, the project will not be silently abandoned. I will update the project's lifecycle badge to "Sundown" or "Open For Adoption" and post instructions about forking or hand-off with at least a month of advance warning.
Deadman Switch
If a man or an animal or a huge meteor gets the best of me and I become dead, designated person will deal with inheritance and hand-offs.
Integrity, security, privacy
No Protestware or Sabotage
Code updates will strictly serve the project's stated technical function. I will never intentionally inject malware, protestware, console activism, political popups, or code designed to break environments. Although, I will openly and transparently make your life harder if you support evil shit.
No Unsolicited Telemetry
I will not include tracking, phone-home features, user profiling, or analytics without explicit, transparent, opt-in consent. Not sure if I do it even with consent.
No Relicensing Rug-Pulls
Published releases will remain open source. Future releases will not be retroactively switched to restrictive, commercial, or non-OSI-approved source-available licenses.
No Package Deletions
Published releases or package registry artifacts will not be arbitrarily deleted or yanked, preventing broken downstream builds, except when required for critical security or legal reasons.
Transparent Stewardship Transfers
Administrative control, repo ownership, and package-publishing keys will never be sold or handed off to unverified third parties. Any transfer of maintainership will be publicly announced and verified.
Obvious
Right to Refuse
I reserve the right to decline features, code contributions, or pull requests that do not align with the project’s scope, design philosophy, or maintenance bandwidth.
No Obligation of Service
Maintenance is conducted on a best-effort basis; I am not an on-call support team or corporate service desk (but we can discuss it)
I do it because I like making and sharing stuff I find useful.