Skip to content
Open
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
662 changes: 579 additions & 83 deletions assets/main.scss

Large diffs are not rendered by default.

14 changes: 12 additions & 2 deletions content/about/roles/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ The purpose of this document is to formalize the governance process used by the

For the community members who currently hold these roles, see the [people page](/people/).

{{< governance-chart >}}

As a whole, we are a consensus-based community project.
However, any subproject within the scverse can have its own governance system as long as they do not conflict with the rules set out here.
Anyone with an interest in the project can join the community, contribute to the project design, and participate in the decision making process.
Expand Down Expand Up @@ -48,7 +50,9 @@ 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` 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).
The team can be reached by e-mail at [core@scverse.org](mailto:core@scverse.org).

{{< role-members "core" >}}

There are sub-roles within the core team covering different kinds of contributions and responsibilities.

Expand Down Expand Up @@ -92,17 +96,23 @@ During that time deadlocked votes of the SC will be postponed until the new memb

The scverse steering council may be contacted at [steering-council@scverse.org](mailto:steering-council@scverse.org).

{{< role-members "council" >}}

### Management Committee

The management committee consists of PIs that support the development of scverse core projects. Members of the management committee are expected to secure funding and allocate resources to the continuous development of one or more core projects.

PIs supervising the development of new core packages, who are not already part of the management committee, will be invited to join.

{{< role-members "management" >}}

### Scientific Advisory Board

The scientific advisory board consists of highly experienced scientists devoted to research in single cell omics analysis. In an annual meeting, the scientific advisory board assesses the progress of scverse and suggests priorities for the next year based on the latest developments in the field.

Members of the scientific advisory board are nominated by the core team.
Members of the scientific advisory board are nominated by the core team.

{{< role-members "advisory" >}}

## Decision Making Process

Expand Down
Loading