Admin, also known as the Core Team, is responsible for all decisions made in the CuPy project. Current members are as follows:

• @kmaehashi
• @asi1024
• @toslunar

Maintainer and Reviewer roles will be designated to active community participants by the consent of all members of the Core Team.

The term "the Development Team" refers to a group of members with Admin, Maintainer, Triager, and Reviewer roles.

All members of the Development Team are required to:

• Turn on two-factor authentication for your GitHub account.
• Report to one of the Admin members when your GitHub account has been breached.

The following continuous integration (CI) systems are integrated to pull requests.

• CPU CIs: automatically triggered for every push
  • GitHub Actions (GitHub-hosted runner): tests coding style compliance, compilation, docs build, etc.
  • ReadTheDocs: tests that the docs can be rendered correctly
• GPU CIs: manually triggered via test phrases in pull-requests (see CI configuration for details)
  • PFN CI (pfn-public-ci/*): for CUDA
  • GitHub Actions (self-hosted runner): for ROCm

Only reviewers (or higher) can trigger CIs by using a trigger phrase in pull requests. Those triggering tests are required to check the content of the pull request to make sure that malicious code is not included (although the test environment is isolated for each test run.)

Trigger phrases are:

• /test [comma-separated test tags (evaluated as AND condition)] (e.g., /test mini): triggers PFN CI projects that matches the tag
• /test rocm: triggers GitHub Actions (self-hosted runner).
• /test skip: skips all GPU CIs
• /test force-skip: ignore all test failures in previous /test executions - only use this when you are confident that the failure is unrelated to the pull request!

To trigger CIs, the visibility of the CuPy organization membership must be set to Public.