On Sun, Feb 15, 2026 at 9:06 AM sebastian <[email protected]> wrote:
> Hey! > > thanks a lot for chiming in, still watching the videos! > > FWIW, I have come around in that I guess we should add something (a lot > of projects > are discussing this, I would be happy to just steal one too). > I would still focus on the transparency and social part (because I think > that > is the part that affects us more in practice) rather than copyright, but > yeah, > I guess it deserves a place. > > > It may well be nice to force a checkbox and a short note in the PR > template, I am > not sure what will work there, but it may also depend a bit on the "risk > assessment" > how much detail we need. > I asked Grok about this, and it suggested a template as the best solution: # Pull Request ## Description ## Checklist ### Required for all PRs - [ ] I have read the [Contributing Guidelines]( https://numpy.org/doc/stable/dev/index.html) - [ ] Tests have been added or updated (and all tests pass) - [ ] Documentation has been updated (docstrings, user guide, release notes if needed) - [ ] Code style: I have run `ruff check --fix` and `ruff format` (or `pre-commit run --all-files`) ### AI Usage (required disclosure) - [ ] I have disclosed any use of AI tools below: - **AI tools used**: (e.g. Claude, GitHub Copilot, ChatGPT, Cursor, etc. — or "None") - **How they were used**: (e.g. "Generated first draft of new function X", "Helped write tests", "Refactored docstring", "None") - **Review notes**: (optional — anything reviewers should pay extra attention to) ### Additional notes <snip> Chuck
_______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]
