Skip to content

governance: no successor line #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
finom merged 1 commit into from
Oct 17, 2026
Merged

governance: no successor line #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,9 @@ Matreshka.js has one maintainer, [Andrey Gubanov](https://github.com/finom), who

## Continuity

The project can go on if the maintainer can't:
If the maintainer can't go on:

- The code, the issues, the docs, the docs deploy and the release workflow all live in this GitHub repository; nothing is kept on the maintainer's machine. Releases publish to npm from the repository's workflow (trusted publishing), with no npm token to hand over.
- The maintainer's GitHub account has a designated [account successor](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/maintaining-ownership-continuity-of-your-personal-accounts-repositories), who can archive the repository or transfer it to a new maintainer.
- The license is MIT: anyone can fork the project and go on.

The bus factor is 1: there is one maintainer.
Loading