Rangeban India from making Pull Requests about express HOT 15 CLOSED

I dislike this idea, it's racist and I highly doubt anyone will approve of this

from express.

There have been several issues like this that are now closed. It is not something that is planned. By not checking closed issues before posting you are only contributing to this spam

from express.

I just took a look at all the low-quality PR's and I think an alternative could be to only allow users that have activity older than 6 months, or something similar.

from express.

There have been several issues like this that are now closed. It is not something that is planned. By not checking closed issues before posting you are only contributing to this spam

I don't want to hear about contributing to spam from a guy begging to be a triager in issues.

There is no begging - I requested the triager access following the template as is normal proccedure. Unlike you, I am actually trying to help, which is why I requested the triager role. I don't want to hear toxic comments from someone with 20 commits in the past decade, how about you git good and stay in your lane? You added no value with your issue, only taking away resources from other people in this community

from express.

This issue is going out of topic. I will close it. Current discussions around the PRs moderation are in #5449

from express.

Closing the issue as this is a steril conversation. By geoblocking it would impact open source as a whole, also blocking contributors that do travel. Some other rules can be put in place, and being discussed

edit: @UlisesGascon was faster :D

from express.

a way to combat this issue would be nice for sure, it is way too abusable

from express.

I dislike this idea, it's racist and I highly doubt anyone will approve of this

Not really. If a Git repo got a large quantity of bot spam requests from Russia or China which are both famous for having large bot farms due to poor cyber laws, it'd be a useful feature. Range banning countries that cause problems is a common practice in the real world, kid.

from express.

I dislike this idea, it's racist and I highly doubt anyone will approve of this

Not really. If a Git repo got a large quantity of bot spam requests from Russia or China which are both famous for having large bot farms due to poor cyber laws, it'd be a useful feature. Range banning countries that cause problems is a common practice in the real world, kid.

Adding kid at the end of your reply doesn't make your message any less racist. There are software developers much more talented than you in all 3 of the countries you mentioned. A blanket ban like this would be very harmful for FOSS

from express.

Calling it racist isn't going to make India stop spamming :^)

from express.

There have been several issues like this that are now closed. It is not something that is planned. By not checking closed issues before posting you are only contributing to this spam

I don't want to hear about contributing to spam from a guy begging to be a triager in issues.

from express.

I just took a look at all the low-quality PR's and I think an alternative could be to only allow users that have activity older than 6 months, or something similar.

Pretty solid idea. Do you mean Git activity as a whole or just to this repo? Because if it's just to this repo, I'm afraid that would drive off new people who want to contribute.

from express.

There have been several issues like this that are now closed. It is not something that is planned. By not checking closed issues before posting you are only contributing to this spam

I don't want to hear about contributing to spam from a guy begging to be a triager in issues.

There is no begging - I requested the triager access following the template as is normal proccedure. Unlike you, I am actually trying to help, which is why I requested the triager role. I don't want to hear toxic comments from someone with 20 commits in the past decade, how about you git good and stay in your lane? You added no value with your issue, only taking away resources from other people in this community

Well yeah, I typically use Bitbucket instead of Github. It doesn't have these kind of problems. But since I use express.js as a dependency I'm helping come up with a solution instead of being a crybaby like you. You begging for a triager role so you can show it on your little resume is no different than all the Indians begging for PR to the readme.md so they can put it on their resume. Grow up, little man.

from express.

There have been several issues like this that are now closed. It is not something that is planned. By not checking closed issues before posting you are only contributing to this spam. And you know it

I don't want to hear about contributing to spam from a guy begging to be a triager in issues.

There is no begging - I requested the triager access following the template as is normal proccedure. Unlike you, I am actually trying to help, which is why I requested the triager role. I don't want to hear toxic comments from someone with 20 commits in the past decade, how about you git good and stay in your lane? You added no value with your issue, only taking away resources from other people in this community

Well yeah, I typically use Bitbucket instead of Github. It doesn't have these kind of problems. But since I use express.js as a dependency I'm helping come up with a solution instead of being a crybaby like you. You begging for a triager role so you can show it on your little resume is no different than all the Indians begging for PR to the readme.md so they can put it on their resume. Grow up, little man.

I think it's obvious to anyone reading these who the little man is in this conversation. Projecting racism and belittling others on the internet speaks more about you than about myself or express js

from express.

@taylordwright44 make anymore personal attacks and you will be banned, I'm being nice even giving you a warning here because we don't tolerate that type of rude behavior here.

FYI for anyone reading this, the trigger role is well documented and participation in it is super helpful to the project. We will be getting to the issue for those soon after we have our upcoming TC meeting.

from express.