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

From Wazeopedia
(Welcome-to-editing PM: nowiki on discord link)
(30 intermediate revisions by the same user not shown)
Line 4: Line 4:
  
 
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?
 
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?
 
+
__TOC__
 
== What to do ==
 
== What to do ==
* When you spot a new editor red-handed making errors
+
* 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 [[Waze_Map_Editor/Welcome|Welcome page]] or [http://bit.ly/Rank1SKills Rank 1 skill slides].  Inspect their work.  Get them to use [[Waze_Map_Editor#Permalink|permalinks]]. Point them at relevant sections of [[Best_map_editing_practice|Best Practices]] or [[Common editing mistakes]].
** In your editable area
+
* 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.
** outside your editable area
+
** If they are deleting or otherwise breaking roads, get a high-level editor to help lock the area down immediately.
* When you get a request for an answer to a question.
+
** 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 editors recent work, but can't find the editor online
+
* 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, but continues to make common editing errors
+
* 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 friendly welcome-to-editing PM ==
 
<blockquote><nowiki>Hello <insert name here>!  I'm really happy to see someone new editing in the <region> area.  We can really use the help.
 
 
 
Because I would really like to see you make a lot of high-quality edits that improve the waze map, I would like to share with you some of the guidelines that really make the map work.
 
  
The most important guideline is -- work with more experienced waze editors. Open up the chat box and type "Hello!  I'm a new editor in <where you are working at the moment>. Can someone look over what I've been working on?"  Other editors will be glad to see you, and you will learn a lot quicklyIf no-one is around, or if chat is so busy nobody notices your message, try again in a few minutes.
+
== Boilerplate ==
 +
<br />
 +
===Welcome-to-editing PM ===
 +
<blockquote>Hello <insert name here>!   
 +
<nowiki>[url=https://wazeopedia.waze.com/wiki/USA/Waze_Map_Editor/Welcome]Welcome to Waze Editing[/url]!</nowiki>
 +
We can really use the help in <region>.   
  
To get started right, please read about [url=https://wiki.waze.com/wiki/Best_map_editing_practice]Best Practices[/url] and [url=https://wiki.waze.com/wiki/Common_editing_mistakes]Common Mistakes[/url].  And then move on to the [url=https://wiki.waze.com/wiki/Map_Editing_Quick-start_Guide]Quick Start Guide[/url] to gain skill with the editor.
+
Please join the community of waze editors just like you. We share tips, tricks, and best practices for really making the map work for wazers. Please <nowiki>[url=https://discord.me/NorthEast_Region]join us on Discord chat[/url]</nowiki>. Always check in each time you edit. Introduce yourself as a new editor, and you'll get plenty of help.
  
All changes to places (area or point) require approval if you are a level 1 editor, so it might be easiest to gain some experience with road building.
+
Thanks for your help with the map!</blockquote>
In order to help you catch your mistakes (and everyone else's), please consider installing these chrome/firefox tools:[url=https://wiki.waze.com/wiki/Community_Plugins,_Extensions_and_Tools#WME_Validator]Validator[/url] and [url=https://wiki.waze.com/wiki/Community_Plugins,_Extensions_and_Tools#WME_Junction_Node_Fixer_.28JNF.29]Junction Node Fixer[/url].
 
  
I know that you can become a great editor through reading and questioning. I hope to see good things from you on the map.</nowiki></blockquote>
+
Some useful references:
 +
<pre><nowiki>
 +
[list]
 +
[*] [url=http://bit.ly/Rank1SKills]Rank 1 skill slides[/url]
 +
[*] [url=https://wazeopedia.waze.com/wiki/USA/Map_Editor_Interface_and_Controls]Map Editor Interface and Controls[/url]
 +
[*] [url=https://wazeopedia.waze.com/wiki/USA/Best_map_editing_practice]Best Practices[/url]
 +
[*] [url=https://wazeopedia.waze.com/wiki/USA/Common_editing_mistakes]Common Mistakes[/url]
 +
[*] [url=https://wazeopedia.waze.com/wiki/USA/Creating_and_editing_road_segments]Creating and editing road segments[/url]
 +
[/list]</nowiki></pre>
 +
[[Category:Sample responses]]

Revision as of 12:31, 20 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://wazeopedia.waze.com/wiki/USA/Waze_Map_Editor/Welcome]Welcome to Waze Editing[/url]! We can really use the help in <region>.

Please join the community of waze editors just like you. We share tips, tricks, and best practices for really making the map work for wazers. Please [url=https://discord.me/NorthEast_Region]join us on Discord chat[/url]. Always check in each 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://wazeopedia.waze.com/wiki/USA/Map_Editor_Interface_and_Controls]Map Editor Interface and Controls[/url]
[*] [url=https://wazeopedia.waze.com/wiki/USA/Best_map_editing_practice]Best Practices[/url]
[*] [url=https://wazeopedia.waze.com/wiki/USA/Common_editing_mistakes]Common Mistakes[/url]
[*] [url=https://wazeopedia.waze.com/wiki/USA/Creating_and_editing_road_segments]Creating and editing road segments[/url]
[/list]