Browse Source

Fix organizer tips formatting

Update the format of Example Planning Schedule.

Change-Id: I7eff82a3e6129760c7396e128fba7898af33160a
Marton Kiss 3 years ago
parent
commit
1106ce3d77
1 changed files with 25 additions and 25 deletions
  1. 25
    25
      organizer-tips.md

+ 25
- 25
organizer-tips.md View File

@@ -118,29 +118,29 @@ Example Planning Schedule
118 118
 -------------------------
119 119
 This is an example planning schedule from the SFBay OpenStack User Group.
120 120
 
121
-1. Establish dates and times at least 6 months in advance
122
-2. Schedule speakers, assistants at least a month in advance
123
-3. Schedule tweets and emails to go out 7, 2, 1, and 0 days before the meetup reminding possible attendees of the meetup.  Examples below
124
-  * T-7 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
125
-  * T-2 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
126
-  * T-1 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening tomorrow at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
127
-  * T-0 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening today at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
128
-- Schedule an email to go out to the community mailing list with the same content
129
-  * To: community@lists.openstack.org
130
-  * Subject: [[OpenStack]] SFBay hackathon next Thursday
131
-  * Body: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at
132
-  * #Yahoo Sunnyvale, RSVP via http://meetup.com/openstack, webex avail. More updates via @sarob
133
-4. Book your meeting space at least 1 month in advance
134
-5. Notify security about the meetup and so they can provide directions so
135
-   visitors do not get lost
136
-6. Order the food at least 3 days in advance. A good gauge is about 70% of the
137
-   RSVPs actually show up. Better topics get a higher percentage turnout.
138
-7. Prep the room about an hour before the meetup. Check the AV equipment,
139
-  power strips, seats, food, drink, and white boards are ready to go. Setup
140
-  the video camera, so you know where the static viewing area is. Line up
141
-  the projector screen to be in the picture. Lay down a tape box where the
142
-  speaker should stand. Dial into the audio conference line. If you are using
143
-  webex or youtube, check for connection to the remote server.
144
-8. Post Meetup: After the meeting, you can prepare a summary blog post with
145
-   images, links to video, marketing updates for the OpenStack blog.
121
+    1. Establish dates and times at least 6 months in advance
122
+    2. Schedule speakers, assistants at least a month in advance
123
+    3. Schedule tweets and emails to go out 7, 2, 1, and 0 days before the meetup reminding possible attendees of the meetup.  Examples below
124
+      * T-7 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
125
+      * T-2 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
126
+      * T-1 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening tomorrow at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
127
+      * T-0 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening today at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
128
+    - Schedule an email to go out to the community mailing list with the same content
129
+      * To: community@lists.openstack.org
130
+      * Subject: [[OpenStack]] SFBay hackathon next Thursday
131
+      * Body: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at
132
+      * #Yahoo Sunnyvale, RSVP via http://meetup.com/openstack, webex avail. More updates via @sarob
133
+    4. Book your meeting space at least 1 month in advance
134
+    5. Notify security about the meetup and so they can provide directions so
135
+       visitors do not get lost
136
+    6. Order the food at least 3 days in advance. A good gauge is about 70% of the
137
+       RSVPs actually show up. Better topics get a higher percentage turnout.
138
+    7. Prep the room about an hour before the meetup. Check the AV equipment,
139
+      power strips, seats, food, drink, and white boards are ready to go. Setup
140
+      the video camera, so you know where the static viewing area is. Line up
141
+      the projector screen to be in the picture. Lay down a tape box where the
142
+      speaker should stand. Dial into the audio conference line. If you are using
143
+      webex or youtube, check for connection to the remote server.
144
+    8. Post Meetup: After the meeting, you can prepare a summary blog post with
145
+       images, links to video, marketing updates for the OpenStack blog.
146 146
 

Loading…
Cancel
Save