Skip to content

docs : explicit about banning accounts that violates policy#19593

Merged
ngxson merged 1 commit intoggml-org:masterfrom
ngxson:xsn/ban_ai_gen_account
Mar 21, 2026
Merged

docs : explicit about banning accounts that violates policy#19593
ngxson merged 1 commit intoggml-org:masterfrom
ngxson:xsn/ban_ai_gen_account

Conversation

@ngxson
Copy link
Copy Markdown
Contributor

@ngxson ngxson commented Feb 13, 2026

Alternative to #18735

Pushing this PR as a suggestion, but I think one of the main reason why people keep pushing AI-generated PR even when the agent warned them, is because they see no consequences of doing so.

Even when banning accounts is technically hard (as maintainers don't technically have the right to do so), I think explicitly telling this will have a psychological impact.

@CISC
Copy link
Copy Markdown
Member

CISC commented Feb 13, 2026

Fine by me, but as you wrote may be hard to enforce, only @ggerganov can I think?

@ngxson
Copy link
Copy Markdown
Contributor Author

ngxson commented Feb 13, 2026

Only ggml-org members can access the moderator settings I think (github UX is not very convenient in this case, so kinda waste time to actually enforce)

@am17an
Copy link
Copy Markdown
Contributor

am17an commented Feb 13, 2026

I think there is no easy way here, I saw this https://github.com/mitchellh/vouch a few days ago. Perhaps we can wait and see how this turns out for the ghostty project.

@ngxson
Copy link
Copy Markdown
Contributor Author

ngxson commented Feb 13, 2026

@am17an I just saw this too, the idea is nice (same point as I brought up about the "consequences"), but I think their intent is to actually enforce something. My proposal here doesn't enforce anything, just to make it clear so that people know the potential consequence of their action (pure psychological)

@JohannesGaessler
Copy link
Copy Markdown
Contributor

I'm with banning people if they go against policy but I'm not sure if we need to explicitly spell this out. I think one will be hard-pressed to find a project where repeated policy violations don't get you eventually banned.

@ngxson
Copy link
Copy Markdown
Contributor Author

ngxson commented Feb 13, 2026

@JohannesGaessler I agree that this doesn't need to be written explicitly, but under one condition that we do actually ban accounts that repeatedly send AI-generated PRs

@CISC
Copy link
Copy Markdown
Member

CISC commented Feb 13, 2026

@JohannesGaessler I agree that this doesn't need to be written explicitly, but under one condition that we do actually ban accounts that repeatedly send AI-generated PRs

If there are no actual consequences the words are meaningless anyway.

Anyway, @danbev is a ggml-org member, I guess that means we have at least two people with the power in Diego's absence?

@Green-Sky
Copy link
Copy Markdown
Collaborator

Green-Sky commented Feb 13, 2026

:)

Copy link
Copy Markdown
Member

@ggerganov ggerganov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think maintainers should warn users who do not follow the AI policy + close PRs/issues. After a few failed attempts (let's say arbitrary 3), maintainers can request a ban of the account. We can discuss and execute ban requests internally within the organization?

@ngxson ngxson merged commit 568aec8 into ggml-org:master Mar 21, 2026
2 checks passed
@Green-Sky
Copy link
Copy Markdown
Collaborator

Green-Sky commented Mar 21, 2026

@aviallon :P

Seunghhon pushed a commit to Seunghhon/llama.cpp that referenced this pull request Apr 26, 2026
rsenthilkumar6 pushed a commit to rsenthilkumar6/llama.cpp that referenced this pull request May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants