Discussion: Challenge Flagging System Improvements

Context

We have received a lot of feedback on the topic of accountability and responsibility of Challenge authors in the past few months. A recurring topic is the Challenge flagging system:

• Some people would love to see a voting system, either before Challenges go live or as they are being used
• Some people think the barrier is too high
• The feature is hard to discover (but see documentation
• There is a mental disconnect between placing a flag and the report appearing in a Github issue
• There are three avenues of potential communication about a flagged Challenge:
  1. MapRoulette's native messaging system
  2. The Github issue
  3. OSM's messaging system

Potential Improvements

Flagging UX improvements

Several things we could address separately or in parallel:

• Make the communication / "chat" feature more visible
• Have a public (or accessible to logged in users) account page for every MR user where all challenges and communication options, account status, mapping work, are consolidated

Focus on lower hanging fruit pending MR redesign

Challenge authors account limitations

If a Challenge author's Challenges are flagged, their MapRoulette account could be limited, for example:

• Lose the ability to create new Challenges
• Any other Challenges of theirs are disabled or flagged
• They need to get in touch with ...someone... to get their account in good standing again