Skip to content

Clarify that being a core developer means ongoing work on a core package #367

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
Zethson merged 1 commit into from
Oct 22, 2026
Merged

Clarify that being a core developer means ongoing work on a core package #367

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: 2 additions & 1 deletion content/about/roles/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,8 @@ There are sub-roles within the core team covering different kinds of contributio

#### Core Developers

Core developers are members of the core team who have made significant code contributions to scverse.
Core developers are members of the core team who maintain or continuously contribute to at least one core package.
Being a core developer is about this ongoing work rather than a one-off contribution, so the way to become one is to get involved in a core package over time: reviewing pull requests, fixing issues and helping with releases alongside its maintainers.
They are granted additional rights so they can more easily carry on with their scverse related activities.
These rights include: merging approved pull requests, voting for and against contested pull-requests, and being involved in deciding major changes to the API.
Core developers are on our `scverse/core-devs` GitHub team.
Expand Down
Loading