[GSoC] Moderation Queue for osm.org

Dan S danstowell+osm at gmail.com
Tue Mar 17 08:04:57 UTC 2015


2015-03-17 4:56 GMT+00:00 Yos Riady <yosriady at gmail.com>:
>> In the first instance it's more about diary entries and comments than
>> about changesets, though we can consider extending to include that if there
>> is enough time. Serge (the mentor) has the details.
>
> Do you mean to say that most of the vandalism happening as diary entries and
> comments? How are map vandalism currently handled by the OSM admins?

Hi Yos,

I'm mostly just a user here - I develop a bit, but I do not deal with
admin/spam issues - but my perspective is this: diary/comment spam is
much more common because spammers can use the same methods as they use
for spamming blogs and wikis. Spam in the form of OSM map edits is
much more of a "specialist" job. As a result, as a user I see far more
spam in diaries and comments (oh and maybe Notes too) than in map
edits.

However, map edit spam does happen, and it would make a lot of sense
to design a moderation system that encompassed it, of course. ... And
that might be the most interesting part of the design problem!


>> Well reporting will be done from existing views I imagine but yes new
>> views will be needed for presenting moderation requests to admins.
>
>
> Yes, I agree. I'm thinking of creating a proper dashboard for the admins to
> handle the moderation requests. I'm currently looking at existing support
> ticket systems as references for the dashboard. Since the features that will
> be implemented largely depends on the needs of the admins and users, I feel
> I need to engage them in discussion. How do you recommend I approach my
> engagement with the wider OSM community?

Tricky question! The OSM community doesn't really focus on one central
discussion place. There's the "talk" mailing list (plus
country-specific e.g. "talk-gb"). Also you might try blogging in your
user-diary - there are quite a few people who read and respond to
those. I don't have a specific great suggestion though.

Best
Dan


> I've created a draft proposal for my GSoC application for this project which
> can be viewed here and here.
> The scope, features, and timeline of the project are defined; although I'd
> love to discuss with Serge, Tom, and the other developers to hear your
> thoughts on what features are needed/should be prioritized. Also, I'd be
> happy to accept advice/constructive criticism on how to improve my project
> proposal!
>
> Thank you for your time!
>
>
> On Mon, Mar 16, 2015 at 12:59 AM, Tom Hughes <tom at compton.nu> wrote:
>>
>> On 15/03/15 16:52, Yos Riady wrote:
>>
>>> As I understand it from the one-line summary, this project is about
>>> adding a reporting and moderation system for the osm website. It'll mean
>>> adding a new "Report" page where events and users can be reported and a
>>> dashboard for admin users to receive and process these reports. Having
>>> made some edits on the openstreetmap website, I can understand why this
>>> feature is very important. In fact, I'm surprised we don't have that
>>> already. From what I understand, the detailed implementation involves:
>>>
>>>   * Creating a new polymorphic model that points to either a ChangeSet
>>>     or a User model that is being reported
>>
>>
>> In the first instance it's more about diary entries and comments than
>> about changesets, though we can consider extending to include that if there
>> is enough time. Serge (the mentor) has the details.
>>
>> The key point is the idea of a polymorphic model anyway, as that will
>> allow us to support reporting of anything.
>>
>>>   * Views and controllers to support reporting and admin
>>> approval/moderation
>>
>>
>> Well reporting will be done from existing views I imagine but yes new
>> views will be needed for presenting moderation requests to admins.
>>
>> Tom
>>
>> --
>> Tom Hughes (tom at compton.nu)
>> http://compton.nu/
>
>
>
> _______________________________________________
> rails-dev mailing list
> rails-dev at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/rails-dev
>



More information about the rails-dev mailing list