NOTE: We may want to instead deploy our own bot that is a member of the Python org and has facebookarchive/mention-bot#212 added.

Previously we configured the mention-bot to only mention people who are members of the Python organization. However, this doesn't currently work if members don't have their membership public. Instead we will configure mention-bot to poke anyone, even non-members.

Or we could ask them to make their membership status public :) There is already a public list of core developers so I don't think there is a privacy concern here.

Yea. This just seemed easier than tracking down 88 people and bugging them to fiddle with their Github settings.

We could just send an email to python-committers list.

I think this is also a good idea, because it encourages "sometimes contributors" to get more actively involved.

Yea, I've been going back and forth on it. For the time being at least I think we should try this out and see how it works. If we decide we really want to limit it, then we should probably at a minimum run our own bot to sidestep the private member issue completely.

Choose a reason for hiding this comment

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

Even if I asked to wait, I concur with Alex "because it encourages "sometimes contributors" to get more actively involved." :-)

Yea. The main reason I made this PR was because currently mention-bot is ignoring anyone who doesn't have their Python membership as public.

I agree with @dstufft that requiring the Python org right now is not necessary as the vast majority of code is only from core devs due to the code's history. Eventually we will want to add back in the check when we have more code with proper attribution from git, but that will probably take years before it's a real issue.

And in terms of the mention bot, this is an experiment that might be turned off. Basically this was the last "maybe/maybe not" idea that was on the table before the team review of the workflow and where things sit, so trying it for a week now seemed like the best idea prior to asking python-committers what is or is not working. (Plus turning off the bot is simple.)

I'm not sure the specific procedures here now. It seems @Haypo has -1'd this PR, but not for the specific content of the PR just about the idea of tweaking it right now or not. Should I merge this or wait?

@dstufft I actually don't know what @Haypo wants because he said " the workflow is moving too fast" but then said "I concur with Alex".

Since the bot is on and not going away today, I say go ahead and merge since no one, including Victor, seems to think the tweak is bad for the bot itself.

@brettcannon: "@dstufft I actually don't know what @Haypo wants"

I fear that mention-bot will start spamming people who don't want to get notified by all these new CPython PR. We should help these people to unsubscribed or be blacklisted. Maybe write an email to python-dev to announce mention-bot and explain how to unsubscribe? At least, you already partially did that on the python-committers list, thank you for that!

In the meanwhile, the quick & hard way to work around spam is to mute the whole cpython project.