Changes

Jump to navigation Jump to search
updating org notes to include reminder to mention python events, tweaked some planning info
Line 2: Line 2:     
before
 
before
 
+
* check calendar to see if the meeting place can/should be moved (e.g. to  lounge2.0, electronics lab, etc)
 
* Keep an eye on the number of RSVPs at [http://www.meetup.com/ChicagoPythonistas/ ChicagoPythonistas Meetups] and [http://www.meetup.com/Pumping-Station-One/ PS:One Meetups]. This will give you an idea of how many people will show up. We haven't overloaded the space yet, but we've come close a couple of times. It is a bridge we might have to cross.
 
* Keep an eye on the number of RSVPs at [http://www.meetup.com/ChicagoPythonistas/ ChicagoPythonistas Meetups] and [http://www.meetup.com/Pumping-Station-One/ PS:One Meetups]. This will give you an idea of how many people will show up. We haven't overloaded the space yet, but we've come close a couple of times. It is a bridge we might have to cross.
 
* Write the wiki url on the whiteboard, and the info for the irc channel. also an arrow pointing to the ceiling for people to find the wifi password.
 
* Write the wiki url on the whiteboard, and the info for the irc channel. also an arrow pointing to the ceiling for people to find the wifi password.
Line 8: Line 8:  
* move tables around, perhaps.
 
* move tables around, perhaps.
 
* be sure to understand the [[Python Office Hours/Code of Conduct]]
 
* be sure to understand the [[Python Office Hours/Code of Conduct]]
 +
* check for python-related events happening soon
    
during
 
during
 
+
* if handy, have a computer to project an etherpad or something like that during office hours for pasting notes and urls. it can go with introductions
* write python office hours and an arrow up stairs on the little whiteboard in the entry way.
   
* say hello and introduce yourself as the host. explain the goal of the event. introduce people to the code of conduct and provide a url.
 
* say hello and introduce yourself as the host. explain the goal of the event. introduce people to the code of conduct and provide a url.
 
* maybe ask what people are interested in and get people to raise their hands if they can answer questions/have questions. I should write down an agenda because I get tongue tied sometimes in a big crowd!
 
* maybe ask what people are interested in and get people to raise their hands if they can answer questions/have questions. I should write down an agenda because I get tongue tied sometimes in a big crowd!
 
* make sure new people sign waivers
 
* make sure new people sign waivers
* give a tour to new folks some time during the event
+
* give a tour to new folks some time during the event (if you can)
* make sure to keep an ear and eye out for doorbells because we get people coming in starting a little before the event to during. You can use doormon to !open the door for a few seconds, but check down the stairs to make sure people don't get lost.
+
* make sure to keep an ear and eye out for doorbells because we get people coming in starting a little before the event to during.
 
* every now and then look around to see how everyone is doing. If anyone looks stuck, you might ask them to see what they are working on and whether they have questions. If anyone is causing a problem (this rarely happens! maybe only once!), ask them gently to leave and let me or someone else on the board know about it.)
 
* every now and then look around to see how everyone is doing. If anyone looks stuck, you might ask them to see what they are working on and whether they have questions. If anyone is causing a problem (this rarely happens! maybe only once!), ask them gently to leave and let me or someone else on the board know about it.)
  
Domain Admins
598

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu