Skip to content

few typos #126

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
merged 1 commit into from
Jul 30, 2024
Merged

few typos #126

Show file tree
Hide file tree
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
6 changes: 3 additions & 3 deletions content/about/mission/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ These tools are placed under shared maintenance and development in the `scverse`

## User engagement

We are community-driven and committed to keeping the `scverse` community open. We strive to actively foster a community where everyone is and feels welcomed, and where there are no barriers to contributions in any form. We welcome newcomers and pledge to build an environment where they can grow as contributors, developers and community members. Together with technical and development support, we also support our users through:
We are community-driven and committed to keeping the `scverse` community open. We strive to actively foster a community where everyone is and feels welcomed, and where there are no barriers to contributions in any form. We welcome newcomers and pledge to build an environment where they can grow as contributors, developers, and community members. Together with technical and development support, we also support our users through:

* Clear documentation of code and usage via docs and tutorials.
* Participation in development through issues and pull requests.
Expand All @@ -40,10 +40,10 @@ Development of these packages is not restricted – contributions are welcomed a
However, `scverse` aims to support the external development of new approaches to analyze and work with single cell data.
We encourage the creation of new methods and tools on top of the *core* packages and data-structures.

We support the development these ecosystem packages by:
We support the development of these ecosystem packages by:

* Providing stable APIs to build on top of.
* Providing standardized and well supported data structure to pass around data.
* Providing standardized and well-supported data structure to pass around data.
* Making sure all contributions are recognized in our change logs and documentation.
* Promoting 3rd party packages that rely on `scverse` via our websites and social media feeds.
* Establishing open communication channels for:
Expand Down
16 changes: 8 additions & 8 deletions content/about/roles/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
The purpose of this document is to formalize the governance process used by the `scverse` project, to clarify how decisions are made and how the various groups within our community interact.

As a whole, we are a consensus-based community project.
However, any subproject within the scverse can have their own governance system as long as they do not conflict with the rules set out here.
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.
This document describes how that participation takes place, how to find consensus, and how deadlocks are resolved.

Expand All @@ -23,7 +23,7 @@ among other possibilities.
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 by our [code of conduct](https://scverse.org/about/code_of_conduct/).
All community members are required to adhere to our [code of conduct](https://scverse.org/about/code_of_conduct/).
Potential contributors are encouraged to read the [Contributing Guide](https://scanpy.readthedocs.io/en/stable/dev/index.html).

A community member becomes a contributor when the following criteria are met:
Expand All @@ -38,15 +38,15 @@ This includes who gets commit rights to their projects.

## Core team

The core team are community members that have demonstrated continued commitment to the project through ongoing contributions.
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.

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

### Core developers

Core developers are members of the core team who have made signifigant code contributions to `scverse`.
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.
Expand All @@ -60,7 +60,7 @@ While there is no hard-and-fast rule about who can be nominated, ideally, they s
* Contributed to the discussion and review of others' work
* Collaborated in a way befitting our community values

After nomination admission will be decided by two-thirds majority vote on a private mailing list by the core team.
After nomination, admission will be decided by two-thirds majority vote on a private mailing list by the core team.

Primary maintainers of new core packages, who are not already core developers, will be invited to join.

Expand Down Expand Up @@ -91,17 +91,17 @@ 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`, or via the [@scverse/steering-council](https://github.com/orgs/scverse/teams/steering-council) GitHub team.

## Management committee
## 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 managment committee, will be invited to join.

## Scientific advisory board
## Scientific Advisory Board

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

Members of the scientific adivsory boards are nominated by the core team.
Members of the scientific advisory boards are nominated by the core team.

# Decision Making Process

Expand Down
Loading