|
1 | 1 | ### PR summary |
2 | | -<!-- Please take some time to make it easier for us maintainers to understand |
3 | | - and review your PR. Describe the pull request, using the questions below as |
4 | | - guidance, and link to any relevant issues and PRs. |
| 2 | +<!-- Please take some time to make it easier for us to review |
| 3 | +your pull request (PR). Describe the PR using the questions below as guidance. |
5 | 4 |
|
6 | | - |
7 | | - Also, have you hit all [the guidelines](https://numpy.org/devdocs/dev/index.html#guidelines)? |
8 | | - And have you filled out the disclosure section below? |
| 5 | +- What problem does this PR solve? Link any relevant issues and PRs. |
| 6 | +- Why are you interested in working on this PR? |
| 7 | +- How does the proposed change help you? |
| 8 | +
|
| 9 | +Please keep in mind that even seemingly small changes can have unexpected consequences |
| 10 | +for workflows unrelated to the ones you may be familiar with. For this reason, maintainers |
| 11 | +carefully consider the risks of all changes, including bug fixes. |
| 12 | +
|
| 13 | +Make sure to review the guidelines for contributing code to NumPy (https://numpy.org/devdocs/dev/index.html#guidelines) and fill out the AI disclosure section below. |
| 14 | +
|
| 15 | +Please note that non-maintainers may only have 2 non-draft PRs open for review at a |
| 16 | +time. |
9 | 17 |
|
10 | 18 | --> |
11 | 19 |
|
12 | | -### First time committer introduction |
13 | | -<!-- If you are new to the NumPy community, please introduce yourself. How do you |
14 | | - use NumPy, what prompted you to make this contribution? We are a community of |
15 | | - mostly volunteers, and getting to know you helps us trust your judgement |
16 | | - and welcome you into the community. |
| 20 | +### First time contributor introduction |
| 21 | +<!-- If you are new to the NumPy contributor community, please introduce yourself and |
| 22 | +share how you use NumPy. It helps us get to know you, understand the context of your |
| 23 | +contribution, and collaborate more effectively during the review process. 2-3 |
| 24 | +sentences is plenty, we are not looking for a work history or a measure of your |
| 25 | +expertise. |
| 26 | +
|
17 | 27 | --> |
18 | 28 |
|
19 | 29 | #### AI Disclosure |
20 | | -<!-- If AI was used in the preparation of this pull request, please disclose |
| 30 | +<!-- If AI was used in the preparation of this PR, please disclose |
21 | 31 | the tool(s) used, how they were used, and specify what code or text is AI generated. |
22 | | -If no AI tools were used, please write "No AI tools used" in this section. Read our |
23 | | -policy on AI generated code at |
24 | | -https://numpy.org/devdocs/dev/ai_policy.html. |
| 32 | +If no AI tools were used, please write "No AI tools used" in this section. |
| 33 | +
|
| 34 | +All interactions with reviewers must be performed by humans, including the submission of PRs. |
| 35 | +
|
| 36 | +Read the NumPy policy on AI generated code at https://numpy.org/devdocs/dev/ai_policy.html. |
25 | 37 |
|
26 | | -In particular, all interaction is to be done by humans, including submission of PRs. |
27 | 38 | --> |
0 commit comments