Update project CoC to match WordPress Project & update out-of-date AI guidelines.

[dd32]

Description

This PR:

• Updates the repository to include the proper WordPress project CoC.
• Removes outdated AI guidelines which are incompatible with the project CoC.
• Removes the outdated funding section, a vestige of the coding standards being a separate project.

Any discussion related to the validity of the guidelines should likely be discussed with the AI team, via https://make.wordpress.org/ai/2026/02/01/ai-guidelines-for-wordpress/ or #core-ai on Slack.

Partially reverts #2598

Suggested changelog entry

None required. Alternatively: Welcome the usage of AI tools.

Related issues/external references

Related: #2722 (comment)

[jrfnl]

@dd32 These are three different decision points and therefore this PR should be split into three different PRs.

We've had a discussion about the CoC previously in #2423 and while their solution was not good enough, the current proposal with the CoC being part of the .github repository, seems fine.

However, things like AI usage has been discussed for this project in #2594 and #2598 based on real world problems it was causing. Changing that deserves it's own discussion and - to me - is not acceptable.

[4thhubbard]

After catching up on the threads, there are a few things to address:

This repo is part of the WordPress project, so it should align with project-level standards. On AI specifically, current project direction allows AI use with human review. Blanket bans aren't aligned with that.

Please bring this in line so contributors have consistent expectations across the project.

[rodrigoprimo]

@dd32, thanks for putting this together. I'd like to second the suggestion to split this into three separate PRs. Each of these is an independent decision, and discussing them separately would help keep each conversation focused. It would also make it easier to move each one forward.

[dd32]

Given the 3 items are all interlinked, I'm not inclined to split this into multiple PRs.
Edit: This is because I don't feel that there's any discussion worth taking place, any discussion could occur here.

If an existing active maintainer would like to create a new PR with different wording, that conveys the same intent, or action the removal of CoC / Funding as a separate commit, please go ahead.

Otherwise I'll merge this on friday, to bring the repository inline with the rest of the WordPress repositories.

[jrfnl]

@dd32 Based on the attitude you display in this issue, in my opinion, you are violating the code of conduct you are trying to introduce....

• Being respectful of differing opinions, viewpoints, and experiences
• Giving and gracefully accepting constructive feedback

• Other conduct which could reasonably be considered inappropriate in a professional setting

[dd32]

@jrfnl With all respect, I do not understand why you feel the need for a debate on whether this repository should align with the WordPress project standards and guidelines.

Splitting this into 3 PRs provides NO benefit to the community, or you, or me, other than duplicating discussion on that core question in three different places.

I respectfully ask that you raise your objections and concerns here without just saying (I'm paraphrasing) "No, we've discussed this elsewhere"

I have personally felt attacked by yourself, and you have felt attacked by me. This was not my intention, but that's where we're at.

[4thhubbard]

Catching up on this thread and want to step in before this goes further off track.

This repo is part of the WordPress project and should reflect project standards and contributor expectations, including current direction around AI usage.

I support the intent behind this PR and bringing the repo into alignment with the broader project.

There are reasonable implementation questions to work through, but alignment with the broader project should not be controversial here.

Let’s focus on the remaining practical concerns and move this forward constructively.

[dd32]

Closing in favour of three focused PRs, as requested:

• Update project Code of Conduct to match WordPress Project #2733 — Update project Code of Conduct to match WordPress Project (removes the project-specific CODE_OF_CONDUCT.md and links to the WordPress project CoC from the README)
• Remove outdated Funding section #2734 — Remove outdated Funding section (removes the README Funding section and .github/FUNDING.yml)
• Update out-of-date AI usage guidelines in CONTRIBUTING.md #2735 — Update out-of-date AI usage guidelines in CONTRIBUTING.md (aligns with the WordPress AI Guidelines)

Please surface objections and concerns (if any) on each of those PRs.

[jrfnl]

@dd32 Thank you for splitting the PR.

[rodrigoprimo]

Thanks for splitting the PR, @dd32!