make no-AI wording in readme clearer

Open Beginner friendly
#643 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github
Domain
documentation

Research direction

Open .github/README.md and read the existing notice about AI contributions. Clarify that the policy covers GitHub interactions, code generation, and other uses beyond asking for explanations. Done means the notice is specific enough that a first-time contributor cannot mistake its scope.

Written by the indexing model from the issue text.

Description

good first issue help wanted r-docs

no worries, keep the existing work, no need to remake it

I'll make the wording on the readme clearer

Originally posted by @alejandro-vaz in #636

the GitHub readme in .github/README.md already contains a notice that AI contributions are not allowed in any @servo repository, but it is quite ambiguous

a first-time contributor can genuinely read it as "no autonomously generated PRs", or have no idea it applies to communication over GitHub as well

simply make the notice a bit more specific saying it includes, but is not limited to:

  • all interactions over github
  • code generation
  • basically anything that isn't just asking chatgpt "how the hell does this even work"
Dominant language
Rust
Stars
1.7k
Forks
218
Avg merge
19h 39m
Merged PRs (30d)
103

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from servo/rust-smallvec

All issues in servo/rust-smallvec

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.