Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions docs/ai-contributions-policy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# AI-Assisted Contributions Policy for htop
v1.0, 2026-02-18

1. You **MAY** use AI assistance for contributing to htop, as long as you follow the principles described below.

2. **Accountability**:

You *MUST* take the responsibility for your contribution.

Contributing to htop means vouching for the quality, license compliance, and utility of your submission.

All contributions, whether from a human author or assisted by large language models (LLMs) or other generative AI tools, must meet the project’s standards for inclusion.

The contributor is always the author and is fully accountable for the entirety of these contributions.

3. **Transparency**:

You *MUST* disclose the use of AI tools when the significant part of the contribution is taken from a tool without changes.

You *SHOULD* disclose the other uses of AI tools, where it might be useful.

Routine use of assistive tools for correcting grammar and spelling, or for clarifying language, does not require disclosure.

- Disclosures are made where authorship is normally indicated. For contributions tracked in git, the recommended method is an `Assisted-by:` commit message trailer.

- Examples:

- `Assisted-by: generic LLM chatbot`

- `Assisted-by: ChatGPTv5`

For contributions outside git commits, disclosure may include document preambles, design file metadata or `Assisted-by:` lines on issues.

4. **Contribution Evaluation**:

AI tools may be used to assist human reviewers by providing analysis and suggestions.

You *MUST NOT* use AI as the sole or final arbiter in making a substantive or subjective judgment on a contribution.

This does not prohibit the use of automated tooling for objective technical validation, such as CI/CD pipelines, automated testing, or spam filtering.

The final accountability for accepting a contribution, even if implemented by an automated system, always rests with the human contributor who authorizes the action.

This policy has been adapted for htop use from the Fedora policy v1.0 published at <https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/>.

The key words “MAY”, “MUST”, “MUST NOT”, and “SHOULD” in this document are to be interpreted as described in [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
2 changes: 2 additions & 0 deletions docs/styleguide.md
Original file line number Diff line number Diff line change
Expand Up @@ -252,3 +252,5 @@ If you open a PR you need to follow up to resolve any comments/change requests.
Otherwise it may be closed without merging.

Rebase early. Rebase often.

Please check the [AI-Assisted Contributions Policy](ai-contributions-policy.md) for requirements and mandatory disclosure in your commits and PRs if you use AI assistance in creating your work.
Loading