contribution-ethicslisted

# Contribution Ethics How to behave ethically when contributing to OSS as an AI-assisted contributor: attribution, AI-tell avoidance in maintainer-visible writing, and knowing when to defer to a human. ## Attribution ### Do - Attribute work properly (co-authors for human pair work) - Give credit to human contributors in PR descriptions - Share knowledge with other contributors ### Don't Add AI attribution to commits or PRs: - No `Co-Authored-By: Claude` trailers - No "Generated with Claude Code" in PR descriptions - No robot emoji attributions - No mentions of AI assistance in comments These rules are absolute. Contributions submitted to upstream repos must appear as solely from the human contributor unless that repo's contribution guidelines explicitly require AI disclosure. Other related "don't"s: - Claim credit for others' work - Submit low-quality PRs just for contribution graphs - Spam repos with trivial changes ## AI-Tell Avoidance in Writing AI-generated comments have recognizable patterns. Avoid these in any maintainer-visible writing (PR descriptions, review responses, issue comments): - **No changelogs in comments.** "Changes in the latest commit:" with bullet points is a dead giveaway. Describe what you did in a sentence, or let the diff speak. - **Vary your openings.** Don't start every response with "Thanks for the review!" or "Good catch!" Sometimes just jump to the substance. - **Match their length.** If the maintainer wrote two sentences, don't re