User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Ohio/Training Raids/Sample Schedule" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(465 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== T-3 months ==
<!-- ========================
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
==============================
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>


* Lock up two-week raid window
These rows fill the major Event table, and are modified using the template {{tl|Event/Item}}. If you are working on a Major Event in {{RootPage2}}, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the <code>updated=</code> parameter.
** 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


== T-2 Months ==


* Workshops
This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically  the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).
** 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 ==
==Accepted parameters:==


* Final check with Champs that our dates are good and don't overlap
*<code>name=</code> The name of the event.
** Do NOT do anything else until you know dates are good
*<code>area=</code> The county or are the event takes place in.
* Announce final dates to participants
*<code>date=</code> The estimated date(s) this event happens on.
* Make sure areas get submitted in plenty of time
*<code>road=</code> The main road(s) affected by this event.
** Get entire raid area assigned to all editors
*<code>pl=</code> A [[permalink]] to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
** Ask it to run four weeks to leave padding
*<code>source=</code> A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
* Raid wiki
*<code>status=</code> Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
** Feedback said previous wikis were good, so consider them as a starting point
**<code>not submitted</code> produces a red background
* Update state wiki
**<code>submitted</code> produces a light green background
** Try to make sure all guidance is fresh before you start
**<code>in progress</code> produces an orange background.
* Send reminders of dates to get excitement up, get chatter going in the GHO
*Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
* Host workshops
*<code>updated=</code> the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.
** Restrict membership to raiders during session
** Share widely afterwards (orbit has a lot of interest, for example)


== T-1 week ==


* Areas go live!
The updated parameter (<code>|updated=YY/MM(/DD)|</code>) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).
** 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
The <code>|date=|</code>, and <code>|updated=|</code> parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.
* 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
For example an Event row should look like this;
** 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 ==
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


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


* [https://hangouts.google.com/group/WiUIfPgM4v7jeP673 Extensions/Places]
If there are multiple editors it should look like this
* [https://hangouts.google.com/group/kzlqn5FzTJ0J8kEx2 WMECH/Wayfinders]
 
* [https://hangouts.google.com/group/di3oOupw9M7QtY7q1 Functional Classification]
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
* [https://hangouts.google.com/group/EFY1uZKLYJpXYsGS2 MapRaid Triage]
 
* [https://hangouts.google.com/group/r1XwuafYTePftNM93 Freeway Editing]
 
 
'''Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box.'''
————————————————————————————————————
 
 
 
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
 
==TO EDIT THIS TABLE CLICK HERE >> ==
</noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -----
======                              ======
======                              ======
======                              ======
====== DO NOT MODIFY ABOVE THIS LINE ====-->
{{Event/Item|name=New Years Celebration|area=NYC|road=Times Sq/Coney Island|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1716991474|date=12/31-01/01 annual|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=NYC 1/2 Marathon & St. Patricks' Day Parade|date=03 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=339510355|area=NYC|road=5 Boroughs|status=submitted|updated=2017/02/09|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
{{Event/Item|name=July 4th Celebration|area=NYC|status=submitted|updated=2017/02/12|Rfrsw101|jdelosa|johnsninja58|PesachZ|road=FDR Dr|date=07/04 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1864894199|source=http://www.nyc.gov/html/dot/html/motorist/wkndtraf.shtml}}
 
{{Event/Item|name=Summer Streets|road=Park Ave|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1984749524|source=http://www.nyc.gov/html/dot/summerstreets/html/home/home.shtml|date=08 First 3 Sundays|area=NYC|status=submitted|updated=2017/02/10|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
{{Event/Item|name=West Indian Day Parade|date=09 Labor Day annual|area=Kings|road=Eastern Pkwy, Classon-Rochester St Johns-Empire|source=http://maps.nyc.gov/streetclosure/|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1605830763|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/10}}
 
{{Event/Item|name=TD 5 Boro Bike Tour|area=NYC|date=05 First Sunday annual|road=5 Boroughs|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=790135118|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=NYC TCS Marathon|area=NYC|date=11 First Weekend annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=0|road=5 Boroughs|source=http://www.tcsnycmarathon.org/race-day/course|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/07}}
 
{{Event/Item|name=UN General Assembly|area=NYC|road=East Midtown|date=09 Last Two Weeks Annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1895099030|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=Macy's Thanksgiving Day Parade|area=NYC|road=Herald Square|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1774745119|date=11 Last Thursday Annual|source=http://social.macys.com/parade/#route|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=Chinese New Year Parades|date=01 or 02 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1190958434|area=NYC|road=Chinatown/8th Avenue/Flushing|status=submitted|updated=2017/02/08|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
=====                                =====
=====                                =====
----- DO NOT MODIFY BELOW THIS LINE ----->
</includeonly>

Latest revision as of 05:15, 19 February 2017

Click here to return to the PesachZ/Closures Subpage

These rows fill the major Event table, and are modified using the template {{Event/Item}}. If you are working on a Major Event in PesachZ, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the updated= parameter.


This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).

Accepted parameters:

  • name= The name of the event.
  • area= The county or are the event takes place in.
  • date= The estimated date(s) this event happens on.
  • road= The main road(s) affected by this event.
  • pl= A permalink to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
  • source= A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
  • status= Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
    • not submitted produces a red background
    • submitted produces a light green background
    • in progress produces an orange background.
  • Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
  • updated= the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


The updated parameter (|updated=YY/MM(/DD)|) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


The |date=|, and |updated=| parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


For example an Event row should look like this;

{{Event/Item|date=14/10|in progress|username|updated=14/08}}


If there are multiple editors it should look like this

{{Event/Item|date=14/10|in progress|username1|username2|updated=14/08}}


Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box. ————————————————————————————————————


The actual contents of this page will only be visible in the Major Events table, or when editing this page.

TO EDIT THIS TABLE CLICK HERE >>