From ea6c8ee9121ecdeb3dc387e7e3525a11d91ba152 Mon Sep 17 00:00:00 2001 From: Lukas Heumos Date: Sun, 23 Aug 2026 22:00:51 +0200 Subject: [PATCH 1/4] Point the core team link at the people page GitHub has no public view of a team, so the two team links on the roles page dropped visitors on a sign-in screen. The team names stay as plain text and the core team now links to the people page, which is the public list; team headings there gained anchors so it can be deep-linked. Core developers have no section on the people page, so that mention is left unlinked. Closes #177 Signed-off-by: Lukas Heumos --- content/about/roles/_index.md | 5 +++-- layouts/people/list.html | 4 ++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/content/about/roles/_index.md b/content/about/roles/_index.md index 038b1d7c..5ec0d75e 100644 --- a/content/about/roles/_index.md +++ b/content/about/roles/_index.md @@ -46,7 +46,8 @@ This includes who gets commit rights to their projects. The core team are community members who have demonstrated continued commitment to the project through ongoing contributions. They have shown they can be trusted to maintain scverse with care. -Team members appear as organization members on the scverse [GitHub organization](https://github.com/orgs/scverse/people) and are on our [@scverse/core](https://github.com/orgs/scverse/teams/core) GitHub team, but can also be reached by e-mail at [core@scverse.org](core@scverse.org). +Team members appear as organization members on the scverse [GitHub organization](https://github.com/orgs/scverse/people) and are on our `scverse/core` GitHub team. +The current members are listed on our [people page](/people/#core-team), and the team can be reached by e-mail at [core@scverse.org](mailto:core@scverse.org). There are sub-roles within the core team depending on the kinds covering different kinds of contributions and responsibilities. @@ -55,7 +56,7 @@ There are sub-roles within the core team depending on the kinds covering differe Core developers are members of the core team who have made significant code contributions to scverse. 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](https://github.com/orgs/scverse/teams/core-devs) GitHub team. +Core developers are on our `scverse/core-devs` GitHub team. All core packages must have at least one core developer as a maintainer. New core developers can be nominated by any existing core developer. diff --git a/layouts/people/list.html b/layouts/people/list.html index 176896b6..e19ce5f1 100644 --- a/layouts/people/list.html +++ b/layouts/people/list.html @@ -9,7 +9,7 @@

{{ .Title }}

{{ range $team := .Params.teams }} {{ if not $team.hide }}
-

{{ $team.name }}

+

{{ $team.name }}

{{ if $team.text }}

{{ $team.text | safeHTML }} @@ -46,7 +46,7 @@

{{ $team.name }}

{{ end }} {{ with .Params.contributors }}
-

{{ .name }}

+

{{ .name }}

{{ if .text }}

{{ .text | safeHTML }} From 158f429dbd5ac6158ee694b56529058007af9c0a Mon Sep 17 00:00:00 2001 From: Lukas Heumos Date: Sun, 23 Aug 2026 22:00:51 +0200 Subject: [PATCH 2/4] Add the missing mailto: prefix on the join page The three e-mail links resolved relative to /join/, so clicking one landed on a 404 instead of opening a mail client. Signed-off-by: Lukas Heumos --- content/join/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/join/_index.md b/content/join/_index.md index 87382f3f..df784992 100644 --- a/content/join/_index.md +++ b/content/join/_index.md @@ -40,6 +40,6 @@ title = "Join scverse" You can also reach us by e-mail for certain matters: -- [core@scverse.org](core@scverse.org): [core team](/about/roles#core-team) -- [conference2026@scverse.org](conference2026@scverse.org): for matters regarding the [next conference](/conference2026) -- [steering-council@scverse.org](steering-council@scverse.org): [steering council](/about/roles#steering-council) (e.g. for questions about sponsorships) +- [core@scverse.org](mailto:core@scverse.org): [core team](/about/roles#core-team) +- [conference2026@scverse.org](mailto:conference2026@scverse.org): for matters regarding the [next conference](/conference2026) +- [steering-council@scverse.org](mailto:steering-council@scverse.org): [steering council](/about/roles#steering-council) (e.g. for questions about sponsorships) From 1c405d4b6d614ac9d08f87a030eb140fc28a464b Mon Sep 17 00:00:00 2001 From: Lukas Heumos Date: Sun, 23 Aug 2026 22:03:15 +0200 Subject: [PATCH 3/4] Tidy up the rest of the roles and people pages The sub-roles sentence had a botched edit in it: "depending on the kinds covering different kinds of contributions". The steering council's social account was linked as @scverse on twitter.com; the handle is @scverse_team and the domain is x.com, which the rest of the site already uses. Four core team members have no e-mail in the people data, and the layout rendered an empty for each of them. Signed-off-by: Lukas Heumos --- content/about/roles/_index.md | 6 ++---- layouts/people/list.html | 8 +++++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/about/roles/_index.md b/content/about/roles/_index.md index 5ec0d75e..c9f95709 100644 --- a/content/about/roles/_index.md +++ b/content/about/roles/_index.md @@ -49,7 +49,7 @@ They have shown they can be trusted to maintain scverse with care. Team members appear as organization members on the scverse [GitHub organization](https://github.com/orgs/scverse/people) and are on our `scverse/core` GitHub team. The current members are listed on our [people page](/people/#core-team), and the team can be reached by e-mail at [core@scverse.org](mailto:core@scverse.org). -There are sub-roles within the core team depending on the kinds covering different kinds of contributions and responsibilities. +There are sub-roles within the core team covering different kinds of contributions and responsibilities. #### Core Developers @@ -77,9 +77,7 @@ The Steering Council (SC) members are core team members who have additional resp SC members are expected to participate in strategic planning, approve changes to the governance model, and make decisions about funding granted to scverse itself (funding to community members is theirs to pursue and manage). Changes that impact the full project require analysis informed by extensive experience with both the project and the larger ecosystem. When the core team (including the SC members) fails to reach a consensus in a reasonable timeframe, the SC is the entity that resolves the issue. -Members of the steering council also have the "owner" role within the [scverse GitHub organization](https://github.com/scverse/) -and are ultimately responsible for managing the [scverse](https://github.com/scverse) GitHub account, the [@scverse](https://twitter.com/scverse_team) -twitter account, the [scverse website](https://scverse.org), and other similar scverse-owned resources. +Members of the steering council also have the "owner" role within the [scverse GitHub organization](https://github.com/scverse/) and are ultimately responsible for managing the [scverse](https://github.com/scverse) GitHub account, the [@scverse_team](https://x.com/scverse_team) account on X, the [scverse website](https://scverse.org), and other similar scverse-owned resources. The steering council is currently fixed in size to three members. This number will be increased as our community grows and diversifies, but will always be an odd number to ensure a simple majority vote outcome is always possible. diff --git a/layouts/people/list.html b/layouts/people/list.html index e19ce5f1..48212338 100644 --- a/layouts/people/list.html +++ b/layouts/people/list.html @@ -30,9 +30,11 @@

{{ $team.name }}

{{ if .showDetails }}

{{ .role }}

-

- {{ .email }} -

+ {{ with .email }} +

+ {{ . }} +

+ {{ end }}

{{ .affiliation }}

{{ end }} From 5f1634ce1c67a203ef6b0b467bf765a45126d3d0 Mon Sep 17 00:00:00 2001 From: Lukas Heumos Date: Sun, 23 Aug 2026 22:04:59 +0200 Subject: [PATCH 4/4] Point the contributing guide at its current URL The /page/dev/ path has been redirecting to /en/stable/dev/ for a while. Signed-off-by: Lukas Heumos --- content/about/roles/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/about/roles/_index.md b/content/about/roles/_index.md index c9f95709..f9a296a2 100644 --- a/content/about/roles/_index.md +++ b/content/about/roles/_index.md @@ -30,7 +30,7 @@ Any community member can become a contributor, and all are encouraged to do so. By contributing to the project, community members can directly help to shape its future. All community members are required to adhere to our [code of conduct](/about/code_of_conduct/). -Potential contributors are encouraged to read the [Contributing Guide](https://scanpy.scverse.org/page/dev/index.html). +Potential contributors are encouraged to read the [Contributing Guide](https://scanpy.scverse.org/en/stable/dev/index.html). A community member becomes a contributor when the following criteria are met: