Changes

Jump to navigation Jump to search
324 bytes added ,  01:04, 22 September 2018
no edit summary
Line 1: Line 1:  
So, you want to start a class / workshop / event? Bully for you, you're thinking like a do-ocrat! Here's what you should probably do and think about next:
 
So, you want to start a class / workshop / event? Bully for you, you're thinking like a do-ocrat! Here's what you should probably do and think about next:
    +
== Where's the Calendar ==
 +
 +
Here it is: [http://www.google.com/calendar/embed?src=hhlp4gcgvdmifq5lcbk7e27om4%40group.calendar.google.com&ctz=America/Chicago PS:One Google Calendar]
    
== Initial Steps ==
 
== Initial Steps ==
Line 6: Line 9:  
** Decide what you want and don't want to teach. Set a scope that makes sense to you.
 
** Decide what you want and don't want to teach. Set a scope that makes sense to you.
 
* Come up with a good name.
 
* Come up with a good name.
** This can't be stressed enough. A good name can make the difference between one attendee and a room of attendees.
      
== Establish a Date ==
 
== Establish a Date ==
 
* Pick a day and time that works for you and has space available on the PS1 calendar.
 
* Pick a day and time that works for you and has space available on the PS1 calendar.
** Ask [email protected] to grant you read/write access to the calendar. (This should no longer be required if your google account is a member of the members list).
+
** Sending an email to [email protected] asking to grant you read/write access to the calendar.  
 
** Warning! Don't try to ask the mailing list for a date that "works for everyone" down that path lies madness and obnoxiously long threads with no definitive answers. This is your project, make a command decision.
 
** Warning! Don't try to ask the mailing list for a date that "works for everyone" down that path lies madness and obnoxiously long threads with no definitive answers. This is your project, make a command decision.
 
** Pick a day at least two (or more) weeks in the future so you can generate interest and people can plan to attend.  
 
** Pick a day at least two (or more) weeks in the future so you can generate interest and people can plan to attend.  
** Remember, PS1 is now large enough that several events can take place at the same time.
  −
      
== Write up a class description: ==
 
== Write up a class description: ==
* Write something brief but flowery, and make sure to include the following things at the bottom of your post (seriously, use this exact format or you're going to get a lot of dumb questions from people who can't read anything not in bullet points):
+
* Write something brief, and make sure to include the following things at the bottom of your post (seriously, use this exact format or you're going to get a lot of dumb questions from people who can't read anything not in bullet points):
 
** Who: who the class is intended for (the public, members only, beginners, intermediate, etc)
 
** Who: who the class is intended for (the public, members only, beginners, intermediate, etc)
 
** Cost (if it's free, say that it's free, or people will ask)
 
** Cost (if it's free, say that it's free, or people will ask)
** Where it is: include ps1's address, which room, etc
+
** Where it is: include PS1's address, which room, etc
 
** (If you are going to use the Electronics Lab for events, please also subscribe to the electronics lab calendar (http://www.google.com/calendar/[email protected]&ctz=America/Chicago). Duplicate your event from the PS1 calendar by clicking the duplicate button in the more action drop down to create a reservation of the Electronics lab, and set your duplicated event to the Electronics lab calendar.)
 
** (If you are going to use the Electronics Lab for events, please also subscribe to the electronics lab calendar (http://www.google.com/calendar/[email protected]&ctz=America/Chicago). Duplicate your event from the PS1 calendar by clicking the duplicate button in the more action drop down to create a reservation of the Electronics lab, and set your duplicated event to the Electronics lab calendar.)
** When it is
+
** When it is: Date and time. Start time and end time might be nice, too.
 
** What you'll be teaching, what the event is about, etc
 
** What you'll be teaching, what the event is about, etc
 
* Find an appropriate picture to go along with your description (because all blog posts must have pictures!)
 
* Find an appropriate picture to go along with your description (because all blog posts must have pictures!)
Line 31: Line 31:  
** PS1-Public list
 
** PS1-Public list
 
** PS1-Private list
 
** PS1-Private list
** The calendar
+
** The calendar: [http://www.google.com/calendar/embed?src=hhlp4gcgvdmifq5lcbk7e27om4%40group.calendar.google.com&ctz=America/Chicago PS:One Google Calendar]
    
* Other places you may want to consider:
 
* Other places you may want to consider:
** The Blog
+
** The Blog (which means a post on the web site)
** Facebook, make an event.
+
** Facebook, make it an event.
 
** Twitter
 
** Twitter
 
** Other local hackerspaces' mailing lists (W88 and SSH for starters)
 
** Other local hackerspaces' mailing lists (W88 and SSH for starters)
 
** Enthusiast mailing lists that talk about stuff you're interested in
 
** Enthusiast mailing lists that talk about stuff you're interested in
 
** If your event is general interest enough, consider local event blogs like chicagoist, or local specialty blogs
 
** If your event is general interest enough, consider local event blogs like chicagoist, or local specialty blogs
** The PS1 meetup group or Eventbrite or similar
   
** Make blog / similar blogs
 
** Make blog / similar blogs
 +
** Eventbrite or Meetup or similar: Meetup.com https://wiki.pumpingstationone.org/Meetup
    
== Create A Roster of Attendees ==
 
== Create A Roster of Attendees ==
   −
* You'll need to know how many people are coming
+
* You'll want to know how many people are coming
 
* You may want to send out waivers / any special instructions ahead of time
 
* You may want to send out waivers / any special instructions ahead of time
 
* Give your attendees a way of contacting you directly
 
* Give your attendees a way of contacting you directly
Line 52: Line 52:     
* Show up early to make sure everything is in order for your event. Only you know how long that will take.
 
* Show up early to make sure everything is in order for your event. Only you know how long that will take.
* Have waivers ready for nonmembers, anyone new that hasn't signed a waiver before
+
* Have guests or anyone that has not signed a waiver use an electronic (online) waiver if possible. Have paper copies of waivers ready for nonmembers, or anyone new that hasn't signed a waiver before.
* Make it easy for people to find you. Unlock the door, put up signs.
+
* Make it easy for people to find you. Put up signs.
 
* Host your event! Share your enthusiasm for the subject!
 
* Host your event! Share your enthusiasm for the subject!
    
== After the Event ==
 
== After the Event ==
* Make sure your event doesn't leave a mess. Clean up. Take down signs, and lock the door when you leave.
+
* Make sure your event doesn't leave a mess. Clean up. Take down signs, and make sure the door is firmly closed and locked if you had it unlocked/open.
 
* Get feedback from your attendees: what did they get out of the event? What do they think should be done differently?
 
* Get feedback from your attendees: what did they get out of the event? What do they think should be done differently?
    
[[Category:Member Manual]]
 
[[Category:Member Manual]]
1,524

edits

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

Navigation menu