-
-
Notifications
You must be signed in to change notification settings - Fork 914
Project Governance
| Role | Organization Membership | Organization Teams | Repository Privileges |
|---|---|---|---|
| Admin | Owner | @cupy/maintainers, @cupy/code-owners | Admin, Push, CI Trigger |
| Committer | Member | @cupy/external-committers, @cupy/code-owners | Push, CI Trigger |
| Reviewer | Member | - | CI Trigger |
| Contributor | - | - | - |
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
- @emcastillo
Committer 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, Committer, 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.
- Tests automatically triggered for every push
- GitHub Actions: tests coding style compliance, build, docs build, etc.
- ReadTheDocs: tests that the docs can be rendered correctly.
- Tests manually triggered via test phrases in pull-requests.
-
FlexCI (a.k.a. "pfnCI",
pfn-public-ci/*): runs unit tests with CUDA - Jenkins: runs unit tests with ROCm
-
FlexCI (a.k.a. "pfnCI",
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](e.g.,/test mini, head): triggers FlexCI projects that matches the tag AND Jenkins -
/test jenkins: triggers Jenkins only. Skips all FlexCI projects. -
/test skip: skips all CIs, both FlexCI and Jenkins.
To trigger CIs, the visibility of the CuPy organization membership must be set to Public.