Difference between revisions of "User:Voludu2/Welcoming New Editors"

From Wazeopedia
m (Welcome-to-editing PM)
Line 22: Line 22:
 
I would like to see you connected to the community of map editors sharing tips, tricks, and best practices for really making the map work for wazers. Please reply to this PM to find out more, or [url=https://discord.me/NorthEast_Region]join us as we chat on Discord[/url]. And remember to check in on chat the next time you edit -- introduce yourself as a new editor, and you'll get plenty of help.
 
I would like to see you connected to the community of map editors sharing tips, tricks, and best practices for really making the map work for wazers. Please reply to this PM to find out more, or [url=https://discord.me/NorthEast_Region]join us as we chat on Discord[/url]. And remember to check in on chat the next time you edit -- introduce yourself as a new editor, and you'll get plenty of help.
  
Thanks for your help with the map.</blockquote>
+
Thanks for your help with the map!</blockquote>
  
 
Some useful references:
 
Some useful references:

Revision as of 20:47, 6 March 2018

This is a work in progress. Please help work this out at: https://www.waze.com/forum/viewtopic.php?f=276&t=108515 or to type the right stuff right here.

When you see red roads, unnecessary parking lots, and other common editing mistakes -- celebrate. When you see a really basic question in chat -- joyfully welcome the new editor.

We all want to see these new editors switch from messing up the map to fixing up the map as quickly as possible. How do we get important information to them as quickly as possible?

What to do

  • When an editor asks a basic question like "How do I stop making this parking lot?", don't answer. Visit. If they don't know that, they don't know much. But you can help. Share the Welcome page or Rank 1 skill slides. Inspect their work. Get them to use permalinks. Point them at relevant sections of Best Practices or Common editing mistakes.
  • When you spot a new editor red-handed making errors anywhere on the map, try to flag them down no matter where they are on the map.
    • If they are deleting or otherwise breaking roads, get a high-level editor to help lock the area down immediately.
    • Otherwise, try the usual tedious and generally ineffective methods of flagging down new editors: "dance party", "road art", "delete their work", and "surround them with URs".
  • When you see an editor's recent work, but can't find the editor in chat, send a friendly "welcome to waze editing" message on the forum. Then forward that message to the state manager in that area.
  • When an editor doesn't answer your PM, and doesn't seem to be learning, contact the state manager again, and if you don't get a response from the state manager, contact a regional coordinator.

Boilerplate


Welcome-to-editing PM

Hello <insert name here>!

[url=https://wiki.waze.com/wiki/Waze_Map_Editor/Welcome]Welcome to Waze Editing[/url]! We can really use the help in <region>.

I would like to see you connected to the community of map editors sharing tips, tricks, and best practices for really making the map work for wazers. Please reply to this PM to find out more, or [url=https://discord.me/NorthEast_Region]join us as we chat on Discord[/url]. And remember to check in on chat the next time you edit -- introduce yourself as a new editor, and you'll get plenty of help.

Thanks for your help with the map!

Some useful references:

[list]
[*] [url=http://bit.ly/Rank1SKills]Rank 1 skill slides[/url]
[*] [url=https://wiki.waze.com/wiki/Map_Editor_Interface_and_Controls]Map Editor Interface and Controls[/url]
[*] [url=https://wiki.waze.com/wiki/Best_map_editing_practice]Best Practices[/url]
[*] [url=https://wiki.waze.com/wiki/Common_editing_mistakes]Common Mistakes[/url]
[*] [url=https://wiki.waze.com/wiki/Creating_and_editing_road_segments]Creating and editing road segments[/url]
[/list]