[openstreetmap/openstreetmap-website] [WIP] Allow reporting of abusive users to moderators or admins (#1576)
notifications at github.com
Thu Mar 1 01:29:57 UTC 2018
> Agree this functionality shouldn't be to report editing errors, but there will be a need to report abusive changeset comments (eventually)
There's definitely scope to widen the list of things that can be reported. I would certainly consider adding changeset comments, note comments and traces in followup PRs, but I'm particularly cautious about expanding the scope until we know that the workflow is OK.
> Any discussion on how to approach this yet? Or even that needs to be taken up?
We'll need to suck-it-and-see, but we might need to add more website moderators, if the list of reports is too big for the existing group of moderators and/or administrators to handle. Currently moderator status on the website is a pretty powerful position since it includes being able to create user_blocks, which I'd prefer to tie more closely to DWG membership status. So if we find we need to add a few dozen new website moderators just to handle notes, diary_entries etc, then we'll need more fine-grained roles and permissions. Some foundational code and refactoring would be needed for that, see e.g. https://github.com/openstreetmap/openstreetmap-website/issues/1626
Of course, it's hard to know whether there will actually be an increase in reports being dealt with, since we currently handle most spam etc through existing out-of-band channels (e.g. using IRC, or via DWG) - this just makes the reporting in-band instead of out-of-band. Like I said, probably best to start with a small list of reportable items and see how it goes.
> What's the possible timeline for deployment of this feature?
* Other developers now review this PR. It's sort of half-reviewed since technically the work I was doing was just improving the existing GSoC PR, with a view to taking care of things I would have asked the student to fix (if I had a time machine).
* I can make any changes requested.
* Gets deployed pretty quickly after that.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rails-dev