chaokunyang commented on code in PR #3437:
URL: https://github.com/apache/fory/pull/3437#discussion_r2867498669
##########
AI_CONTRIBUTION_POLICY.md:
##########
@@ -0,0 +1,127 @@
+# AI Contribution Policy
+
+Apache Fory is a performance-critical foundational serialization framework
with cross-language compatibility requirements.
+AI tools are welcome as assistants, but project quality, legal safety, and
maintainability standards are unchanged.
+
+The key words MUST, MUST NOT, REQUIRED, SHOULD, and MAY are interpreted as
described in RFC 2119.
+
+## 1. Core Principle
+
+- AI tools MAY assist contribution work.
+- AI tools MUST NOT replace contributor accountability.
+- The human submitter is responsible for correctness, safety, performance, and
maintainability of all submitted changes.
+- AI-assisted code MUST be reviewed carefully by the contributor line by line
before submission.
+- Contributors MUST be able to explain and defend design and implementation
details during review.
+
+## 2. Disclosure (Privacy-Safe)
+
+For substantial AI assistance, PR descriptions MUST include a short `AI Usage
Disclosure` section.
Review Comment:
This is indeed ambiguous. I added some clarification:
Definition of substantial AI assistance:
- Substantial means AI materially influenced technical content, not only
writing style.
- Contributors MUST mark AI assistance as substantial (`yes`) if any of the
following apply:
- AI generated or rewrote non-trivial code/test logic (even for a small
change or a single function).
- AI-generated or AI-refactored content is about 20 or more added/changed
lines in aggregate.
- AI materially influenced API, protocol, type mapping, performance,
memory, or architecture decisions.
- AI produced substantive technical text used in PR rationale (beyond
grammar/translation cleanup).
- Contributors MAY mark substantial AI assistance as `no` for minor or
narrow assistance only, such as spelling/grammar fixes, formatting, trivial
comment wording edits, or other non-technical edits with no behavior impact.
Required disclosure fields:
- Whether substantial AI assistance was used (`yes` or `no`)
- Scope of assistance (for example: design drafting, code drafting, refactor
suggestions, tests, docs)
- Affected files or subsystems (high-level)
- Human verification performed (checks run locally or in CI, and results
reviewed by the contributor)
- Provenance and license confirmation (see Section 6)
Standard disclosure template (recommended):
```text
AI Usage Disclosure
- substantial_ai_assistance: yes
- scope: <design drafting | code drafting | refactor suggestions | tests |
docs | other>
- affected_files_or_subsystems: <high-level paths/modules>
- human_verification: <checks run locally or in CI + pass/fail summary +
contributor reviewed results>
- performance_verification: <N/A or benchmark/regression evidence summary>
- provenance_license_confirmation: <Apache-2.0-compatible provenance
confirmed; no incompatible third-party code introduced>
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
