Skip to content
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.

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

chore: move @nissy-dev to past maintainer #2785

Merged
merged 1 commit into from
May 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 6 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -418,7 +418,6 @@ Members are listed in alphabetical order. Members are free to use the full name,
### Core Contributors team

- [Arend van Beelen @arendjr](https://github.com/arendjr)
- [Daiki Nishikawa @nissy-dev](https://github.com/nissy-dev)
- [Denis Bezrukov @denbezrukov](https://github.com/denbezrukov)
- [Hiroki Ihoriya @unvalley](https://github.com/unvalley)
- [Jon Egeland @faultyserver](https://github.com/faultyserver)
Expand All @@ -435,3 +434,9 @@ Members are listed in alphabetical order. Members are free to use the full name,
- [Yoshiaki Togami @togami2864](https://github.com/togami2864)
- [Ze-Zheng Wu @Sec-ant](https://github.com/Sec-ant)
- [Zheyu Zhang @ah-yu](https://github.com/ah-yu)

### Past Maintainers

- [Daiki Nishikawa @nissy-dev](https://github.com/nissy-dev) (Core contributor)


4 changes: 2 additions & 2 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ One or more people can own certain parts of the codebase. This process is inform

There aren't strict requirements and expectations around activity for core contributors and maintainers; although long periods of inactivity must be communicated to the team.

Inactive core contributors or maintainers may have voting and access rights removed and status removed, and given them the _Past contributor_ status. A core contributor or maintainer may request their voting rights and status back upon sufficient activity.
Inactive core contributors or maintainers may have voting and access rights removed and status removed, and given them the _Past maintainer_ status. A core contributor or maintainer may request their voting rights and status back upon sufficient activity.

> [!NOTE]
> The definition of "long periods", and how long an individual needs to stay inactive in order to have their voting rights removed have yet to be decided.
Expand Down Expand Up @@ -195,7 +195,7 @@ Bounties are the second approach towards funding Biome development. Unlike a spo
- The commission charged by Polar.sh is split accordingly.
- We reserve the right to decide on a different split in the future.
- Bounties cannot be opened for bug fixes. Users who wish to see bugs fixed are advised to consider [sponsorship](#sponsorship) instead, in order to give the project a better long-term ability to fix bugs as well.
- If an issue in our issue tracker is not yet open for pledges, the person who wishes to pledge should indicate their desire in the comments of the issue, or do so through the `Community > #funding` channel on Discord. A [Core Contributor](#core-contributor) can then **accept** or **reject** the request for the bounty. Reasons for rejection include, but are not limited to:
- If an issue in our issue tracker is not yet open for pledges, the person who wishes to pledge should indicate their desire in the comments of the issue, or do so through the `Community > #funding` channel on Discord. A [Core Contributor](#core-contributor) can then **accept** or **reject** the request for the bounty. Reasons for rejection include, but are not limited to:
- Implementation of the task would conflict with the project direction or [its values](https://biomejs.dev/internals/philosophy/).
- Implementation of the task is (currently) technically infeasible.
- The suggested pledge is deemed inappropriate for the amount of work involved.
Expand Down