User:PesachZ/SyncScratch View history

VisualWikitext
m (Copying text of wiki page for coparison with the "West Virginia/AM/Editor/Area" page)
m (Copying text of wiki page for coparison with the "Ohio/Training Raids/Sample Schedule" page)
Line 1: Line 1:
<!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------
== T-3 months ==
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------                                                -------------------------------------    INSTRUCTIONS    -    START READING HERE    -------------------------------------                                                --------------------
-------------------------------------------------------------------------------------
-- Country/State Managers: Cancel this edit and use the link at the top of the table.


-------------------------------------------------------------------------------------
* Lock up two-week raid window
** Identify holidays to avoid, both [http://www.timeanddate.com/holidays/us/ US] and [http://www.timeanddate.com/holidays/israel Israel]
** Find dates planning team is unavailable
** Select dates
* Confirm Champs have dates and have blocked them off on master raid list
** Don't want to compete with a bigger raid
* Announce raid
** Use ROUGH dates as calendar can shift downrage
** Say you're taking applicants, leave time to apply
*** Two weeks is a good window
*** Make sure to PM editors who don't check GHO often
*** Remind at the halfway mark of the signup window
* Notify accepted editors
** PM people directly
** Update forum post saying applications are closed
*** Possibly list people in raid?
* Create Raid hangouts
** Participants
** Planning/Mentors
* Make raid zone map
** Cut up overall area into proper number of areas
** Get "coloring" slides from Terry that were made by RickZabel and color appropriately
** USE FOUR-POINT POLYGONS
** Previous feedback is one editor per area is a good thing
** 220 sq miles of basemap is a lot.  Maybe do half that?
** Have Terry create raid script
** Have Champs send link for raid map to Orbit
* Send out request for mentors
** GLR AM hangout, forum posts
** Consider going outside region for mentors
** Closeout feedback said 1:1 ratio of mentors to mentees was ideal


-- Editors: To add yourself to this Area Manager table, copy and paste the following
== T-2 Months ==


-- template into the space below with the other {{AM/Editor|...}} templates. Add
* Workshops
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)
** PROACTIVE PLANNING
-------------------------------------------------------------------------------------
*** Find out what organizes want covered, get right people to teach
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}
** Possible topics
-------------------------------------------------------------------------------------
*** Raid 101: useful tools (validator, toolbox, JAI, Color Highlighter, raid overlay, localizations for ohio)
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"
*** Raid 102: how to attack basemap (ordered criteria come in helpful here)
-------------------------------------------------------------------------------------
*** Raid 201: places
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------
*** Raid 201: Junction Angles Intro
================================================================================-->|-
*** Raid 202: Road types (not FC!)
{{AM/Editor|Lord_of_Xibalba|2|North Central WV|WV resident editor}}
*** Raid 203: Closures
{{AM/Editor|danofsatx|4|Ohio Valley north of Wheeling
*** Raid 204: turn/segment restrictions
|WV Native / TX Resident|gho= <span style="font-size:88%”>[https://plus.google.com/u/0/101163268272263890541/about GHO: Dan]</span>|pic=File:Danofsatx.JPG}}
*** Raid 205: house numbers
{{AM/Editor|gunnargsd|5|WV Northern panhandle|NW Ohio Large AM|gho= <span style="font-size:88%”>[https://plus.google.com/u/0/108369821571063976266/about GHO: Dave]</span>|pic=File:Gunnargsd.jpg}}
*** Raid 206: divided roads
{{AM/Editor|kwrigh01|4|Eastern WV|Live just into VA and Travel WV a lot for work}}
*** Raid 207: AGCs
{{AM/Editor|mtb2314|4|Davis area|Maryland native, spent a lot of time in WV. AM in MD, WV, and MA.}}
*** Raid 301: smudged cities
{{AM/Editor|jbucklee|3|Parkersburg/Western WV|WV Native/DC Metro Resident/MD Heavy Traveler|gho=bretcarr|pic=File:Jbucklee.jpg}}
*** Raid 302: Routing basics
{{AM/Editor|JasonN899|4|Eastern Panhandle, Northern & Central MD|MD Native|gho= <span style="font-size:88%”>[https://plus.google.com/117937605575546402255/about GHO: Jason N]</span>|pic=File:JasonN899.jpeg}}
*** Raid 303: Keep/turn/exit
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
*** Raid 304: U-turns
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------
*** Raid 305: interchanges
-------------------------------------------------------------------------------------
*** Raid 306: diagnosing routing issues
-------------------------------------------------------------------------------------
*** Raid 307: Functional Classification
--></includeonly>
*** Raid 308: Text-to-speech (abbreviations, etc)
*** Raid 309: Area Manager basics (what role is and isn't, expectations)
*** Raid 401: Freeways
*** Raid 402: Wiki editing
*** Raid 403: Tunnels/overpasses/bridges (elevation, splitting segmetns)
*** Raid 404: Wayfinder
*** Raid 405: Detour Prevention
*** Raid 406: State Manager intro (role, expectations)
 
== T-1 Month ==
 
* Final check with Champs that our dates are good and don't overlap
** Do NOT do anything else until you know dates are good
* Announce final dates to participants
* Make sure areas get submitted in plenty of time
** Get entire raid area assigned to all editors
** Ask it to run four weeks to leave padding
* Raid wiki
** Feedback said previous wikis were good, so consider them as a starting point
* Update state wiki
** Try to make sure all guidance is fresh before you start
* Send reminders of dates to get excitement up, get chatter going in the GHO
* Host workshops
** Restrict membership to raiders during session
** Share widely afterwards (orbit has a lot of interest, for example)
 
== T-1 week ==
 
* Areas go live!
** Make sure everyone has area, send in high-priority requests to get any people missing fixed
 
== Raid Start (T-0) ==
 
* Make sure as many mentors as possible can be there when the gun goes off
* If it's a slow start, may have lost momentum for entire raid
* Proactive mentors
** Feedback is mentors should not be passive!
** Mentors should actively ask who is editing when they "check in", and then walk their areas
** Try to spot as many learning opportunities as possible
* Raid promotions
** Remind mentors to be watching for people going above/beyond
 
== Post-Raid ==
 
* Host closeout meeting
** Come with specific questions of what worked/didn't work in case people are reluctant to chip in at beginning
** Do as little as possible, organizers are just facilitators
* Post raid scoreboard
* Announce raid promotions
 
== Workshop Hangouts ==
 
Ohio did one hangout per topic in the past. To peruse what was covered:
 
* [https://hangouts.google.com/group/WiUIfPgM4v7jeP673 Extensions/Places]
* [https://hangouts.google.com/group/kzlqn5FzTJ0J8kEx2 WMECH/Wayfinders]  
* [https://hangouts.google.com/group/di3oOupw9M7QtY7q1 Functional Classification]
* [https://hangouts.google.com/group/EFY1uZKLYJpXYsGS2 MapRaid Triage]
* [https://hangouts.google.com/group/r1XwuafYTePftNM93 Freeway Editing]

Revision as of 01:53, 20 September 2016

T-3 months

  • Lock up two-week raid window
    • Identify holidays to avoid, both US and Israel
    • Find dates planning team is unavailable
    • Select dates
  • Confirm Champs have dates and have blocked them off on master raid list
    • Don't want to compete with a bigger raid
  • Announce raid
    • Use ROUGH dates as calendar can shift downrage
    • Say you're taking applicants, leave time to apply
      • Two weeks is a good window
      • Make sure to PM editors who don't check GHO often
      • Remind at the halfway mark of the signup window
  • Notify accepted editors
    • PM people directly
    • Update forum post saying applications are closed
      • Possibly list people in raid?
  • Create Raid hangouts
    • Participants
    • Planning/Mentors
  • Make raid zone map
    • Cut up overall area into proper number of areas
    • Get "coloring" slides from Terry that were made by RickZabel and color appropriately
    • USE FOUR-POINT POLYGONS
    • Previous feedback is one editor per area is a good thing
    • 220 sq miles of basemap is a lot. Maybe do half that?
    • Have Terry create raid script
    • Have Champs send link for raid map to Orbit
  • Send out request for mentors
    • GLR AM hangout, forum posts
    • Consider going outside region for mentors
    • Closeout feedback said 1:1 ratio of mentors to mentees was ideal

T-2 Months

  • Workshops
    • PROACTIVE PLANNING
      • Find out what organizes want covered, get right people to teach
    • Possible topics
      • Raid 101: useful tools (validator, toolbox, JAI, Color Highlighter, raid overlay, localizations for ohio)
      • Raid 102: how to attack basemap (ordered criteria come in helpful here)
      • Raid 201: places
      • Raid 201: Junction Angles Intro
      • Raid 202: Road types (not FC!)
      • Raid 203: Closures
      • Raid 204: turn/segment restrictions
      • Raid 205: house numbers
      • Raid 206: divided roads
      • Raid 207: AGCs
      • Raid 301: smudged cities
      • Raid 302: Routing basics
      • Raid 303: Keep/turn/exit
      • Raid 304: U-turns
      • Raid 305: interchanges
      • Raid 306: diagnosing routing issues
      • Raid 307: Functional Classification
      • Raid 308: Text-to-speech (abbreviations, etc)
      • Raid 309: Area Manager basics (what role is and isn't, expectations)
      • Raid 401: Freeways
      • Raid 402: Wiki editing
      • Raid 403: Tunnels/overpasses/bridges (elevation, splitting segmetns)
      • Raid 404: Wayfinder
      • Raid 405: Detour Prevention
      • Raid 406: State Manager intro (role, expectations)

T-1 Month

  • Final check with Champs that our dates are good and don't overlap
    • Do NOT do anything else until you know dates are good
  • Announce final dates to participants
  • Make sure areas get submitted in plenty of time
    • Get entire raid area assigned to all editors
    • Ask it to run four weeks to leave padding
  • Raid wiki
    • Feedback said previous wikis were good, so consider them as a starting point
  • Update state wiki
    • Try to make sure all guidance is fresh before you start
  • Send reminders of dates to get excitement up, get chatter going in the GHO
  • Host workshops
    • Restrict membership to raiders during session
    • Share widely afterwards (orbit has a lot of interest, for example)

T-1 week

  • Areas go live!
    • Make sure everyone has area, send in high-priority requests to get any people missing fixed

Raid Start (T-0)

  • Make sure as many mentors as possible can be there when the gun goes off
  • If it's a slow start, may have lost momentum for entire raid
  • Proactive mentors
    • Feedback is mentors should not be passive!
    • Mentors should actively ask who is editing when they "check in", and then walk their areas
    • Try to spot as many learning opportunities as possible
  • Raid promotions
    • Remind mentors to be watching for people going above/beyond

Post-Raid

  • Host closeout meeting
    • Come with specific questions of what worked/didn't work in case people are reluctant to chip in at beginning
    • Do as little as possible, organizers are just facilitators
  • Post raid scoreboard
  • Announce raid promotions

Workshop Hangouts

Ohio did one hangout per topic in the past. To peruse what was covered:

Retrieved from "https://beta.waze.com/wiki/USA/index.php?title=User:PesachZ/SyncScratch&oldid=149858"