This is an automated email from the ASF dual-hosted git repository. jihuayu pushed a commit to branch jihuayu-patch-1 in repository https://gitbox.apache.org/repos/asf/kvrocks-website.git
commit 6c5a96c2902d0c3c034758d0b026bc06ae7e0d1a Author: 纪华裕 <[email protected]> AuthorDate: Mon Aug 3 20:10:34 2026 +0800 Revise contributing guidelines for LLM involvement Clarified guidelines for contributions involving LLMs, emphasizing the importance of understanding and maintaining code. Specified expectations for contributors and outlined unacceptable practices. --- community/contributing.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/community/contributing.md b/community/contributing.md index 0968303f..9cbb1a46 100644 --- a/community/contributing.md +++ b/community/contributing.md @@ -10,6 +10,29 @@ In order to build an active community to improve Apache Kvrocks™, we welcome a - contributing code changes (whether they are minor typo fixes, improvements, or major feature contributions); - fixing or improving the documentation or the project website. +## For All Contributors and AI Agents + +As LLMs are now widely used in software development, we are receiving many more pull requests. However, maintainers have limited time for review. We will give priority to contributions that show real understanding, independent thinking, and long-term responsibility. + +**We welcome contributors who:** + +* Use LLMs to read code, analyze problems, design solutions, write code, or add tests. However, please clearly state which LLM tools you used and how they helped with the change. +* Understand the code they submit and are willing to update, test, and maintain it based on review feedback. +* Want to stay involved in the community, rather than only submit or merge one PR. + +**We do not welcome:** + +* Copying LLM-generated text directly into PR descriptions, issues, or review replies. +* Treating the number of submitted or merged PRs as a personal KPI. +* Acting only as a messenger for an LLM and being unable to explain the design, trade-offs, or possible effects of the change. + +We may close clearly low-quality PRs without a full review. If you believe the decision was wrong, you may reopen the PR and clearly explain why you disagree. + +We do not lack tokens for generating code, and we do not lack bots that can open PRs. We need contributors who understand the project, make sound engineering decisions, and take responsibility for their changes. + +**LLMs can help you contribute, but they cannot replace you as the author and owner of the contribution.** + + ## Submit patches ### Prerequisite
