Open Source Comes to Campus/Meta-organizing/Meta organizer: Difference between revisions

imported>Paulproteus
 
(15 intermediate revisions by 2 users not shown)
Line 11:
If you're reading this, that might be you!
 
Meta-organizer isn't ais title you keep forever; it's ''a relationship you have with a particular event''' rather than a title one keeps forever. It's OK to be a meta-organizer for an event today and be an organizer of a different event tomorrow!
 
Keep reading and you'll see how to be a great meta-organizer for an event.
Line 17:
== How we meta-organize ==
 
OpenHatch maintains a spreadsheet with prospective organizers and schools interested in running aan workshopevent, the status of each upcoming workshopevent, and which meta-organizer us was responsible for making sure that worskhopevent took place. This helps us keep track of who's doing what, where, when.
 
In general, we share this with every person who has been a meta-organizer for an event.
 
=== Workflow ===
 
* AtPeriodically, leastsome oncepeople perwho quarter,have been meta-organizers get together to brainstorm and send emails to prospective event organizers.
* CombTo find event organizers, we look through the list of past volunteervolunteers and organizerorganizers listsand to seepeople who mighthave becontacted willingOpenHatch toexpressing organizeinterest againin or for therunning firstan timeevent.
* We also sometimes look through big lists of computer science organizations (such as this [http://geekfeminism.wikia.com/wiki/List_of_academic_organizations_interested_in_women_in_CS List of academic organizations interested in Women in CS]) to see if any of them might be interested in organizing again or for the the first time.
* Look through our list of companies who have previously offered to host or that we have contacts at and decide who to ask.
* SendFor outeach prospective event, we assign a bunchprospective ofmeta-organizer. That person sends out emails to their potential organizers and venues.
* FollowThey follow up with those who have questions or are up for it.
* The meta-organizer helps the local organizer pick a date for their event and find volunteers, and answers any other questions the organizer has.
* Connect volunteers and venues to pick a date for their workshop.
 
== Strategies for Recruiting Organizers ==
 
The path often looks something like: studentattendee --> TAmentor --> teacherorganizer --> meta-organizer, but that's very rough and often steps are skipped. Lots of teachersmentors don't start off as studentsattendees, for instance, and sometime studentsattendees are ready to jump right into organizing!
 
== Places to look for organizers ==
 
* Look at your recentlist volunteersof listattendees and local mentors, and see if you have repeat volunteers. TheseIf some of them are students at the host institution, folksthey might be up for stepping into the organizer role for aan workshopevent.
* At the beginning of the workshopevent, announce that there will be a table at lunch offor people talkinginterested aboutin organizinghow athe workshopevent ifwas anyoneorganized, isso interestedthat inattendees thatwho are curious can begin to learn about the inner workings of the event.
* Ask past attendees & mentors & organizers! And when you ask, ask for nominations as well. They might know someone perfect.
 
=== Information & Skills Needed ===
 
These are the things you need to know and be able to do to be an effective meta-organizer.
 
=== Growing the Potential WorkshopEvent Organizers & Mentors List ===
 
Every event needs an organizer and some mentors. We need to keep growing the list of people so that people who would enjoy doing that are able to do it!
 
Information needed:
 
* A list of past organizers, friends, volunteers, and anyone you can think to askbe toa organizementor
* A list of past organizers who might be interested in organizing
* A list of colleges/universities you are willing to email people at -- even better if there is a computer club or women in CS organization
* Other humans' suggestions for who to ask
 
Line 52 ⟶ 58:
 
* Ability to ask for help convincingly
* Participation at events where you can recruit people to the list of potential organizers & mentors is hugely helpful
 
=== RecruitingActually Venuesrecruiting +event Sponsorsorganizers ===
 
Information needed:
 
* A list of local tech companies; often but not necessarily RoR shops
* Space / tech requirements for a workshop
* Benefits to hosting a workshops
 
Skills needed:
 
* Research skills to find new venues
* Ability to email people you don't know
* Remembering to follow up
* Following up
* Keeping track of who you've asked, so you can follow up
 
=== Actually recruiting workshop organizers ===
 
Information needed:
Line 83 ⟶ 73:
* Ability to keep track of who's been asked, when, and what they said (spreadsheet!)
 
=== Helping organizers pick a date & create sign-up page ===
=== Matching venues with organizers ===
 
Information needed:
 
* Venue's and organizerOrganizer's availability
* Availability of mentors if you know some who are tentatively interested in attending the workshop
* Where to announce / post when workshop is scheduled
* Knowledge of where to announce the event once it's scheduled (for example, events.openhatch.org)
 
Skills needed:
 
* Tolerance for email back-and-forth (or Google Hangouts meetings/phone calls) to determine date of workshopevent
* Willingness to convince the organizers they need a sign-up page
 
=== Hosting organizer kick-off meeting ===
 
Great events often start with a kick-off meeting between the '''meta-organizer''' and the '''organizer(s)'''. We often do this before the date is picked, but it's OK to do it after the date is picked.
 
Information needed:
Line 103 ⟶ 97:
Skills needed:
 
* Ability to schedule drinksa phone call/coffeevideo chat/meetup with all the organizers and hopefully the mentor
* Excitement forabout RailsBridgeOpenHatch and workshopsOpen Source Comes to Campus events
* Ability to answer questions about organizing
 
=== Making sureHelping the workshoporganizer(s) isget actuallyconnected beingwith plannedmentors ===
 
Every Open Source Comes to Campus event needs mentors. The organizer is fundamentally responsible for getting a mentor involved, but they typically need help finding the mentors. That's where the meta-organizer comes in.
 
Information needed:
 
* List of people's names & email addresses & general info about them, who are possibly interested in mentoring
* Knowledge of what mentoring options are available
* General stuff about mentoring, to answer their questions
 
Skills needed:
 
* Ability to email prospective mentors, preferably with a suggestion of a ''specific'' mentorship task they'd be good at, CC:ing the event organizer(s)
* Willingness to follow up with prospective mentors if they don't reply
* Ability to stay organized with these emails
 
=== Making sure the event is actually being planned ===
 
Information needed:
 
* Date of the workshop
* Whether or not the organizers are planning the workshopevent
 
Skills needed:
 
* Ability to follow up with organizers to make sure things are going okay
* Judgement to determine if one of the organizers is doing all the work, to see if you can help spread the load
* Communication skills to help resolve issues with organizers / mentors / venues should they arise
Anonymous user