Moderation concept for issues on git repositories #7

New Issue

GiteaMirror · 2025-11-02T03:03:12-06:00

GiteaMirror commented

2025-11-02 03:03:12 -06:00

Originally created by @joubertredrat on GitHub (Nov 2, 2016).

Hi guys,

Open source projects is amazing, but sometimes, noob users usually more disturb than help and collaborate on issues.
Because this I think that is good idea to implement moderation option on issues, so repo owerns and moderators
may ban user on specific issue or on all repo issues.

Example, I want to ban octocat on my awesome-devops repo on "Add Puffin" because she is spamming on issue,
I can enable ban and put reason "you're not following the rules", then when octocat try to comment,
will not possible, because is banned and will display to octocat "You can't post on this issue, reason: you're not following the rules".

Like this, if octocat is banned on all repo, she can't open new issue and display too "You can't open this issue, reason: I don't like you".

This idea is to prevent this as example: https://github.com/git/git/pull/233

This is only a concept, what you think guys?

Original idea: https://gist.github.com/joubertredrat/05759a27b71a4e2da72f9079edc9694b
Issue on GitLab: https://gitlab.com/gitlab-org/gitlab-ce/issues/19801

Reference: https://github.com/gogits/gogs/issues/3658

Originally created by @joubertredrat on GitHub (Nov 2, 2016). Hi guys, Open source projects is amazing, but sometimes, noob users usually more disturb than help and collaborate on issues. Because this I think that is good idea to implement moderation option on issues, so repo owerns and moderators may ban user on specific issue or on all repo issues. Example, I want to ban octocat on my awesome-devops repo on "Add Puffin" because she is spamming on issue, I can enable ban and put reason "you're not following the rules", then when octocat try to comment, will not possible, because is banned and will display to octocat "You can't post on this issue, reason: you're not following the rules". Like this, if octocat is banned on all repo, she can't open new issue and display too "You can't open this issue, reason: I don't like you". This idea is to prevent this as example: https://github.com/git/git/pull/233 This is only a concept, what you think guys? Original idea: https://gist.github.com/joubertredrat/05759a27b71a4e2da72f9079edc9694b Issue on GitLab: https://gitlab.com/gitlab-org/gitlab-ce/issues/19801 Reference: https://github.com/gogits/gogs/issues/3658

GiteaMirror added the type/proposal label 2025-11-02 03:03:12 -06:00

GiteaMirror commented

2025-11-02 03:03:13 -06:00

@jhasse commented on GitHub (Nov 3, 2016):

"You can't open this issue, reason: I don't like you"

Hm ... thats exactly the reason why I dont like this idea. It should be obvios to outsiders that a certain person is blocked. Maybe still show the post with a "Marked as spam" spoiler?

@jhasse commented on GitHub (Nov 3, 2016): > "You can't open this issue, reason: I don't like you" Hm ... thats exactly the reason why I dont like this idea. It should be obvios to outsiders that a certain person is blocked. Maybe still show the post with a "Marked as spam" spoiler?

GiteaMirror commented

2025-11-02 03:03:13 -06:00

@joubertredrat commented on GitHub (Nov 3, 2016):

@jhasse a little question, is you as owner of your project can control your code by PRs, why not you can control your issues from spammers as example?

I will explain with example. I hate @bkcsoft and he is owner of this repo, I want to irritate him, then, I will open a lot of Issues spamming and PR's bombs with robots. Today in Github, @bkcsoft can't do anything but close the issues and refuse PR, maybe report to GitHub e maybe Github will ban me.

This is strange because @bkcsoft is owner but don't have control of your repository issues. The idea of moderation and just for that, @bkcsoft already have control of your code on repository and with this concept, have control of issues too.

Gitlab is studing this case, https://gitlab.com/gitlab-org/gitlab-ce/issues/19313

PS: @bkcsoft I hate you only on example 👍

@joubertredrat commented on GitHub (Nov 3, 2016): @jhasse a little question, is you as owner of your project can control your code by PRs, why not you can control your issues from spammers as example? I will explain with example. I hate @bkcsoft and he is owner of this repo, I want to irritate him, then, I will open a lot of Issues spamming and PR's bombs with robots. Today in Github, @bkcsoft can't do anything but close the issues and refuse PR, maybe report to GitHub e maybe Github will ban me. This is strange because @bkcsoft is owner but don't have control of your repository issues. The idea of moderation and just for that, @bkcsoft already have control of your code on repository and with this concept, have control of issues too. Gitlab is studing this case, https://gitlab.com/gitlab-org/gitlab-ce/issues/19313 PS: @bkcsoft I hate you only on example :+1:

GiteaMirror commented

2025-11-02 03:03:13 -06:00

@xinity commented on GitHub (Nov 3, 2016):

i like to idea to be able to cleanup irrelevant issues (or so to speak), but i'm sure it will take a huge amount of energy to build, implement and manage.

i'd be happy to know how many projects implement this moderation system ?
don't get me wrong, it's just i'm wondering if it's really worth it, considering the overhead it will have on the moderation team

@xinity commented on GitHub (Nov 3, 2016): i like to idea to be able to cleanup irrelevant issues (or so to speak), but i'm sure it will take a huge amount of energy to build, implement and manage. i'd be happy to know how many projects implement this moderation system ? don't get me wrong, it's just i'm wondering if it's really worth it, considering the overhead it will have on the moderation team

GiteaMirror commented

2025-11-02 03:03:13 -06:00

@strk commented on GitHub (Nov 3, 2016):

I think the these kind of attacks should be prevented somewhat automatically (rate limiting, spam filtering)

@strk commented on GitHub (Nov 3, 2016): I think the these kind of attacks should be prevented somewhat automatically (rate limiting, spam filtering)

GiteaMirror commented

2025-11-02 03:03:13 -06:00

@lunny commented on GitHub (Nov 3, 2016):

Good idea. But I think this will not be the emphasis currently.

@lunny commented on GitHub (Nov 3, 2016): Good idea. But I think this will not be the emphasis currently.

GiteaMirror commented

2025-11-02 03:03:14 -06:00

@worthy7 commented on GitHub (Oct 7, 2019):

Just to add my 2 cents here, I think if this is a not a feature in GitHub, then we shouldn't really try to copy it.
No doubt this idea has been raised with GitHub internally and they decided not to implement it (to my knowledge at least?). So although it sounds good, this is just one of the down-sides of open source really. on the upside - unlimited contributors!

@worthy7 commented on GitHub (Oct 7, 2019): Just to add my 2 cents here, I think if this is a not a feature in GitHub, then we shouldn't really try to copy it. No doubt this idea has been raised with GitHub internally and they decided not to implement it (to my knowledge at least?). So although it sounds good, this is just one of the down-sides of open source really. on the upside - unlimited contributors!

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7