docs: add AI contributing guidelines

[brendt]

No description provided.

[iamdadmin]

Thought I'd comment here, how's this @brendt or did I still go a bit too far with it?

AI contributions

Overview

Behind Tempest is a small group of humans who are passionate about code and this project. We welcome anyone who's passionate about PHP and programming to join Tempest, regardless of the tools they are using. At the same time, we expect a level of respect between each other.

As an example, PRs that were AI-generated without any self-review from the contributor's side don't show mutual respect, as it puts the burden of reviewing LLM-generated code on the maintainer's side. We expect each contributor to take a level of ownership and responsibility over their contributions (before they are merged), to make sure the submitted code is clean and understandable, well-tested and adhering to our code style. In turn, from our side, we will be happy to guide anyone who's eager to learn, as long as it goes both ways. We also expect each contributor to ensure that code they are contributing is compatible with the Tempest License.

Definitions

GenAI - short for Generative AI referring to Code Assistants or Chat Agents.

Code Assistants - such as (but not limited to) OpenAI Codex, Claude Code, Gemini Code, Cursor, Windsurf, and others. These are embedded in your development software and/or are integrated with your terminal.

Chat Agents - such as (but not limited to) ChatGPT, Copilot, Claude Gemini, and others. These are accessed via a website chat interface, and are not embedded with your development software.

Contributions Containing or Consisting of GenAI Code - A contribution which includes any proportion of code sourced via GenAI, from a single line you checked syntax on with a Chat Agent, through to fully generated by a Code Assistant.

Policy

1. Contributions Containing or Consisting of GenAI Code will be considered in line with all other contributions. Do however bear in mind that they may require extra review by our maintainers. Respect their time, by documenting your code well, including appropriate and meaningful tests which pass on your local environment before you create your draft PR, and be able to respond to comments and questions as needed, showing that you understand the function of and need for the code you have included. Furthermore, try to make contributions in small parcels, to make the review easier to handle, and sure your code aligns to Tempest coding standards (mago lint, mago fmt and review naming conventions).

2. Contributions which are too large in scope, do not follow Tempest coding standards, or if you do not or cannot answer queries and questions from the maintainers, are highly likely to be declined. Showing repeated disrespect to the restricted time and resources of Tempest framework and the maintainers in this manner may result in removal of your ability to submit PRs for consideration, at the discretion of the maintainers.

3. As with all contributions, the maintainers may decline contribution to Tempest framework, and instead suggest you launch this is a third-party package. If you aren't sure whether your contribution is suitable for Tempest framework, or simply wish to learn more about Tempest, you can raise this as a Feature Request / Discussion on GitHub, or join the Discord.

Summary

In other words, you may use whatever tools you want to write code (editors, IDEs, AI chat, agents, …), but you must take ownership and responsibility over your PRs. The least we ask is that you yourself understand the code you've written or generated and are able to explain it in full.

[xHeaven]

Thought I'd comment here, how's this @brendt or did I still go a bit too far with it?

Though it's definitely not a bad write-up, I think it's a bit over the top. Realistically, if someone slaps 20 PRs in our face, "made by ClaudeTM", they will not read this much text.

The license addition is a good touch, I would keep that.
The definitions I'm not sure they're needed.

Policy 1 is ambiguous, it's pretty much what's written in the Overview.
Policy 2 is also ambiguous, those rules are applying for every PR, not just AI-contributed ones.
Policy 3 is basically Policy 2 with extra steps (join Discord), feels ambiguous as well.

Thoughts?

[brendt]

Yeah I think the definition and policy sections are a bit overkill for now, but I really like the rephrasing of the first paragraphs, so I've copied that 👍

[innocenzi]

Very well put 👍