Dilum Aluthge

> A member of an organisation may not have write access to all repos of the organisation. Correct. However, the current behavior of Registrator is: if a user is a...

> Oh, so it doesn't check anyway the actual permissions in the specific repo. It does both. It checks the public members of the org. But also it checks who...

> There's also outside collaborators to think about. Yeah. Those should get picked up in the "also it checks who has push access to the repo".

> Yeah but you can't do that check without push access of your own... Yeah exactly.

Personally I would vote to just leave things the way they are.

Maybe one day GitHub will give us an API for getting a list of users with push access without needing push access ourselves.

Maybe post in the `#pkg-registration` channel on the [Julia Slack](https://julialang.org/slack/)? The General registry has a very high rate of GitHub notifications, so these things can get missed.

FWIW, I'd be fine with changing this in the future to require that these notices go in the third party notice file.

If this is for the General registry, just comment "please close", and in 30 days the PR will automatically be closed. No need for an additional Registrator feature.

@logankilpatrick @ericphanson Currently, it looks like these messages are getting posted to the `#new-packages-feed` channel. What do I need to modify in order to get the messages to post to...