├── Aftermath.md
├── Announcement-templates.md
├── CONTRIBUTING.md
├── Class-level-grouping-guide.md
├── Finding-space-sponsors-volunteers-and-students.md
├── Frequently-Asked-Questions.md
├── Guidance-to-Mens-Attendance.md
├── Help-Them-Keep-Learning.md
├── Hosting-venue-questions.md
├── How-to-Improve-Attendance.md
├── Installfest-Tasks.md
├── Letters-to-students.md
├── Local-Organizations.md
├── Meta-Organizer-Cookbook.md
├── Minimum-Viable-Workshop.md
├── Money-Things.md
├── Opinions.md
├── People-Subcommittees-and-GTD.md
├── Post-workshop-feedback-survey.md
├── Pre-workshop-tasks.md
├── README.md
├── Resources-on-Diversity.md
├── Sample-budget.md
├── TA Training.md
├── Teacher-Training.md
├── Templates-and-Materials.md
├── Three-Main-Roles.md
├── Translation.md
├── Venue.md
├── Workshop-Planning-Tasks.md
├── Workshop-Planning-Timeline.md
├── Workshop-tasks.md
└── files
    └── ClojureBridge-logo.svg


/Aftermath.md:
--------------------------------------------------------------------------------
 1 | ### <a name="followup"/> Send follow-ups/thank yous to students, teachers, sponsors, & host space
 2 | * Within 72 hours, email students with:
 3 |  * Links to resources to continue learning
 4 |  * Post-workshop survey link, again
 5 |  * Encouragement to come back and volunteer
 6 | * Email thanks to your teachers, host space, and sponsors
 7 | * Add your students to the ClojureBridge Alumni Google group (send list of email addresses to info@clojurebridge.org).
 8 | 
 9 | ### <a name="writeup"/> Send a writeup of the weekend to the organizer's listserve
10 | * You're surely already on it, but again: https://groups.google.com/forum/#!forum/clojurebridge-workshops
11 | * What went wrong and right?
12 | * Link to the the post-workshop survey results
13 | 
14 | ### <a name="updatewiki"/>Update this wiki with your brilliant discoveries
15 | * Pretty please!
16 | 


--------------------------------------------------------------------------------
/Announcement-templates.md:
--------------------------------------------------------------------------------
  1 | ## Announcement for ClojureBridge.org
  2 | 
  3 | Go to the repository <https://github.com/ClojureBridge/Workshops> and
  4 | file an issue.
  5 | 
  6 | All infos need to make announcement page are in
  7 | [Announcement Template](https://github.com/ClojureBridge/Workshops/blob/master/announcement-template.md).
  8 | Copy this template, fill out and paste to the issue.
  9 | 
 10 | 
 11 | ## Announcement for Students 
 12 | 
 13 | ### ClojureBridgeWorkshop for (constituency). 
 14 | (For example, "women" or "high school students")
 15 | 
 16 | ### When:
 17 | Installfest: (date/times)
 18 | 
 19 | Workshop: (date/times)
 20 | 
 21 | Afterparty: (date/time)
 22 | 
 23 | ### Where:
 24 | Organization/Company name
 25 | 
 26 | Full street address
 27 | 
 28 | City, State/Province
 29 | 
 30 | ### Organizers:
 31 | 
 32 | Organizers
 33 | 
 34 | ### Description: 
 35 | This workshop will be in Location city at Organization/Company name, Full street address, City. _(If applicable, list nearby transit stops, and whether the location is wheelchair accessible.)_
 36 | 
 37 | _If you are focusing on a particular constituency, include text like the following: "This workshop is intended to reach out to women who are new to Clojure. To register, you must identify as a woman. Men, you are welcome to come if you find a woman who wants to learn Clojure who will register and bring you as a guest."_
 38 | 
 39 | In this workshop, we'll take you through building a complete web application using Clojure. By the end of the workshop, you'll have an application on the internet that connects to a database and reads and writes information. We'll meet up Friday night to install all of the software you need, and then spend workshop day learning and writing code. 
 40 | 
 41 | Total programming novices, system administrators, developers in other languages, and folks who attended our previous workshops are all welcome. We'll have 5-7 different classes separated by experience level. Each participant needs to bring his or her own computer.
 42 | 
 43 | When you RSVP you'll be asked a few question about your operating system, level and type of programming experience, and whether you will require childcare. Childcare and private space for nursing or pumping is available -- just let us know.
 44 | 
 45 | (Sometimes people ask if the Friday night installfest is mandatory, and yes, it is! It's a crucial part of the weekend, even if you’ve already gone through the instructions independently. There are a ton of moving parts when setting up a development environment, and the reason that we’re able to get through the curriculum on Saturday is that every single student has had their dev environment checked and has been awarded a sticker for their successes. There are also enough changing parts that even if you’ve been to a workshop in the past, you should attend the Installfest to get re-verified, because this stuff changes almost constantly.)
 46 | 
 47 | We are looking for additional volunteers, both folks who know Clojure to TA and people who are willing to help with logistics. Please sign up here: (link to volunteer registration)
 48 | 
 49 | If you have questions or ideas for us, the best way to get in touch is to email organizer.
 50 | 
 51 | ## Announcement for Volunteers
 52 | 
 53 | ### ClojureBridge Outreach Workshop for (constituency). 
 54 | (For example, "women" or "high school students")
 55 | 
 56 | ### When:
 57 | Installfest: (date/times)
 58 | 
 59 | Workshop: (date/times)
 60 | 
 61 | Afterparty: (date/time)
 62 | 
 63 | ### Where:
 64 | Organization/Company name
 65 | 
 66 | Full street address
 67 | 
 68 | City, State/Province
 69 | 
 70 | ### Organizers:
 71 | 
 72 | Organizers
 73 | 
 74 | ### Description: 
 75 | This workshop will be in Location city at Organization/Company name, Full street address, City. _(If applicable, list nearby transit stops, and whether the location is wheelchair accessible.)_
 76 | 
 77 | Got a desire to either help or teach and some Clojure knowledge to share? Well, great! We need you!
 78 | 
 79 | We're looking for volunteer instructors and TAs, as well as some people to do some light lifting or moving things around and helping with clean up, welcoming and check-ins. Are you a big social networker? Let us know! We also want people posting pics with the hashtag #railsbridge. 
 80 | 
 81 | The curriculum can be found here: https://github.com/ClojureBridge/curriculum
 82 | 
 83 | **Teacher Training**: _(including teacher training details here if they exist)_
 84 | 
 85 | 
 86 | **Here’s the timeline for the day of the workshop**:
 87 | 
 88 | * 9:00-9:30 Sign-in/get coffee/make friends
 89 | * 9:30-10:00 Intro Presentation
 90 |  * While we're doing the opening presentation, we're going to huddle and split students into classes. Therefore, arriving in advance of this meeting is critical.
 91 | * 10:00-10:50 Session 1
 92 | * 11:00-12:00 Session 2
 93 | * 12:00-1:00 Lunch
 94 | * 1:00-2:15 Session 3
 95 | * 2:30-3:30 Session 4
 96 | * 3:30-4:00 Wrap up & final questions
 97 | * 4:00-4:15 Teacher/TA debrief & cleanup
 98 | * 4:30 - ??? After party at TBD (All volunteers get a free drink and a chance to network)
 99 | 
100 | Hope you can join us!
101 | 


--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
 1 | # How to contribute
 2 | 
 3 | Updates to the ClojureBridge organizing guide are welcome and encouraged. We would not have anything without the input from the volunteers who put on workshops.
 4 | 
 5 | Also feel free to make forks of the organizing guide and not contribute back. Make different organizing guides, too. This guide is simply meant to provide suggestions for ClojureBridge workshop organizers.
 6 | 
 7 | 
 8 | ## Getting Started
 9 | * Make sure you have a [GitHub account](https://github.com/signup/free)
10 | * Fork the repository on GitHub
11 | 
12 | ## Making Changes
13 | * Commit changes
14 | * (Add more git guidance?)
15 | 
16 | ## Submitting Changes
17 | * Push your committed changes to your local fork of the repository
18 | * Create a pull request 
19 | * Submit a pull request (PR) to the ClojureBridge/organizing repository
20 | * The ClojureBridge organizing guide team will review and discuss the pull requestin comments on the PR.
21 | * Two curriculum team members must give a thumbs up, then the PR will be accepted.
22 | 
23 | 
24 | # Organizing Guide Team
25 | * Wait, why does the organizing guide team get to say which PRs get accepted?? I'm glad you asked! If you contribute more than two patches, you, too, will become part of the organizing guide team. 
26 | * Organizing guide team members are given commit rights to the curriculum.
27 | * Commit rights are meant for approving PRs, not for making direct commits.
28 | 
29 | 
30 | # Workshop/Chapter organizing guide forks
31 | * Workshops or chapters that are using the main ClojureBridge organizing guide should fork the organizing guide in their chapter's github.
32 | * Give teachers commit rights to the chapter's fork of the organizing guide.
33 | * The submit pull requests to the main organizing guide, if you would like to contribute the changes back.


--------------------------------------------------------------------------------
/Class-level-grouping-guide.md:
--------------------------------------------------------------------------------
 1 | While one of the sometimes toughest parts of organizing a workshop, doing this well can often make the difference between really happy workshop goers/volunteers and frustrated ones. The links to the forms, with important instructions for using them, lives on the [pre-workshop tasks page](Pre-workshop-tasks.md).
 2 | 
 3 | ## Suggested Class Levels
 4 | It can help to try and define the different grouping levels as follows. Feel free to combine/create class levels depending on the folks who sign up for your workshop.
 5 | * Beginner: Has never really worked with any programming languages.
 6 | * Advanced Beginner: Has worked with other programming languages and may be familiar with programming concepts, but has not worked with functional programming, Clojure.
 7 | * Intermediate: Understands programming concepts like functions, loops, classes. May only know about Clojure without having actually used it themselves.
 8 | * Advanced Intermediate: Has written their own programs many times but may not have worked with Clojure, Git or Heroku before.
 9 | * Advanced, no Clojure: Advanced work in another programming language, but new to Clojure.
10 | * Advanced in Clojure: Has written Clojure applications before. Possibly a good candidate for teaching or being a TA.
11 | 
12 | ## Student Grouping
13 | Once students have filled out the form, it should be relatively easy to assign them to a group.  Here's one way to handle grouping:
14 | * Group as many people as possible before the workshop
15 | * Anyone who hasn't taken the survey when they check into the Installfest should take the survey before proceeding to the Installfest
16 | * At workshop check-in, either hand attendees a card with their level, or simple tell them and ask them to remember or write it down
17 | * If someone didn't attend the Installfest and also didn't fill out the form, ask a volunteer to check their install and have them take the survey then.
18 | 
19 | ## Volunteer Grouping
20 | There are a few ways to do this. Follow your heart.
21 | 
22 | ### More Organized/More Prep
23 | **Thursday before Installfest:**
24 | * Based on the survey results, create preliminary volunteer groupings to teach the needed groups. Group sizes should be around 5-7 (bigger groups may be broken down to use the ‘flexible’ volunteers outlined below).
25 | * Create one or two additional ‘flexible’ volunteer groupings to cover attendees who have not filled out the form yet. They may end up as TA’s distributed among other classes, or as their own class, depending on who shows up on the day.
26 | * Send an e-mail to the volunteers, letting them know what Teacher/TA groups you’ve paired them into. While noting that this may change depending on actual attendance on Saturday, also note the potential attendee class level you are thinking of heaving each teacher work with, so they can prepare.
27 | 
28 | **Workshop Morning:**
29 | * Based on the number of attendees in each group, adjust the classes each volunteer grouping will teach as necessary.
30 | * 20 minutes before the introduction speech, take each teacher to their teaching area to get set up.
31 | * Give a TA from each class a card with their level it, and have them stand over to the side while the introduction speech is happening.
32 | * At the end of the opening presentation, have the TAs announce which class levels they are each helping with, and ask the students to go to the appropriate TA.
33 | * If there are several sections of a class level, subdivide the attendees between the TA’s for those classes.
34 | Have the TA’s bring their students to where the teacher is set up.
35 | * Reiterate that people should feel free to swap classes if they'd like.
36 | 


--------------------------------------------------------------------------------
/Finding-space-sponsors-volunteers-and-students.md:
--------------------------------------------------------------------------------
 1 | 
 2 | ## <a name="find_community"/>Identify existing communities to collaborate with
 3 | If you're not already involved with your local Clojure scene, Google is your friend. First find your local Clojure user groups; in some cities [Meetup.com](http://clojure.meetup.com/) is a hub for user groups. Ask the [ClojureBridge mailing list](https://groups.google.com/forum/?fromgroups#!forum/clojurebridge-workshops) if they know anyone in your city.
 4 | 
 5 | In addition to your local tech communities, think about finding organizations that are working with whatever demographic you're focusing on, like professional organizations, chamber of commerce-type organizations, and non-profits. 
 6 | 
 7 | You can find a partial list of local Clojure- and diversity-in-tech-related organizations [here](https://github.com/ClojureBridge/organizing/wiki/Local-Organizations).
 8 | 
 9 | 
10 | ## <a name="find_volunteers"/>Recruit volunteers to teach, TA, and help you organize
11 | Hopefully you have a friend or two helping you out. And maybe a few coworkers? Here are some of the positions you will need to fill:
12 | * Organizers (that’s you!)
13 | * Teacher trainers (might be you, as well)
14 | * Teachers
15 | * TAs
16 | * Installers
17 | * Greeters/door-people/pizza-getters
18 | 
19 | For your first workshop, you’ll probably want to keep it simple and just have two roles: teachers/TAs and greeters/door-people/pizza-getters.
20 | 
21 | The ideal ratio is 1 TA/Teacher to 3 students.
22 | 
23 | If you don’t already have someone who’s handling logistics (signup forms, coordinating with the event host, figuring out lunch, etc.), convince one of the people you find early on to take that role. Don’t be afraid to delegate to point people! Being the point person on something is not more work, just a different set of responsibilities. No one wants to die the painful, stressful death caused by trying to do everything.
24 | 
25 | 
26 | ## <a name="find_space"/>Find a space
27 | Not much you can do without a space, and the space you find will determine how many students you can have at your workshop. Here are a couple ideas for where to find spaces:
28 | * Local companies that use Clojure – this is a great recruiting opportunity for them
29 | * Community colleges
30 | * Community centers
31 | * Coworking spaces
32 | * Advocacy organizations that work with your target group (Workshop for Latinos? See if there’s an immigration advocacy group that would host you. For women? Maybe there’s a women’s business group.)
33 | 
34 | What you’re looking for is a place with classroom seating for 50-80, fast and reliable Internet connectivity, plenty of power sources and, ideally, break-out rooms or separate spaces that can be used when the group breaks out into classes.
35 | 
36 | Consider that participants and volunteers will arrive by a variety of transport modes.  If the space offers free parking, mention that in your event posting and any publicity for the workshop.  Cyclists will appreciate hearing of secure bike parking.  Specify nearby transit stops in your communications to volunteers and attendees.
37 | 
38 | Ask the venue about barriers to wheelchair accessibility, such as staircases, high curbs and narrow doorways.  Potential attendees need to know of these before signing up so include notices of them in your communications also.
39 | 
40 | Remember that you'll also need a space for Teacher Training some time in the week or so prior to the workshop. This will be an easier space to find, since it will be just for teachers and teaching assistants.
41 | 
42 | 
43 | ## <a name="find_sponsor"/>Find a sponsor
44 | This really ties in with finding a space, as your sponsor might be the one to provide with a space. What is a sponsor, you ask? Well, think about the things you need that cost money – the two most common being renting the space and providing your attendees with lunch. If you can get a sponsor to donate the space, then you’ve saved yourself what could be your biggest cost. Sometimes, though, someone will offer you a space but require you to pay for security and whatnot. If so, then you’ll need another sponsor to pay for that. And of course, get somebody to pick up the lunch tab if you can. Remember, sponsors get publicity for their businesses or organizations out of sponsorship – which can mean an awful lot to them! But if all else fails, if you’ve got a space but no lunch, ask your participants to brown bag it.
45 | 
46 | You can also contact the [ClojureBridge mailing list](https://groups.google.com/forum/#!forum/clojurebridge-workshops) for ideas and help with sponsorship.
47 | 
48 | For more information about funding, check out the [Money Things](Money-Things.md).
49 | 
50 | 
51 | ## <a name="set_date"/>Set a date and time 
52 | Plan the Installfest for a Friday evening and the workshop the following Saturday. Trust us, you need that extra day for the Installfest – students can’t do the workshop without it, it’s messy and takes everybody vastly different amounts of time.
53 | 
54 | 
55 | ## <a name="find_students"/>Recruit participants 
56 | A workshop’s no fun if nobody comes. Find out the capacity of the space you’ll be in so that you don’t sign up more people than you have capacity for. But remember, a lot of the people who sign up won’t show – could be as many as half. Plan accordingly.
57 | 
58 | In addition to reaching out to Clojure user groups, research local tech groups and communities that might include members interested in Clojure:
59 | * SysAdmins
60 | * Designers
61 | * QA Engineers
62 | * Product and Project Managers
63 | * Devs working in other languages
64 | 
65 | Other people who are often interested in ClojureBridge workshops include:
66 | * Lawyers
67 | * College students
68 | * Admins
69 | * Career changers
70 | * People from all backgrounds!!!
71 | 
72 | Now, how are you going to get the word out? Other ideas include posting to local forums, putting flyers in coffee and book shops with a link to a Google form that they can use to say they’ll attend, or connecting with community colleges/local IT businesses in your area to get the word out are also good ways to go.
73 | 
74 | 
75 | 
76 | ### [Go to Cookbook home](README.md)
77 | 


--------------------------------------------------------------------------------
/Frequently-Asked-Questions.md:
--------------------------------------------------------------------------------
 1 | <a name="teaching_diversity"/>
 2 | 
 3 | ## Do workshop organizers and teaching staff need to be women?
 4 | 
 5 | For a workshop intending to introduce women to programming, ideally,
 6 | there should be a strong presence of women both on the teaching staff
 7 | and amongst the organizers. Given that, ClojureBridge exists to
 8 | address an imbalance in the Clojure community, so a diverse teaching
 9 | staff may not be possible in certain geographic areas.
10 | 
11 | Even though the first workshop couldn't make good gender balance on
12 | the teaching staff, the second, third, etc. workshop may solve
13 | this. Continuing to organize will help make change in your
14 | community. Some ways to maximise the presence of women in the running
15 | of a ClojureBridge workshop are:
16 | 
17 | 1. Invite local organisations for women in tech to advise/co-organise
18 |    the event.
19 | 2. Would any women you know who program in languages other than
20 |    Clojure consider learning enough to be a TA? This is particularly
21 |    useful if they have previous experience teaching at a similar event
22 |    like RailsBridge, Django Girls etc.
23 | 3. Are there women Clojure developers living in neighbouring cities
24 |    who could help? (offer to pay their travel costs if possible).
25 | 4. Is there a Clojure/FP conference in your region which you could
26 |    schedule ClojureBridge close to, so that conference delegates can
27 |    volunteer?
28 | 5. If there's been a previous ClojureBridge near you, are there former
29 |    students who could become TAs?
30 | 6. Make the most of the women you have, giving them leading roles in
31 |    teaching and presenting
32 | 
33 | Ultimately, it's important to be proactive about creating a diverse
34 | environment where possible, and that the environment created by a
35 | ClojureBridge workshop be inclusive of all participants.
36 | 
37 | 
38 | ## Who can attend to workshops? Men are allowed?
39 | 
40 | See another doc, [Guidance to Men's Attendance](https://github.com/ClojureBridge/organizing/blob/master/Guidance-to-Mens-Attendance.md) .
41 | 
42 | 
43 | ## How to improve attendance
44 | 
45 | See antoher doc, [How to Improve Attendance](https://github.com/ClojureBridge/organizing/blob/master/How-to-Improve-Attendance.md)


--------------------------------------------------------------------------------
/Guidance-to-Mens-Attendance.md:
--------------------------------------------------------------------------------
 1 | # Guidance to Men's Attendance
 2 | 
 3 | ## Who should we accept as students for the workshop?
 4 | - Men can attend?
 5 | - How to accept students of under-represented groups only? Say, only women?
 6 | 
 7 | This document provides guidance on whether we should accept men as students for ClojureBridge workshops.
 8 | Also, this document provides suggestions as to how to avoid accepting attendees who aren't members of an under-represented group.
 9 | For example, how to accept only female students.
10 | 
11 | What follows is __guidance__. Workshop organizers are free to choose their workshops' attendance policies.
12 | When organizers can't decide whether they should accept men for the workshop, this document will help them to make a decision.
13 | 
14 | 
15 | ### Consider ClojureBridge's goal
16 | 
17 | ClojureBridge was started to increase diversity in the Clojure community.
18 | ClojureBridge is for people who belong to under-represented groups such as women, trans\*\*, genderqueer, or gender non-conforming.
19 | There may be other groups we should identify as under-represented in Clojure community.
20 | 
21 | Given that, please do not accept men simply because there are available seats.
22 | 
23 | Success of a workshop is not measured by the number of attendees but by the satisfaction of those who attend.
24 | 
25 | 
26 | ### Consider how attendees will feel during the workshop
27 | 
28 | We have heard positive voices from female attendees of women-only workshops.
29 | They liked the comfortable atmosphere. They weren't afraid to ask questions during the workshop.
30 | This shows that women-only workshops worked as a safe space for them.
31 | 
32 | Please be very careful when organizers accept men.
33 | The workshop may make female attendees uncomfortable.
34 | 
35 | 
36 | ### How to accept male attendees
37 | 
38 | ClojureBridge suggests accepting male attendees as guests of female attendees.
39 | A female attendee may bring a man who is a Clojure or programming beginner.
40 | 
41 | Or, on the contrary, male attendees must come with female guests, would be another rule.
42 | 
43 | In any case, ClojureBridge wants to avoid decreasing the ratio of attendees from under-represented groups.
44 | 
45 | 
46 | ### When organizers may accept men, please...
47 | 
48 | Please do not write *for women* in anywhere of the workshop announcements.
49 | There may be subscribers because the workshop is *for women*.
50 | What if such attendees see men in the workshop?
51 | This could be considered as betrayal.
52 | 
53 | Once the announcements said *for women*, please don't change the policy.
54 | 
55 | 
56 | ### How to enforce or check all subscribers are women
57 | 
58 | Organizers decided they would accept only female attendees.
59 | But, how can it be possible?
60 | 
61 | Guessing from name is very tricky and never works perfectly.
62 | Especially, a foreign name is hard to figure out whether the subscriber is he or she.
63 | 
64 | Some workshops added a checkbox to a registration form, which required "yes" to
65 | the question, "I identify as a woman, trans\*, genderqueer, and/or gender non-conforming person."
66 | The organizers said this worked well.
67 | 
68 | Be prepared beforehand.
69 | 
70 | 
71 | #### Reference: Discussion on Mailing List
72 | 
73 | This document is created based of the discussion done on the ClojureBridge Workshops mailing list.
74 | Here's a link to the thread:
75 | 
76 | <https://groups.google.com/forum/#!topic/clojurebridge-workshops/7TE0HEJ1jxg>
77 | 
78 | (You need to subscribe and login to see the content.)
79 | 
80 | Thanks to those who participated in the discussion.
81 | 


--------------------------------------------------------------------------------
/Help-Them-Keep-Learning.md:
--------------------------------------------------------------------------------
 1 | ## How to Help Attendees Keep Learning
 2 | 
 3 | ### Just one weekend is not enough, of course.
 4 | 
 5 | Installing Clojure stuff on Friday, learning Clojure basics on Saturday, then she's good to go to become a Clojure developer?
 6 | Except for a very few cases, of course, the answer is no.
 7 | As many of you suspect, just one weekend is not enough to start coding Clojure; moreover, it's not enough to keep coding Clojure.
 8 | This document contains ideas for ClojureBridge volunteers to help workshop attendees further after the workshop.
 9 | 
10 | 
11 | ### Provide a list of local meetups and/or community info
12 | 
13 | Since a ClojureBridge workshop is driven by a community in the area, we can assume there is also a local Clojure community in the area.
14 | Give ClojureBridge attendees local community info, upcoming events or other resources they can take advantage of.
15 | When you give the info, it's a good idea to hand them a piece of paper.
16 | Many of the attendees are not familiar with meetup.com, github.com, etc.
17 | If you just show or say urls of those, they may miss the info.
18 | 
19 | 
20 | ### Invite them to local Clojure events
21 | 
22 | Clojure developers you have not met yet may attend your ClojureBridge workshop.
23 | If that is the case, this is a chance to invite them to local Clojure events, such as meetups, and expose them to Clojure technology and community.
24 | If some of the attendees who are new to Clojure come to a local Clojure event, it means they have made a great first step to getting more involved with Clojure.
25 | 
26 | 
27 | ### Organize follow-up workshop or event
28 | 
29 | It is a good idea to organize a follow-up workshop or event.
30 | This may be a short - one or two hours - event like a meetup you do regularly.
31 | During the follow-up event, walking through the ClojureBridge curriculum or other introductory materials would be good.
32 | Either lecture style or hack night style will help attendees to keep learning.
33 | If some folks have been coding a little on their own, starting a project may be an idea - for example, a quil app of their own.
34 | Since this sort of short event is easy to organize, you can do more than one or even a recurring event.
35 | 
36 | 
37 | ### Follow-up meetups in the past
38 | 
39 | 1. Durham NC - Intro to Clojure at a local Clojure meetup
40 | 2. San Francisco - 
41 | 
42 | 
43 | ### ClojureBridge Alumni mailing list
44 | 
45 | <https://groups.google.com/forum/#!forum/clojurebridge-alumni>
46 | 
47 | Every attendees, instructors and TAs can join this mailing list.
48 | Although the mailing is not local, it is a good place to announce upcoming events or meetups.
49 | 
50 | 
51 | ### After workshop materials (Ongoing)
52 | 
53 | ClojureBridge has materials other than main curriculum, listed below.
54 | 
55 | - The second drawing app, <https://github.com/ClojureBridge/drawing/blob/master/curriculum/create-something.md>
56 | - Global Growth app, <https://github.com/ClojureBridge/global-growth>
57 | - Community-docs, <http://clojurebridge.github.io/community-docs/>
58 | 
59 | In addition to above, ClojureBridge is planning to add fun-to-try-out, small apps for after workshop events or self-study.
60 | 
61 | 
62 | ### Remind them to watch LispCast
63 | 
64 | Lastly, don't forget to mention about LispCast. The attendees can watch it for free.
65 | 


--------------------------------------------------------------------------------
/Hosting-venue-questions.md:
--------------------------------------------------------------------------------
 1 | Location Questionnaire
 2 | ### Space
 3 | * Who will be the company's liaison to contact if any questions/problems arise during the workshop?  What is their contact information?  During parts of the workshop will they be on-site?
 4 | * Which rooms/spaces are available for workshop use?
 5 | * May we (and _can_ we -- sometimes there are reasons why it's logistically not possible) reconfigure spaces freely, for instance moving desks and tables, as long as we promise to diligently restore their original configuration before leaving on Saturday?
 6 | * Can the location also be used for teacher training and/or after-party?
 7 | * What is a suitable space, if any, to put children and a babysitter?
 8 | 
 9 | ### Security
10 | * What arrangements need to be made regarding picking up/dropping off keys?
11 | * Does there need to be someone down at the door?
12 | * Will they require non-disclosure agreements?
13 | * Are there rooms/areas that must be kept off-limits?
14 | * Are there any special arrangements to make regarding security?  For example, providing a list of attendee names some number of days/weeks in advance.
15 | * Is there a firm time when they need us to depart, or are they fine with letting us stay until the last person is done? (Particularly relevant for the unpredictable nature of Installfest.)
16 | 
17 | ### Equipment
18 | * How many of the rooms/spaces for the workshop have screens/projectors?  Do we need to bring some if we are working in open spaces, or can they lend us monitors to instead plug into?
19 | * Are there Mac and PC adaptors available for each of those screens/projectors/monitors?
20 | * Are there extension cords/connectors that the workshop can use?
21 | * Is there a microphone and amplified system available to use for the large group announcements sections?
22 | * Is there central air/heat on the weekends? If not, are there extra fans/space heaters that can be used if needed?
23 | * May we use any whiteboards and chalkboards we find in the rooms/spaces?  If so, may we erase whatever is already on those?
24 | * Anything not-completely-obvious to know about using their equipment?
25 | * What is the wifi login?
26 | 
27 | ### Parking
28 | * Is there public parking nearby they can recommend?
29 | * Is there bike parking anywhere in the building that would be available for the workshop?
30 | 
31 | ### Catering
32 | * Which of the meals for the workshop are they planning on covering?
33 | * Would they prefer to arrange any of the food?  Or would they prefer we arrange and have the caterers submit any invoices to the location host?
34 | * Can the caterer accommodate special dietary requests, e.g. food allergies?  Or do they prefer we arrange for those meals separately?
35 | * If there are snacks/drinks at the office, are these available to people at the workshop?
36 | 
37 | ### Cleanup
38 | * Where are trash receptacles?
39 | * Where are compost/trash/recycle bags located?
40 | * Where should filled compost/trash/recycle bags be put?
41 | * Do they have any specific cleanup/composting requirements?
42 | * Do we need to wipe down all tables or just handle the trash and put tables back where they were before the event?  
43 | * Would they prefer we use all disposable dishes and utensils?
44 | * Would they prefer that we throw out any left over food?  Or wrap it and leave it in the fridge for any of their people?
45 | 
46 | ### Plug
47 | * When would they like to have a plug?  (Friday night?  Saturday Morning?)  Would they like to make a recruiting pitch too?
48 | * Will they have some of their people attending to do this?
49 | * If no, do they have any specific projects they would like us to mention when we’re giving the plug?
50 | * Would they like to provide company-branded stickers for Installfest?
51 | * Would they like to provide any other promotional shwag, such as company t-shirts, buttons, etc?
52 | 
53 | ### [Back to pre-workshop tasks](Pre-workshop-tasks.md)
54 | 


--------------------------------------------------------------------------------
/How-to-Improve-Attendance.md:
--------------------------------------------------------------------------------
 1 | ## How to Improve Attendance
 2 | 
 3 | ClojureBridge is a free workshop, which sometimes leads to bad attendance. Especially, in big cities, attendace is a serious problem.
 4 | Organizers get a bunch of subscribers, find a bunch of teachers not to leave students behind, and order bunch of food to meet with the number of expecting attendees. Everything is ready. Then, the workshop starts. Organizers see only a few attendees despite the big subscribers list...
 5 | 
 6 | 
 7 | Unfortunately, there are many people who don't weigh a free workshop. They subscribe instantly and just don't show up. Some meetups charge small amout of money to lower no show rate. This may be the way. However, ClojureBridge is a free workshop. This is a philosophy of ClojureBridge described in [What makes a workshop a ClojureBridge Workshop?](https://github.com/ClojureBridge/organizing/blob/master/Minimum-Viable-Workshop.md#what-makes-a-workshop-a-clojurebridge-workshop) . Organizers, please don't rely on money to improve attendance.
 8 | 
 9 | 
10 | ### Why relying on money is a bad idea
11 | 
12 | We understand paying money works in the big cities. Also, the situation varies country to country, or region to region. However, there are certain number of people who don't have their own credit card for payment. We may kick such people out from ClojureBridge workshop.
13 | 
14 | Another reason is we want to lower the barrier to get started. Paying money on the website will add an obstacle though it's small. We may discourage people who are about to make the very first step of programming.
15 | 
16 | 
17 | ### Tips to improve attendance
18 | 
19 | Even in the big cities, some workshops have made a great attendance. How did they do? Here're tips to improve attendance.
20 | 
21 | 
22 | #### 1. 'Subscribed' doesn't mean get the seat
23 | 
24 | Although organizers' work load will go up, this works well. Send out confirmation and require a response to the confirmation. It's good to notify approved attendees to cancel if their schedule changes.
25 | 
26 | 
27 | #### 2. Choose attendees
28 | 
29 | When the first strategy doesn't work, it's better to add a selection process. This will add further work load to organizers, but works better. For example, ask subscribers to write thier story, passion, or other, why they want to attend. People who have good reasons will show up.
30 | Downside of this selection process is, organiers may get complaints from who aren't selected. Avoid writing a specific reason of rejection. It would be good, "we selected beginners" or such, something very general.
31 | 
32 | 
33 | ### 3. Make it one day workshop
34 | 
35 | RailsBridge/RailsGirls workshops are a template of ClojureBridge, so it is a two-day workshop.
36 | However, requiring attendees to show up both two days may be the reason of bad attendance. Friday evening traffic may be very bad which makes enough reason of no show. Sometime, people commmute to downtown spending long time. Dropping by after a day work is ok, but on Saturday morning, they may loose motivation to be back to downtown again.
37 | 
38 | For RailsBridge/RailsGirls, installing Ruby is a big stuff, sometime problematic. In general, the workshop requires the latest or newer version of Ruby to run newer version of Rails. It's safe to finish all installation on Friday. However, we are on Java. Downloading takes long, but normally the installation goes smoothly. Except Windows 7 users with old Java version setup, Java installation won't take long. Other installations won't take long as well. We may cut downloading time short by preparing USB with already downloaded archives.
39 | 
40 | 
41 | ## Please report us!
42 | 
43 | If you orgnized the workshop in a big city and made a good attendance, please share what worked well.
44 | 


--------------------------------------------------------------------------------
/Installfest-Tasks.md:
--------------------------------------------------------------------------------
 1 | ## Installfest Tasks
 2 | _Remember that you have tons of volunteers eager to help, allow them to help by delegating!_
 3 | ### <a name="installspace"/>Setting up a good Installfest space
 4 | * Post the wireless SSID & password often and visibly. 
 5 | * Post the installfest link as well, as many people will have ignored instructions and will need to install it when they get there. 
 6 | * Power outlets will guide how the space is set up, but RailsBridge's rolling chest of power cords should help with. The Installfest should be one big room with different tables, ideally marked with OSs so that folks with similar issues can help each other. (This usually means getting more granular than just Mac/Linux/PC and breaking out older Mac OSs into their own pods.)
 7 | 
 8 | ### <a name="welcomedesk" id="welcome_desk"></a> Welcome desk with class level confirmation
 9 | * People will show up early. Sometimes 30 minutes early. Be ready. Depending on the space you are in, it's easy to let people slip by without checking in. Don't let them!  It helps to have signage stating that everyone, including volunteers, needs to check in and make a name tag. 
10 | * _Tip: set up the welcome desk (with clear signage) before setting up the rest of the Installfest. People will make themselves at home, so if you need to bail on that setup to check people in, do it!_
11 | * Use your Eventbrite signup sheet to check people in. You can easily add multiple volunteer 'checkeriners' to help speed things up. 
12 | * When volunteers check in, have them mark their name tags in some way (star stickers or a drawn star have worked). Make sure the students know they should not be shy about asking anyone with a star (or your chosen signifier) for help. 
13 | * When people check out for the evening, you can tell them their class level for the workshop and a brief description of what it means. People tend to horribly underestimate their skill levels, so encourage upward shifts. Emphasize that they can always change classes during the workshop.
14 | 
15 | 
16 | ### <a name="installfestissues" id="issues"></a> Dealing with inevitable issues
17 | * Wireless bandwidth is always difficult at workshops. Preparing for this and communicating it repeatedly to your students is the best bet, but people will still show up at the Installfest not having downloaded gargantuan necessary files. Having said files on flash drives will help dramatically, so make sure to have those. And don't lose them! 
18 | * As an organizer, people will expect you to solve their problems. Help them if you can, but if someone asks you about something outside of your expertise, delegate swiftly and without guilt. If it's 7pm and it looks like it's going to be 6 hours for a student to download a necessary file, this probably isn't the weekend that the workshop will work for them. Since we do this regularly, telling people that they can't do the workshop this time isn't the worst thing in the world. It sucks, but it's better than having someone sitting in the workshop on Saturday unable to do anything or derailing their section because of their incomplete install.
19 | 
20 | ### Organizers - Take This Time To Get Your Ducks In Order
21 | Carve out some time to review your Schedule for Saturday:
22 | * Count your Logistical volunteers so you know who you can count on.  Cross reference the Workshop task list and to sort out the tasks that can easily be taken care of (door greeting, Signage (WIFI & hashtag, Class Room Levels), time keeper, etc.)
23 | * Know (or sort-of know) who is working the Registration desk, (if they're not there,at best send them a quick email) let them know how much you appreciate them for taking on a very important position & that you'll see them bright and early on Saturday.
24 | * Teacher Training Night is a good time to do this also
25 | 


--------------------------------------------------------------------------------
/Letters-to-students.md:
--------------------------------------------------------------------------------
  1 | # Maggie's letters to students
  2 | 
  3 | ## Teachers/TAs
  4 | 
  5 | * 2 emails to TAs prior to the teacher/TA training, in addition to sending a Google calendar invite. I sent the first email about 2 weeks in advance, the second email about one week in advance. See example #1.
  6 | * One email sent immediately after the training with suggested next steps. See example #2.
  7 | * One reminder email about the workshop on the Monday before the workshop. See example #3.
  8 | * Thank You note plus link to feedback survey after the workshop. See example #4.
  9 | 
 10 | 
 11 | 
 12 | ## Students
 13 | 
 14 | * One email about 2 weeks before the workshop. Reviewing workshop basics, stressing the importance of canceling if you can't come, reminding folks the InstallFest is mandatory, some info about the facilities at the location. I also sent some links to @Aphyr's Clojure from the Ground Up & @nonrecursives Clojure for the Brave & True, but stressed that these were FYI only, not required reading. See example #5.
 15 | * One email on the Monday before the workshop. This email reviewed dates & times, reminded folks about the waitlist and cancelling if they can't come. See example #6.
 16 | * One email to waitlisted folks on the Monday before the workshop. See example #7.
 17 | * Thank You note plus link to feedback survey after the workshop. See example #4.
 18 | 
 19 | ## Letters
 20 | 
 21 | ### Example 1: Note to TAs 1 week before training
 22 | 
 23 | 
 24 | 
 25 | Subject line: ClojureBridge Teacher Training on 3/18
 26 | 
 27 | 
 28 | Hi Folks,
 29 | 
 30 | Thanks to each of you for volunteering as a teaching assistant for the first-ever ClojureBridge workshop! Seventeen women have signed up to attend the workshop so far. I'm really excited to see so much interest, and really eager to welcome these new folks into the Clojure community.
 31 | 
 32 | Please make sure the ClojureBridge teacher training session is on your calendar. It's next Tuesday, March 18, from 6:00 - 8:00 PM, at the Cognitect offices in downtown Durham. We'll be serving free pizza, soft drinks, and snacks.
 33 | 
 34 | If you want to be a TA, you *must* attend this training session.
 35 | 
 36 | Here's a rough agenda:
 37 | 
 38 | * Teachers & TAs meet each other. Group hugs optional.
 39 | * Explain ClojureBridge's goals 
 40 | * Talk about how to be a good TA and what to expect
 41 | * Review the ClojureBridge curriculum 
 42 | * Q & A
 43 | 
 44 | We'll have a GoTo Meeting session in case anyone can't make it in to the Cognitect offices. The link is in the Description field of the calendar event. I've also included it below:
 45 | 
 46 | GoToMeeting link: 
 47 | <link went here>
 48 | You will be connected to audio using your computer's microphone and speakers (VoIP). A headset is recommended.
 49 | Meeting ID:xxx-xxx-xxx
 50 | 
 51 | If you have any questions, please let me know. I look forward to seeing you all next week!
 52 | 
 53 | 
 54 | ### Example 2: Email to TAs after training session
 55 | 
 56 | 
 57 | 
 58 | Subject line: ClojureBridge TAs - next steps
 59 | 
 60 | Dear Superfriend,
 61 | 
 62 | Thanks for coming out for the ClojureBridge teacher training session last night! This would not be possible without your help, your time, and your enthusiasm.
 63 | 
 64 | As of this morning, we have a waiting list of folks who want to attend the workshop. (Registration is currently capped at 20 people. We may consider upping that, especially if there are only 1-2 people on the list.)
 65 | 
 66 | As we mentioned last night, here are some things you can do to prepare for the workshop:
 67 | 
 68 | 1 -  Read the curriculum and think about how you'd do the exercises. The curriculum us still a work in progress, but it's mostly done. Pull requests for minor improvements welcome. Pull requests involving major overhauls won't get much attention until after the first workshop. The curriculum will also be available in slide format by the time of the workshop.
 69 | 
 70 | 2 - We'd especially appreciate help testing the the Windows version of the setup instructions. If you don't have Windows installed, you can get an evaluation-licensed VM of Windows from Microsoft at modern.ie. 
 71 | 
 72 | 3 - Get familiar with Light Table, so you can answer basic questions about it. 
 73 | 
 74 | 4 -  Check out the Global Growth app we'll be "building" in the workshop. The master/full version is here. The shell/fill-in-the-blank version that students will start with is here. 
 75 | 
 76 |  
 77 |  If you have any questions, post them to the ClojureBridge Workshops Google group . You're all members. And here are the teachertraining slides from RailsBridge if you would like to review anything.
 78 | 
 79 |  Thanks again to everyone for teaching and TAing. This is going to be so much fun!!
 80 | 
 81 | 
 82 | ## Example 3: TA reminder email on Monday before workshop
 83 | 
 84 | 
 85 | 
 86 | 
 87 | Subject line: ClojureBridge TAs: Ready, Set, Go!
 88 | 
 89 | Hi Folks,
 90 | 
 91 | Thanks so much for volunteering your time and enthusiasm to help teach the first-ever ClojureBridge workshop! You're awesome.
 92 | 
 93 | Here are a few things you should do this week to prepare for the workshop:
 94 | 
 95 | * Check out the full schedule here: 
 96 | 
 97 | http://clojurebridge.github.io/community-docs/2014/03/28/the-first-durham-chapter.html
 98 | 
 99 | * Double-check the event times (They are listed at the bottom of this email and in the link above). If for any reason you can't attend the InstallFest or the Workshop, please let us know as soon as possible so we can adjust our plans accordingly. We have a full house of 20 attendees, so we need all your hands on deck to make this successful.
100 | 
101 | * If you haven't yet, please make sure you read through the entire curriculum and get familiar with the Global Growth application we'll be building in the workshop. The full curriculum will also be available in slide format by the time of the workshop. See something that could be better? Please send us a pull request.
102 | 
103 | * Check in with Bridget prior to the festivities on Friday night. She'll be coordinating TA activities and she may have some special requests for you. 
104 | 
105 | * If you have any questions about the curriculum or the workshop, please send a note to <add yr email here> or post a question to the ClojureBridge-Workshops Google group. You're all group members. By default, you get no email notifications from this group. To change that, you can log into the group and edit your settings.
106 | 
107 | 
108 | Thanks again for making this possible!
109 | 
110 | 
111 | <3<3<3 ClojureBridge
112 | 
113 | 
114 | 
115 | ==InstallFest
116 | Friday, April 4
117 | 6:30 - 8:30 PM
118 | Dinner provided.
119 | Feel free to head over to the Cognitect office anytime on Friday afternoon. We'll be around and you won't be interfering with anything. You can help us re-arrange furniture! 
120 | 
121 | 
122 | ==Workshop
123 | Saturday, April 5
124 | 9:00 - 5:30
125 | Breakfast & lunch provided.
126 | Afterparty at The Pinhook, in downtown Durham. Your first drink is on us. Snacks will be provided.
127 | 
128 | 
129 | ### Example 4: Thank You notes
130 | 
131 | 
132 | ==TA Note
133 | 
134 | Subject line: Thank you for helping with ClojureBridge Durham
135 | 
136 | 
137 | Hi all.
138 | 
139 | Thank you SO much for giving up most of your weekend to assist with the Durham ClojureBridge workshop. We could not have done it without each and every one of your contributions. 
140 | 
141 | We need to ask for one more piece of help. Could you please fill out the following survey so that we have more information about how to improve future workshops? We would very much appreciate it. 
142 | 
143 | <link to survey here>
144 | 
145 | The ClojureBridge team 
146 | 
147 | 
148 | 
149 | 
150 | ==Attendee Note
151 | 
152 | Subject line: Thanks for attending ClojureBridge
153 | 
154 | 
155 | 
156 | Dear ClojureBridge friends,
157 | 
158 | It was great to meet you at the first ever Durham ClojureBridge workshop. Thank you so much for attending. 
159 | 
160 | We would love to know about your experience at the workshop. Please fill out this short survey:
161 | 
162 | <feedback form link here>
163 | 
164 | 
165 | We have added you to the ClojureBridge Alumni Google group. ClojureBridge teachers and TAs will be there. Please feel free to ask any follow up questions that you may have. All questions are welcome!
166 | 
167 | 
168 | Here are other some resources you may want to check out: <note: many of these are local to Durham>
169 | 
170 | ClojureBridge community docs: http://clojurebridge.github.io/community-docs
171 | 
172 | Meetups
173 | 
174 | Triangle Clojure Meetup: http://www.meetup.com/TriClojure/
175 | Refresh the Triangle: http://www.meetup.com/refreshthetriangle/
176 | TriPython: http://trizpug.org/meetings
177 | 
178 | Clojure tutorials
179 | 
180 | Clojure for the Brave and True: http://www.braveclojure.com/
181 | Clojure from the Ground Up: http://aphyr.com/posts/301-clojure-from-the-ground-up-welcome
182 | 4Clojure: http://www.4clojure.com/problems
183 | 
184 | Code schools
185 | 
186 | The Iron Yard: http://theironyard.com/locations/durham/
187 | Girl Develop It RDU: http://www.meetup.com/Girl-Develop-It-RDU/
188 | 
189 | 
190 | The ClojureBridge team
191 | 
192 | 
193 | ### Example 5: Email to attendees 2 weeks in advance
194 | 
195 | 
196 | Subject line: Welcome to the Durham ClojureBridge Workshop! 
197 | 
198 | 
199 | Dear Super Friends,
200 | 
201 | We are *so* excited you've signed up for the ClojureBridge workshop April 4-5.
202 | 
203 | Here are a few things to keep in mind:
204 | 
205 | * Registration for this workshop is capped at 20 participants, and we do have a waiting list. Please let us know if you can't attend this workshop, so we can offer your spot to someone on the waiting list. This won't be your last chance--we hope to offer more workshops like this in the future.
206 | 
207 | * Attendance at the Friday night InstallFest is mandatory. We'll be installing all the necessary software on your laptop so you'll be ready to go Saturday morning. And it'll be fun, we promise. You'll get to meet the other workshop participants and teachers. We'll have free food, beer, and soft drinks available.
208 | 
209 | * Free breakfast, lunch, and snacks are provided on Saturday. If you'd like to bring your own food, you're welcome to do so. We'll have a fridge, a microwave, dishes, & eating utensils on hand.
210 | 
211 | * The Cognitect office is wheelchair-accessible. Please let us know if any special accommodations or assistive technologies would help make your workshop experience more awesome.
212 | 
213 | * If you're curious to learn more about the Clojure programming language before the workshop, you can check out Clojure from the Ground Up, by Aphyr, or Clojure for the Brave and True, by @nonrecursive (also known as Daniel Higgenbotham, who will be one of the workshop TAs). This reading is completely optional, and you won't need to be familiar with this material prior to the workshop.
214 | 
215 | In the meantime, if you have any questions, please contact your friendly workshop organizers at <yr email here>
216 | 
217 | We can't wait to meet you!
218 | 
219 | <3<3<3 ClojureBridge
220 | 
221 | 
222 | ### Example 6: Reminder to attendees on Monday prior
223 | 
224 | 
225 | Subject line: Durham ClojureBridge Workshop Reminder
226 | 
227 | Hi Super Friends,
228 | 
229 | First, some news. Saturday's afterparty will be held at The Pinhook, in downtown Durham. After the workshop, we'll walk to The Pinhook or carpool in groups, since parking downtown can be challenging on weekends. We'll provide light snacks, and your first round is on us!
230 | 
231 | Next up, a couple of reminders:
232 | 
233 | * Please double-check the event times and location and make sure you can arrive on time. The Friday-night InstallFest is a mandatory part of the workshop. Bring your laptop so we can install the necessary software and make sure you have a working Clojure environment. This allows us to hit the ground running on Saturday morning.
234 | 
235 | * If you're unable to attend Friday's InstallFest or the workshop on Saturday, please let us know as soon as possible. We have several people on the waiting list, and we'd hate for any spots to go unused.
236 | 
237 | As always, if you have any questions, please let us know at <yr email here>
238 | 
239 | We can't wait to meet you!
240 | 
241 | 
242 | --Your Friendly Workshop Organizers
243 | 
244 | 
245 | ### Example 7: email to waitlisted folks
246 | 
247 | 
248 | Subject line: ClojureBridge waitlist status
249 | 
250 | 
251 | Hi Everyone,
252 | 
253 | Thanks so much for your interest in the ClojureBridge workshop April 4-5. You're currently on the waitlist for this event, and we'll let you know if any spots open up. 
254 | 
255 | We're delighted that this event sold out, but we're also sorry we won't get to meet you this time.
256 | 
257 | We'll be hosting other workshops in the future, and we'll make sure you get a chance to register for any future events before tickets go on sale publicly. 
258 | 
259 | In the meantime, if you'd like to learn more about ClojureBridge, you can check out our web site or this talk ClojureBridge founder Bridget Hillyer gave at the recent Clojure/West conference.
260 | 
261 | And if you're curious about the Clojure programming language, some good introductory materials are Clojure from the Ground Up, by @Aphyr, and Clojure for the Brave and True, by @nonrecursive (also known as Daniel Higgenbotham, who is one of the workshop TAs). 
262 | 
263 | We hope to see you next time!
264 | 
265 | ### [Back to Templates and Materials](Templates-and-Materials.md)
266 | 


--------------------------------------------------------------------------------
/Local-Organizations.md:
--------------------------------------------------------------------------------
 1 | Local Organizations
 2 | ===================
 3 | 
 4 | Below is a list of local feminist and/or women-in-tech groups, ordered by state and metropolitan area. You can use this list as a resource while performing outreach for your ClojureBridge event, or you can use it to avoid scheduling conflicts with other organizations.
 5 | 
 6 | 
 7 | San Francisco Bay Area, CA
 8 | ---------------------------
 9 | 
10 | - [Bay Area Clojure User Group](http://www.meetup.com/The-Bay-Area-Clojure-User-Group/)
11 | 	- Bay Area Clojure User Group is the primary meetup for Clojurians in the Bay Area.
12 | 	- You can view a list of upcoming events on their [Meetup page](http://www.meetup.com/The-Bay-Area-Clojure-User-Group/).
13 | 
14 | - [Double Union](https://doubleunion.org)
15 | 	- Double Union is a non-profit hacker/maker space for women in San Francisco, with a physical location in the Mission. They are intersectional feminists, women-centered, and queer- and trans-inclusive.
16 | 	- Double Union maintains a mailing list for all of its members. You can request that a ClojureBridge event be promoted via the mailing list by reaching out to Double Union's public email address, [doubleunionsf@gmail.com](mailto:doubleunionsf@gmail.com).
17 | 
18 | - [Girl Develop It](http://www.girldevelopit.com)
19 | 	- Girl Develop It is a non-profit organization that exists to provide affordable and accessible programs to women who want to learn web and software development through mentorship and hands-on instruction. They have 35 chapters across the United States (as of September 2014) and most frequently offer paid classes in front-end development, as well as free study groups to facilitate community learning.
20 | 	- You can contact the organizers of Girl Develop It - San Francisco through their public email address, [sf@girldevelopit.com](mailto:sf@girldevelopit.com); reach out to one of the local leaders through their chapter's [website](http://www.girldevelopit.com/chapters/san-francisco); or view a list of upcoming events on the Girl Develop It - San Francisco [Meetup page](http://www.meetup.com/Girl-Develop-It-San-Francisco).
21 | 
22 | - [Hackbright Academy](http://hackbrightacademy.com)
23 | 	- Hackbright Academy is a for-profit organization that offers full-time, part-time, and weekend programming courses for women in San Francisco. They also host free events for women in tech, such as beginner-friendly hackathons and tech talks by women engineers.
24 | 	- Hackbright maintains mailing lists for their alumni, as well as their current students. You can request for a ClojureBridge event to be promoted via the mailing lists by sending an email to [Angie Chang](mailto:a@hackbrightacademy.com), Hackbright's Director of Growth, or [Katherine Fellows](mailto:k@therinefello.ws), a Hackbright alumna who volunteers with ClojureBridge in San Francisco.
25 | 
26 | - [Liberating Ourselves Locally](http://oaklandmakerspace.wordpress.com)
27 | 	- Liberating Ourselves Locally is a people-of-color-led, gender-diverse, queer- and trans-inclusive hacker/maker space in East Oakland.
28 | 	- You can contact Liberating Ourselves Locally via their public email address, [oaklandmakerspace@gmail.com](mailto:oaklandmakerspace@gmail.com).
29 | 
30 | - [PyLadies](http://www.pyladies.com/)
31 | 	- PyLadies is an international mentorship group with a focus on helping more women become active participants and leaders in the Python open-source community. Their mission is to promote, educate, and advance a diverse Python community through outreach, education, conferences, events, and social gatherings. They have 32 chapters across the world (as of September 2014) and provide a friendly support network for women and a bridge to the larger Python world.
32 | 	- You can contact the organizers of PyLadies SF, as well as view a list of upcoming events, via their [Meetup page](http://www.meetup.com/PyLadiesSF).
33 | 
34 | - [RailsBridge](http://www.railsbridge.org)
35 | 	- RailsBridge is working to make tech more diverse and welcoming by teaching programming, connecting human beings, and listening to people's needs. They organize and teach free workshops on Rails, Ruby, and HTML & CSS in cities all over the world, targeted at groups of people that are underrepresented in tech. RailsBridge is a sister organization of ClojureBridge, and ClojureBridge closely follows their model.
36 | 	- You can view a list of upcoming RailsBridge events in San Francisco at [BridgeTroll](http://bridgetroll.org).
37 | 
38 | - [San Francisco Lesbian Gay Bisexual Transgender (LGBT) Community Center](http://www.sfcenter.org)
39 | 	- The mission of the SF LGBT Center is to connect the diverse LGBT community to opportunities, resources, and each other to achieve their vision of a stronger, healthier, and more equitable world for LGBT people and their allies. The SF LGBT Center offers career counseling, job fairs, a computer lab, social activities, mentorships, youth meals, daycare, various workshops, and much more.
40 | 	- You can view a list of upcoming events on their [official calendar](http://www.sfcenter.org/events-calendar), or contact the organization through their [website](http://www.sfcenter.org/contact).
41 | 
42 | - [TranscodeSF](http://transcodesf.org)
43 | 	- TranscodeSF was developed in 2012, as a programming class for trans and gender non-conforming folks. Transcode teaches folks computer programming and software engineering skills through a series of classes, study groups, and hands-on events with tech industry experts. All events are free and open to all trans and GNC people and their allies.
44 | 	- You can view a list of upcoming TranscodeSF events on their [Meetup page](http://www.meetup.com/TranscodeSF), or contact the organization via their [website](http://transcodesf.org/en/contact).
45 | 
46 | - [Trans*H4CK](http://www.transhack.org)
47 | 	- Trans*H4CK was conceived as a response to the growing social and economic barriers that plague the trans community. Trans*H4CK tackles these problems by developing new and useful open source tech products that benefit the trans and gender non-conforming communities, as well as serving as a meeting point for trans and GNC individuals interested in pursuing employment and those that are currently working in the industry.
48 | 	- You can sign up for Trans*H4CK's mailing list on their [official website](http://www.transhack.org/#!contact/c1z0x), or email [transhackathon@gmail.com](mailto:transhackathon@gmail.com) to ask questions about trans* resources or Trans*H4CK events.
49 | 
50 | - [Women Who Code](https://www.womenwhocode.com)
51 | 	- Women Who Code is a global non-profit dedicated to inspiring women to excel in technology careers. They provide an avenue into tech, empower women with skills needed for professional advancement, and provide environments where networking and mentorship are valued. They have 42 (as of September 2014) chapters across the world, which organize technical study groups, coding events, and tech talks by influential women in their respective regions.
52 | 	- You can view a list of upcoming Women Who Code East Bay events, or contact the East Bay organizers, at their [Meetup page](http://www.meetup.com/Women-Who-Code-East-Bay).
53 | 	- You can view a list of upcoming Women Who Code SF events, or contact the San Francisco organizers, at their page [Meetup page](http://www.meetup.com/Women-Who-Code-SF).
54 | 	- You can request that your ClojureBridge event be posted in Women Who Code's worldwide online newsletter by emailing [womenwhocode@gmail.com](mailto:womenwhocode@gmail.com).
55 | 
56 | 
57 | 
58 | New York City and Greater Metropolitan Area
59 | -------------------------------------------
60 | - [Black Girls CODE](http://www.blackgirlscode.com/)
61 | 	- Started in August 2011, this organization reaches out to young girls from underrepresented communities through workshops and after school programs. According to their site, they have used Scratch or Ruby on Rails in the past.
62 | 	- The local chapter of Black Girls Code has a twitter [account](https://twitter.com/VolunteerBGCNY), and they are looking for volunteers. They can also be emailed to [newyorkchapter@blackgirlscode.org](mailto:newyorkchapter@blackgirlscode.org).
63 | 
64 | - [Girl Develop It](http://www.girldevelopit.com)
65 | 	- Girl Develop It is a non-profit organization that exists to provide affordable and accessible programs to women who want to learn web and software development through mentorship and hands-on instruction. 
66 | 	- You can contact the local organizers of Girl Develop It - New York through through their chapter's [website](http://www.girldevelopit.com/chapters/new-york) 
67 | 
68 | - [NYC Tech Latinas](http://www.meetup.com/NYC-Latinas-in-Technology/)
69 | 	- This Meetup group has been around for a year, with over 100 members.
70 | 	- You can contact the local organizers through the [meetup] site, or by checking out their Twitter [page](https://twitter.com/nyctechlatinas).
71 | 
72 | - [Women In Tech New York City](http://www.womenintechnyc.com/)
73 | 	- Women In Tech is part of the larger NY Tech Meetup [group](http://www.meetup.com/ny-tech/), and the list of events can be seen on their [website](http://www.womenintechnyc.com/events). You can sign up for their newsletter on their main page.
74 | 	- As of September 2014, the NY Tech Meetup group has over 41K members. The group helped sponsor a report about the growing tech [economy](http://www.nyctecheconomy.com/) in the city.
75 | 
76 | - [Women Who Code](https://www.womenwhocode.com)
77 | 	- Women Who Code has a local chapter in NYC. For more information, see the Women Who Code entry under SF.
78 | 	- You can view a list of upcoming Women Who NYC events, or contact the NYC organizers, at their [Meetup page](http://www.meetup.com/WomenWhoCodeNYC).
79 | 	- Follow the local chapter Twitter handle [@WomenWhoCodeNYC](https://twitter.com/womenwhocodenyc)
80 | 	- You can request that your ClojureBridge event be posted in Women Who Code's worldwide online newsletter by emailing [womenwhocode@gmail.com](mailto:womenwhocode@gmail.com).
81 | 
82 | - [Ladies Who Code](http://www.meetup.com/Ladies-Who-Code/)
83 | 	- Monthly meetup in NYC, very active and well attended by women with a wide variety of backgrounds, preferred languages, and experience levels.
84 | 	- On twitter: [@ladieswhocode](https://twitter.com/ladieswhocode)
85 | 
86 | - [NYC Ruby Women](http://www.meetup.com/NYC-Ruby-Women/)
87 | 	- Monthly meetup in NYC, which has been around for ~3 years with over 500 members.
88 | 	- On twitter: [@NYCRubyWomen](https://twitter.com/nycrubywomen)
89 | 
90 | - [NYC PyLadies](http://www.meetup.com/NYC-PyLadies/)
91 | 	- Local chapter of the larger PyLadies organization, with multiple events throughout every month.
92 |         - For more information, see the PyLadies entry under SF.
93 | 	- On twitter: [@NYCPyLadies](https://twitter.com/NYCPyLadies)


--------------------------------------------------------------------------------
/Meta-Organizer-Cookbook.md:
--------------------------------------------------------------------------------
  1 | SF meta-organizers are Lillie Chilen and Rachel Myers. This is how we roll.
  2 | 
  3 | ## What's a meta-organizer?
  4 | 
  5 | A meta-organizer finds workshop organizers and venues so that lots of workshops can happen in a given locale. Since we have 1-2 workshops a month in San Francisco, we spread out who's doing the heavy lifting of running each workshop.
  6 | 
  7 | ## How we meta-organize in San Francisco
  8 | 
  9 | In SF, we have a spreadsheet that lists out our prospective organizers / venues, the status of each upcoming workshop, and which of us was responsible for making sure that worskhop took place. This helps us keep track of who's doing what, where, when.
 10 | 
 11 | ### Workflow:
 12 | 
 13 | * At least once per quarter, get together to brainstorm and send emails.
 14 | * Comb through the past volunteer and organizer lists to see who might be willing to organize again or for the first time.
 15 | * Look through our list of companies who have previously offered to host or that we have contacts at and decide who to ask.
 16 | * Send out a bunch of emails to potential organizers and venues.
 17 | * Follow up with those who have questions or are up for it.
 18 | * Connect volunteers and venues to pick a date for their workshop.
 19 | 
 20 | ## Strategies for Recruiting Organizers
 21 | 
 22 | The path often looks something like: student --> TA --> teacher --> organizer, but that's very rough and often steps are skipped. Lots of teachers don't start off as students, for instance, and sometime students are ready to jump right into organizing!
 23 | 
 24 | ### Places to look for organizers
 25 | 
 26 | * Look at your recent volunteers list, and see if you have repeat volunteers. These folks might be up for stepping into the organizer role for a workshop.
 27 | * At the beginning of the workshop, announce that there will be a table at lunch of people talking about organizing a workshop if anyone is interested in that.
 28 | * Ask! And when you ask, ask for nominations as well. They might know someone perfect.
 29 | 
 30 | ## Information & Skills Needed 
 31 | 
 32 | These are the things you need to know and be able to do to be an effective meta-organizer.
 33 | 
 34 | ### Growing the Potential Workshop Organizers List
 35 | 
 36 | Information needed:
 37 | 
 38 | * A list of past organizers, friends, volunteers, and anyone you can think to ask to organize
 39 | * Other humans' suggestions for who to ask
 40 | 
 41 | Skills needed:
 42 | 
 43 | * Ability to ask for help convincingly
 44 | * Participation at events where you can recruit people to the list of potential organizers is hugely helpful
 45 | 
 46 | ### Recruiting Venues + Sponsors
 47 | 
 48 | Information needed:
 49 | 
 50 | * A list of local tech companies; often but not necessarily RoR shops
 51 | * Space / tech requirements for a workshop
 52 | * Benefits to hosting a workshops
 53 | 
 54 | Skills needed: 
 55 | 
 56 | * Research skills to find new venues
 57 | * Ability to email people you don't know
 58 | * Remembering to follow up 
 59 | * Following up
 60 | * Keeping track of who you've asked, so you can follow up
 61 | 
 62 | ### Actually recruiting workshop organizers
 63 | 
 64 | Information needed:
 65 | 
 66 | * A brief pitch of what organizing is and why they should do it
 67 | * Prior experience organizing goes a long way in explaining what it entails
 68 | 
 69 | Skills needed:
 70 | 
 71 | * Ability to email people you don't know
 72 | * Email writing and follow up, remembering to follow up, following up, etc.
 73 | * Ability to keep track of who's been asked, when, and what they said (spreadsheet!)
 74 | 
 75 | ### Matching venues with organizers
 76 | 
 77 | Information needed:
 78 | 
 79 | * Venue's and organizer's availability
 80 | * Where to announce / post when workshop is scheduled
 81 | 
 82 | Skills needed:
 83 | 
 84 | * Tolerance for email back-and-forth to determine date of workshop
 85 | 
 86 | ### Hosting organizer kick-off meeting
 87 | 
 88 | Information needed:
 89 | 
 90 | * Who is organizing
 91 | * General stuff about organizing, to answer their questions
 92 | 
 93 | Skills needed:
 94 | 
 95 | * Ability to schedule drinks/coffee with all the organizers and hopefully the mentor
 96 | * Excitement for RailsBridge and workshops
 97 | * Ability to answer questions about organizing
 98 | 
 99 | ### Making sure the workshop is actually being planned
100 | 
101 | Information needed:
102 | 
103 | * Date of the workshop
104 | * Whether or not the organizers are planning the workshop
105 | 
106 | Skills needed:
107 | 
108 | * Ability to follow up with organizers to make sure things are going okay
109 | * Judgement to determine if one of the organizers is doing all the work
110 | * Communication skills to help resolve issues with organizers / mentors / venues should they arise


--------------------------------------------------------------------------------
/Minimum-Viable-Workshop.md:
--------------------------------------------------------------------------------
 1 | ## What makes a workshop a ClojureBridge Workshop?
 2 | 
 3 | * A commitment by the organizers, teachers, and students to increasing diversity in tech. You can see what that looks like by reading our ["Resources on Diversity" page](https://github.com/ClojureBridge/organizing/blob/master/Resources-on-Diversity.md), or by reading how we typically describe ClojureBridge workshops to attendees:
 4 | 
 5 | > This workshop is for underrepresented groups in tech who are interested in learning programming with Clojure, an expressive, general-purpose programming language. Men, you are welcome if you know a woman who would like to attend and come to learn Clojure together.  ClojureBridge is emphatically queer and trans\* friendly.
 6 | 
 7 | * It's __free__!
 8 | * An Installfest in which participants end up with a functional development environment on their machines.
 9 | * A Workshop day in which participants do hands-on work on some kind of curriculum.
10 | 
11 | 
12 | ## The Bare Necessities
13 | 
14 | Here’s what you need for a minimum viable workshop:
15 | * A space
16 | * Teachers
17 | * Participants
18 | * Teacher Training (as late as during the Installfest)
19 | * Installfest (Friday night)
20 | * Workshop (Saturday day)
21 | 
22 | Any number of factors can decide the size of the workshop: the size of the space, the number of teachers available, or the number students interested. If you're striking out on your own, start small and get bigger.
23 | 
24 | 
25 | ## Finding or Starting an Ecosystem
26 | 
27 | Workshops need to be part of an ecosystem to be successful. It seems to work best when there is a community, events, and resources available locally. For Clojure and women, regular in-person meetings seem to make a big difference. If there isn't already a monthly meetup, plan to start one after the workshop. If you have a large enough community and a founding team with stamina, plan a series of workshops, so that workshop graduates can come back and TA the next workshop. Learn, understand, practice, teach is a powerful sequence. Women often respond to need more than self-promotion; what they won't do for themselves, they will often do for a like-minded community.
28 | 
29 | ### [Back to Cookbook Home](README.md)
30 | 


--------------------------------------------------------------------------------
/Money-Things.md:
--------------------------------------------------------------------------------
 1 | # Money Things
 2 | 
 3 | Money! It's so fun! Or not, depending. Workshops can require dealing with some of it, so here's how we roll.
 4 | (We try to avoid dealing with money by having sponsors order food directly, but that's not always possible. Such is life.)
 5 | 
 6 | 
 7 | ClojureBridge has two types of money managements; short term and long term.
 8 | The short term is for an individual workshop and completes in just one workshop.
 9 | While, the long term may be for a single chapter/area or multiple chapters in more broad area, and the management continues over years.
10 | 
11 | 
12 | ## Short term management
13 | 
14 | This is for the individual workshop, the advice for the organizer.
15 | 
16 | 
17 | ### Plan as early as possible
18 | 
19 | Ideally, when a workshop is scheduled and announced, the organizer should have at least one sponsor who will pay food.
20 | A hosting company may or may not pay. Make sure the hosting company can do something for the workshop.
21 | 
22 | Sometimes, finding sponsors other than the hosting company is very hard.
23 | In such a case, please contact the ClojureBridge board or mentor.
24 | We will help finding sponsors.
25 | Also, it is a good idea to post to the ClojureBridge Workshops mailing list for suggestions and advices from past organizers.
26 | 
27 | 
28 | However, remember, money won't move fast. 
29 | Especially, asking companies to pay money often takes more than two weeks; their decision to process won't go forward instantly.
30 | Planning as early as possible is a key to get sponsors.
31 | 
32 | 
33 | ### What if the organizer is unable to find a sponsor?
34 | 
35 | Despite the organizer's intensive efforts, funding may not go well.
36 | For such an emergency situation, ClojureBridge is able to pay a small amount from ClojureBridge General Fund.
37 | At the same time, please consider the following 3 options:
38 | 
39 | 
40 | Here are suggestions:
41 | 
42 | 1. Lunch only
43 | 
44 |     Don't forget, cutting down to lunch only is totally agreeable.
45 |     So far, most ClojureBridge workshops have successfully provided Friday evening pizza, Saturday breakfast/lunch and drinks.
46 |     But, ClojureBridge workshop is not necessarily so fancy.
47 | 
48 | 2. Potluck style
49 | 
50 |     This depends on the location. Sometime works well but sometime not.
51 |     If the potluck is possible, this has another good side effect - communication between attendees.
52 | 
53 | 3. No food at all
54 | 
55 |     Either encouraging attendees to bring food or eat out, no food at all is among choices.
56 |     However, providing food, at least lunch, is good for this kind of workshop.
57 |     No food style would be the very last choice.
58 | 
59 | 
60 | ### Sample Budget
61 | 
62 | How much money should the organizer raise? Here're some figures in typical US cities based on previous workshops.
63 | 
64 | The main expense is catering for lunch. Other than food, organizer may also need a few supplies (pens, nametags).
65 | This menu totals about $1,000 to $1,200 (currency US$).
66 | 
67 | #### Catering for 60
68 | 
69 | * $200 for Installfest pizza + drinks.
70 | * $150 for coffee + bagels for workshop morning
71 | * $500-700 for Saturday lunch from a catering service/restaurant
72 | * $300 for workshop after-party with drinks and tip for 25 volunteers
73 |  * If you have extra money, it's nice to get some appetizers to share.
74 | 
75 | #### Other Expenses
76 | 
77 | * Name tags and pens shouldn't cost you more than $30.
78 | * The Installfest instructions tell students to get a sticker from a volunteer when their install has been checked. Star stickers work just fine.
79 | * It's helpful to find a space that has the necessary tables/chairs so that you don't have to worry about renting those. 
80 | 
81 | #### Upgrade expenses
82 | * Childcare: Depending on the need and if the chapter wants to offer it, around $150.
83 | * Travel assistance e.g. for female coaches to come over to your city.
84 | * ClojureBridge-Stickers, T-Shirts, notebooks etc. Prices vary.
85 | 
86 | ## Long term management
87 | 
88 | Organizing ClojureBridge workshops on the longterm may lead organizers to upgrade their workshops. If they are doing well on funding they may want to offer a variety on food, childcare or travel assistance.
89 | Nevertheless, sometimes a shortage happens. E.g. one major sponsor drops out last minute or doesn't pay the bill. Therefore, the organizers may want to manage money for a long term. The Berlin chapter for example tries to find sponsors for the after next workshop.
90 | 
91 | If the team is located in the US, there's a choice to become non-profit organization under Bridge Foundry.
92 | If the team is located in Germany, [Travis foundation](http://foundation.travis-ci.org/) will help.
93 | Minneapolis and Berlin teams have experiences, so let us know if your team is interested.
94 | 
95 | 
96 | As of November 2016, Bridge Foundry is planning (still early stage) to have a similar funding system in UK, London base.
97 | Let's see how it will go.
98 | 


--------------------------------------------------------------------------------
/Opinions.md:
--------------------------------------------------------------------------------
1 | Lillie Chilen says:
2 | * Don't be a hero. Delegation is hard for some people, but if you don't delegate, your head might pop off your body. Ask for help.
3 | * Most of the volunteers will be teachers, so unless you recruit dedicated non-teaching volunteers, prepare to lasso some volunteers and get them to help with whatever needs doing. 
4 | 
5 | What do you say?
6 | 
7 | [Back to the Cookbook](README.md)
8 | 


--------------------------------------------------------------------------------
/People-Subcommittees-and-GTD.md:
--------------------------------------------------------------------------------
 1 | ClojureBridge likes to play things fast and loose. Therefore, we don't have a lot of formal organizational structures. If you're wondering who to talk to about stuff regarding ClojureBridge, this is something of a starting place. 
 2 | 
 3 | Please join & send any questions to the [workshop organizer's listserve/Google group](https://groups.google.com/forum/#!forum/clojurebridge-workshops). We all like being in the loop, and those that don't subscribe to the daily digest :D
 4 | 
 5 | ### The Board
 6 | ClojureBridge currently has a five-person board:
 7 | 
 8 | * Katherine "kf" Fellows
 9 | * Yoko Harada
10 | * Ali King
11 | * Jamie Kite
12 | * Bhaskar "Buro" Mookerji
13 | 
14 | ### Major Curriculum Contributors
15 | These folks are good to talk to if you have questions, comments, or thoughts about the curriculum. Or just submit a pull request! 
16 | * Bridget Hillyer
17 | * Sean Corfield
18 | * Yoko Harada
19 | 
20 | ### Online Presence Keepers
21 | Jamie Kite is the point person for updates to the main ClojureBridge site, http://www.clojurebridge.org.
22 | * Jamie Kite
23 | 
24 | 


--------------------------------------------------------------------------------
/Post-workshop-feedback-survey.md:
--------------------------------------------------------------------------------
 1 | ### ClojureBridge Feedback Survey
 2 | 
 3 | ** INSERT SURVEY **
 4 | 
 5 | 1. How likely are you to recommend a ClojureBridge workshop to a friend or colleague?
 6 |    - Very likely
 7 |    - Somewhat likely
 8 |    - Neutral
 9 |    - Somewhat likely
10 |    - Very unlikely
11 | 
12 | 2. What was great?
13 | 
14 | 3. What should we change?
15 | 
16 | 4. What else would you like us to know?
17 | 
18 | 
19 | 
20 | 
21 | [Back to Materials](Templates-and-Materials.md)
22 | 


--------------------------------------------------------------------------------
/Pre-workshop-tasks.md:
--------------------------------------------------------------------------------
 1 | ### <a name="joinlistserve"/>Join the organizer's listserve
 2 | If you haven't already, join: https://groups.google.com/forum/#!forum/clojurebridge-workshops. You can email the list with questions, requests, panic, or jokes. We're all here to help. 
 3 | 
 4 | ### <a name="confirmvenue"/>Confirm dates & details with the hosting venue
 5 | The ClojureBridge meta-organizers have introduced you via email to the contact person at the hosting venue. You'll want to confirm that the dates still work for them, how much room they have (which you will use to guide the RSVP cap on Meetup), and lots of other details. So many, in fact, that we have a whole separate page: [hosting venue questions|hosting venue questions](hosting venue questions|hosting venue questions.md).
 6 | 
 7 | ## Post the event
 8 | 
 9 | In practice, using a closed, invite-only system for recruiting instructors and a more public application such as Eventbrite to register participants in the other roles has worked well. If you have the benefit of a local Clojure group, see whether you can use that group's mailing list or Meetup page to handle registration for the workshop attendees and non-instructor volunteers.
10 | 
11 | ## Survey the students and volunteers
12 | We have a pre-workshop survey that you will send to participants that will help gauge who actually plans on coming and what class levels they will be in. You can add the survey to Eventbrite.
13 | 
14 | ** ADD SURVEY QUESTIONS**
15 | 
16 | ## Arrange catering
17 | 
18 | As you are getting quotes for the catering, check out the [sample budget](Sample-Budget.md). Totals will vary depending on the number of folks there and where you're getting the food, but you shouldn't spend more than $1,500 for the whole workshop.
19 | 
20 | 
21 | ### Installfest
22 | Installfest food is pizza and hopefully salad. If the host has a beer fridge or kegerator to share, that's awesome, otherwise, get some beer, too. 
23 | 
24 | Amounts: 2-3 slices of pizza (20 inch) for each anticipated individual. 
25 | (I.e. Total Volunteers + Attendees = 80, 60% = 48: Roughly 144 slices needed- so 9 pizzas with 16 slices)
26 | 
27 | ### Breakfast
28 | Workshop breakfast is usually coffee & bagels. Arrange to have everything delivered about 15 minutes before Volunteers arrive, so there is food and coffee to greet them.
29 | 
30 | Search around the workshop’s location to find a coffee shop which will deliver it to you, if possible. You need sugar, milk, disposable cups etc. 5 gallons of coffee is usually MORE than enough for 70 people as not everyone will drink coffee.
31 | 
32 | ### Lunch
33 | 
34 | Ask the host location if they have any recommendations for catering companies that they have used before. 
35 | Give the Caterer estimated head count; usually 70% of that number of Yes RSVPs. Ask for a Vegetarian/Vegan option for about a third of the food, and if they will want help clearing away any of the set-up they bring. 
36 | 
37 | If the host company is not paying for it, ask for a quote to submit to Austin for approval. 
38 | 
39 | ## Make after-party reservations
40 | Provided you’ve found a sponsor whose donation has left a little extra after catering, it’s always great to thank volunteers for their time and help with a free drink after the event. This also gives the workshop goers a chance to socialize more and really build some networking connections that will help support them if they decide they now have the bug and want to actually delve into this awesome world of Clojure programming!
41 | 
42 | Find someplace close. The closer the after-party is to the workshop site, the more likely it is that people won’t get lost or distracted between leaving the workshop and arriving at the party. You need a place that has enough unoccupied space for the whole group to gather and mingle. A deserted bar is ideal, a casual restaurant is also good. Most workshops end at 4:30 or so on Saturdays, which tends to be a slow time for bars and restaurants, but it pays to check.
43 | 
44 | Make arrangements with the host location ahead of time. If you can tell a place that you’re estimating X many people will be coming and that you for sure will buy Y many drinks (one for each of your volunteers), that’s often enough to encourage them to go out of their way to support what you’re doing. Some places will offer specials (free drinks, extra food) to entice large groups but even those that don’t should be informed before a horde of people descend on them.
45 | 
46 | Mention the after-party early and often. Some students will fail to read the instructions, some will arrive too late for the opening presentation, and some will finish their coursework early and miss the after-class gathering. The more times you mention the fact and location of the after party the less likely it is that people don’t come because they don’t know about it.
47 | 
48 | If a potential host demands a minimum bar tab or rental fee, go elsewhere! Plenty of places don’t, but some places are in the business of hosting parties. This tends to run $1000 and up, which is too expensive unless you have an after-party sponsor.
49 | 
50 | ## Train the teachers
51 | Set up a teacher training. This often happens during the week of the workshop. If you can't get a separate evening, you can do it during the Installfest, but try to get extra volunteers if you do that. Don't want to leave the student high and dry while teachers discuss best practices. 
52 | 
53 | Take a look at the teacher training slides, which live at [http://docs.railsbridge.org/workshop/more_teacher_training](http://docs.railsbridge.org/workshop/more_teacher_training). 
54 | 
55 | ## Communicate with everyone
56 | A few of the things you'll do:
57 | * Email the pre-workshop survey to the attendees, optionally including a deadline to respond
58 | * Remind attendees to take the pre-workshop survey
59 | * Email the volunteer survey to the volunteers
60 | * Send Installfest instructions to attendees 
61 | * Send logistical info (detailed schedule, parking info, etc.) 
62 | * Ask people at every turn to update their RSVP on Eventbrite if they can't come
63 | 
64 | You can find templates for emails in the [materials section](materials.md) under "Communication".
65 | 
66 | ## Obtain necessary objects: power cords, flash drives, name tags, etc.
67 | 
68 | ## Update the pre- and post-workshop presentation slides
69 | 
70 | ## Figure out student class levels
71 | * Use the [grouping guide](Class-level-grouping-guide.md) to interpret the results of the pre-workshop survey
72 | 
73 | ### [Back to Cookbook](README.md)
74 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | # Get involved
 2 | 
 3 | ClojureBridge aims to increase diversity within the Clojure community by offering free, beginner-friendly Clojure programming workshops for underrepresented groups in tech.
 4 | 
 5 | 
 6 | Early workshops focused on women. Organizers are free to choose a different underrepresented group when planning a workshop. A workshop's description should state the group or groups for which the workshop is to be held.
 7 | 
 8 | 
 9 | ClojureBridge was started in 2014 and is part of [Bridge Foundry](http://bridgefoundry.org/). All around the world there have been workshops organized by people like you! Many people volunteered in different ways. Here are some insights for you to get involved:
10 | 
11 | ## What can you do?
12 | 
13 | There are different ways you can contribute. Maybe you like to...
14 | 
15 | ### ...organize!
16 | 
17 | You want to organize a workshop in your area? Great! Let’s get started! For a [minimal viable workshop](https://github.com/ClojureBridge/organizing/blob/master/Minimum-Viable-Workshop.md) you need to find: 
18 | 
19 | - **A venue:** A safe and quiet space for learners to take their first steps in Clojure. An office leisure space or a co-working space might work.
20 | - **A date:** ClojureBridge is a two-day workshop. Which means you need to find a date for the install party (e.g. Friday evening from 5 PM - 8 PM) and a date for the workshop day (e.g. Saturday 9 AM - 6 PM).
21 | Moreover, there should be a coaches training before the event. To raise awareness on how to coach. This training can be one evening (e.g. 2 weeks) before the event.
22 | - **Coaches:** Coaches help you to teach the attendees. One coach for two attendees is a good ratio.
23 | - **Attendees:** The attendees are the most important part of the workshop. Invite them via mailing lists, social media, posters, flyers etc. Attendees should be women or people from underrepresented groups in tech. Read more about [men’s attendance here](https://github.com/ClojureBridge/organizing/blob/master/Guidance-to-Mens-Attendance.md).
24 | 
25 | We recommend you to join our [workshop mailing list](https://groups.google.com/forum/#!forum/clojurebridge-workshops). When you decided for a date and have found a venue we are happy to receive your information via an issue in our [workshops repository](https://github.com/ClojureBridge/Workshops) on GitHub. Then we will publish your workshop on our website and assign you a mentor who can help you with answers to questions and by providing resources and information.
26 | 
27 | You can find lots of information in our [organizing repository](https://github.com/ClojureBridge/organizing) on GitHub and read about the [Workshop Planning Timeline](Workshop-Planning-Timeline.md). [Resources on Diversity](Resources-on-Diversity.md) provides a number of great resources on how to create a diverse, inclusive event. Feel free to read and contribute to these documents.
28 | 
29 | ClojureBridge follows the BridgeFoundry [Code of Conduct](http://bridgefoundry.org/code-of-conduct/).
30 | 
31 | Last, but not least, you might want to find some sponsors. They can help you provide awesome food, drinks or fancy swag for your learners so that this workshop will stay a memorable event.
32 | 
33 | ### ...coach!
34 | 
35 | As a coach you and your co-coach will teach a small group of attendees Clojure and fundamental programming principles at the workshop. This way you can help to start new carriers in tech. Have a look at our [curriculum](https://clojurebridge.github.io/curriculum/#/1). Coaching is an awesome experience. It helps you understand Clojure better and to practice your explaining skills which is also useful for work.
36 | 
37 | ### ...be a teaching assistant!
38 | 
39 | As a teaching assistant or a “floating coach” you also help attendees learn Clojure. You are not assigned to a fixed group but you can float around and help when questions arise. Being a teaching assistant might be your thing if you just started learning Clojure yourself. 
40 | 
41 | ### ...sponsor or donate!
42 | 
43 | What would ClojureBridge be without our sponsors? Many great companies and private people have sponsored ClojureBridge workshops. With their help it was possible to provide food, drinks, T-shirts, notebooks and stickers for the attendees at different workshops. 
44 | You can help by sponsoring the workshop in your area or abroad but also a [donation to ClojureBridge](http://www.clojurebridge.org/donate) is very welcome to help us spread the word, run our servers etc.
45 | 
46 | ### ...help improve the curriculum!
47 | 
48 | Our curriculum can be found in our [curriculum repository](https://github.com/ClojureBridge/curriculum). You are very welcome to [join our curriculum mailing list](https://groups.google.com/forum/#!forum/clojurebridge-curriculum) and share your ideas.
49 | 
50 | ### ...spread the word!
51 | 
52 | Last, but not least, you can help ClojureBridge by spreading the word! Introduce ClojureBridge at your local meetup groups, especially events for women. Retweet, post and share whatever you find about ClojureBridge. Tell the women YOU know and love about it and encourage them to attend! 
53 | 
54 | ----
55 | 
56 | # Contact
57 | 
58 | Please mail us if you have any questions: <info@clojurebridge.org>
59 | 
60 | ----
61 | 
62 | **Quick access:**
63 | 
64 | * [Cookbook Home](README.md)
65 | * [Minimum Viable Workshop](Minimum-Viable-Workshop.md)
66 | * [Workshop Planning Timeline](Workshop-Planning-Timeline.md)
67 |   * [Finding space, sponsors, volunteers, and students](Finding-space-sponsors-volunteers-and-students.md)
68 |   * [Workshop Planning Tasks](Workshop-Planning-Tasks.md)
69 |   * [Installfest Tasks](Installfest-Tasks.md)
70 |   * [Workshop Tasks](Workshop-tasks.md)
71 |   * [Aftermath](Aftermath.md)
72 | * [Money Things](Money-Things.md)
73 | * [The Three Main Roles](Three-Main-Roles.md)
74 | * [Venue](Venue.md)
75 | * [Templates and Materials](Templates-and-Materials.md)
76 | * [Class Level Grouping Guide](Class-level-grouping-guide.md)
77 | * [Opinions](Opinions.md)
78 | * [FAQ](Frequently-Asked-Questions.md)
79 | 


--------------------------------------------------------------------------------
/Resources-on-Diversity.md:
--------------------------------------------------------------------------------
 1 | Below is a list of resources, created by people of diverse backgrounds, about how to facilitate inclusive spaces for (cis/trans) women, people of color, and people who identify as LGBTQIA.
 2 | 
 3 | ## On Organizing Diverse, Inclusive Tech Events
 4 | 
 5 | ### From the perspectives of organizers:
 6 | - ["How much it cost us to make more attendees feel safe and welcome at .concat() 2015"](https://medium.com/@boennemann/how-much-it-cost-us-to-make-more-attendees-feel-safe-and-welcome-at-concat-2015-2bc51d4df656) by Stephan Bönnemann
 7 | - ["What Creating the Black Weblog Awards Taught Me"](https://modelviewculture.com/pieces/what-creating-the-black-weblog-awards-taught-me) by Maurice Cherry
 8 | - ["So you want to put on a diverse, inclusive conference"](http://www.ashedryden.com/blog/so-you-want-to-put-on-a-diverse-inclusive-conference) by Ashe Dryden
 9 | - ["Strange Loop thoughts"](http://bridgetconsulting.com/?p=131) by Bridget Hillyer
10 | - ["How to Have an Awesomely Inclusive and Radically Transparent Hackathon"](http://lizthedeveloper.com/how-to-have-an-awesomely-inclusive-and-radically-transparent-hackathon) by Liz Howard
11 | - ["Silicon Chef: Women-centric hardware hackathon"](http://aerialdomo.tumblr.com/post/63998844533/silicon-chef-women-centric-hardware-hackathon) by Christina Liu
12 | - ["Organizing a Successful Open Source Sprint"](http://bitchincode.wordpress.com/2014/04/16/organizing-a-successful-open-source-sprint-a-tale-of-cupcakes-and-rest) by Becka Robbins
13 | - ["Python for Ada!"](http://www.roguelynn.com/words/Support-Ada-Initiative) by Lynn Root
14 | - ["Interview: Ada Developers Academy"](http://modelviewculture.com/pieces/interview-ada-developers-academy) by Elise Worthy
15 | - ["A Code of Conduct is Not Enough"](https://modelviewculture.com/pieces/a-code-of-conduct-is-not-enough) by Maggie Zhou, Alex Clemmer, and Lindsey Kuper
16 | 
17 | ### From the perspectives of attendees:
18 | - ["moving through a hierarchical system"](https://web.archive.org/web/20150202220502/http://anarchival.net/Strange-Loop/) by Amber Adams
19 | - ["Strange Loop 2014: Reflections on my first conference"](http://krisc.github.io/blog/StrangeLoop2014/) by Kris Calabio
20 | - ["Strange Loop 2014"](http://jvns.ca/blog/2014/09/24/strange-loop-2014/) by Julia Evans
21 | - ["Unlocking the Invisible Elevator"](https://modelviewculture.com/pieces/unlocking-the-invisible-elevator-accessibility-at-tech-conferences) by Liz Henry
22 | - ["Strange Loop - You had me at 'Strange'"](http://deadlugosi.blogspot.com/2014/09/strange-loop-you-had-me-at-strange.html) by Margaret Staples
23 | - ["The week of Strange Loop"](http://madhuvishy.in/posts/the-week-of-strange-loop.html) by Madhu Vishy
24 | - ["Five Days of Clojure Immersion at ClojureConj"](http://www.codeadventurer.com/2014/11/22/five-days-of-clojure-immersion) by Persa Zula
25 | 
26 | ## On Diversity in Tech
27 | 
28 | ### Tech Industry Culture
29 | - ["Dear Marginalized People Coming Into Tech"](http://modelviewculture.com/pieces/dear-marginalized-people-coming-into-tech) by Kronda Adair
30 | - ["We Need Critique in Tech"](http://modelviewculture.com/pieces/we-need-critique-in-tech) by Ashe Dryden
31 | 
32 | ### Diversity in OSS
33 | - ["Bringing More Women to Free and Open Source Software"](https://www.youtube.com/watch?v=gDUMXEfvAME) by Karen Sandler
34 | 
35 | ### Resources for Allies
36 | *Useful for workshop volunteers not from the marginalised group(s) targeted by the workshop*
37 | - ["So You Want To Be An Ally"](http://juliepagano.com/blog/2014/05/10/so-you-want-to-be-an-ally) by Julie Pagano
38 | 


--------------------------------------------------------------------------------
/Sample-budget.md:
--------------------------------------------------------------------------------
 1 | The main expense is catering, but you'll also need a few supplies (pens, nametags). Here are some figures from a previous workshop to give you an idea of how much to budget. This menu totals about $1,000 to $1,200 (all currency US$).
 2 | 
 3 | ## Catering for 60
 4 | * $200 for Installfest pizza & beer. Typical order: nine large pizzas (at least three cheese and/or vegetarian), sliced into sixteen pieces; one case of beer.
 5 | * $100 for coffee for workshop morning
 6 | * $500-700 for Saturday lunch from a catering service/restaurant
 7 |  * Getting food from a grocery store like Whole Foods is way cheaper than hiring a restaurant. I ordered 70 pounds of food (a variety of pasta and regular salads and hummus) for a workshop with about 100 students and volunteers. The total came to $584 and there were leftovers.
 8 | * $300 for workshop after-party with drinks and tip for 25 volunteers
 9 |  * If you have extra money, it's nice to get some appetizers to share.
10 | 
11 | ## Other Expenses
12 | * Name tags and pens shouldn't cost you more than $30.
13 | * The Installfest instructions tell students to get a sticker from a volunteer when their install has been checked. You'll want to procure stickers from your sponsor if possible, otherwise star stickers work just fine.
14 | * It's helpful to find a space that has the necessary tables/chairs so that you don't have to worry about renting those. 


--------------------------------------------------------------------------------
/TA Training.md:
--------------------------------------------------------------------------------
 1 | * **Introduce yourselves!**
 2 | 
 3 |   Spend some time learning each others' names, along with everyone's backgrounds in Clojure, functional programming, and programming at large.
 4 | 
 5 | * **Review the RailsBridge teacher training slides.**
 6 |   
 7 |   They live at http://docs.railsbridge.org/workshop/more_teacher_training.
 8 | 
 9 | * **Determine how TAs should approach students, taking into account the layout of your classroom.** 
10 | 
11 |   For example, if your classroom space is large enough to do so, it's usually preferable to seat students in clusters, which help facilitate discussion. In this case, it's best to divide the TAs, (informally) assigning them to assist a cluster or two at a time. 
12 | 
13 |   However, if your classroom has tables arranged in rows facing forward, it may be preferable to have TAs seated amongst the students; having TAs along the edges of the rows will make them less approachable, and having TAs walk along the rows could block students' view of the teacher and slides.
14 | 
15 | * **Choose a circus ringmistress!**
16 | 
17 |   As [described in the ClojureBridge docs](https://github.com/intuedge/Railsbridge-docs/wiki/Three-Main-Roles), the circus ringmistress acts as the face of your workshop the day it takes place.
18 | 
19 |   The ringmistress should welcome everyone to your workshop with a "What are we doing here?" introduction, then help send people to the appropriate groups (if you are running a workshop with multiple beginner/intermediate/advanced groups).
20 |  
21 |   The ringmistress should also be in charge of opening issues (and submitting PRs, if possible!) for your workshop's curriculum repo as you encounter challenges throughout the day. Teachers and TAs will probably be tempted to open issues and submit PRs to the repo themselves, but it's preferable that the ringmistress handle it, instead; teachers and TAs should stay focused on helping attendees learn to code!
22 | 
23 |   Finally, throughout the day, the ringmistress should announce to the group when food is being served, breaks should be taken, etc., so that the workshop can stay on track.
24 | 
25 | * **Make sure all volunteers know where the unisex and women's bathrooms are.**
26 | 
27 |   In addition, if your workshop is being hosted in a space that requires a key to use the bathroom, be sure that the key is freely accessible to all attendees (preferable), or that a non-male volunteer keeps track of the key--so that women and gender minorities are not required to ask permission from men to use the bathroom.
28 | 
29 |   Also, particularly if your workshop is being hosted in a tech office, overstock the unisex and women's bathrooms if at all possible. Tech offices are typically male-dominated spaces, so unisex and women's bathrooms might not be fully stocked, by default.


--------------------------------------------------------------------------------
/Teacher-Training.md:
--------------------------------------------------------------------------------
 1 | We **strongly** recommend running a teacher training event for your teachers and teaching assistants prior to the workshop. This teacher training session should generally be scheduled a few days prior to your workshop - this keeps it fresh in everyone's mind.
 2 | 
 3 | Teacher training generally covers two areas:
 4 | 
 5 | * Being a good teacher and being sensitive to the students' needs
 6 | * Agreeing on the style of how the workshop will run
 7 | 
 8 | ## Being a Good Teacher
 9 | 
10 | We currently rely on the [RailsBridge teacher training](http://docs.railsbridge.org/workshop/more_teacher_training) slide deck.
11 | 
12 | _We'd love a volunteer to adapt this into something specific to ClojureBridge - hint, hint!_
13 | 
14 | We want the install fest and the workshop to be a fun, friendly, welcoming environment for learning! Encourage questions, be supportive - don't criticize, don't take over their computer, don't use jargon. Keep an eye our for students who are struggling and help them - encourage them.
15 | 
16 | ## Running the Workshop
17 | 
18 | If you haven't already, decide who is going to lead the class(es) through the slides - it can be tiring to be the presenter all day so tag-teaming the presentation part might be a good idea. Decide who is going to keep an eye on the time to help track the pace of the workshop, the exercises, and the breaks. It's a good idea to designate someone as the notetaker for the day, writing down things that would be good to cover in the teacher / TA retrospective after the workshop is complete.
19 | 
20 | Consider how or if you'll handle breaking the group into separate classes based on ability and running multiple classes through the material - at a different pace, with different exercises.
21 | 
22 | Make sure everyone has run through the workshop slides and the narrative of the curriculum and feels comfortable with the flow. Since not all of your teaching assistants will necessarily have Clojure skills, figure out who your "go to" people are so everyone knows how to get "unstuck" when the students ask questions where you don't know the answer.
23 | 
24 | Above all, this is your collective chance to ask questions about the install fest and the workshop process so that you're all on the same page, to help the workshop run smoothly.


--------------------------------------------------------------------------------
/Templates-and-Materials.md:
--------------------------------------------------------------------------------
 1 | ### Post Workshop Survey
 2 | * [Post workshop feedback survey](Post-workshop-feedback-survey.md)
 3 | 
 4 | 
 5 | ### Miscellania
 6 | * [Hosting venue questions](Hosting-venue-questions.md)
 7 | * [Class level grouping guide](Class-level-grouping-guide.md)
 8 | * [Sample Budget](Sample-Budget.md)
 9 | * [Wrap-up flyer](https://drive.google.com/file/d/0B4I97LcO3nCAZTdxZm5Sc2ViNDA/edit?usp=sharing)
10 | * [Media Release](https://docs.google.com/document/d/1vPOR2XmlXrkYeIzQtyfNvCCjN8QcB0W52Lac7Oodcik/edit?usp=sharing)
11 | * [ClojureBridge Logo](files/ClojureBridge-logo.svg)
12 | 
13 | * [Announcement Templates](Announcement-templates.md)
14 | * [Letters to students](Letters-to-students.md)
15 | 
16 | ### [Back to Cookbook home](README.md)
17 | 


--------------------------------------------------------------------------------
/Three-Main-Roles.md:
--------------------------------------------------------------------------------
 1 | There are basically three roles to be filled by organizers, which in theory could be done by one superhuman, but is more realistically split between two people.
 2 | 
 3 | First, **the communicator**. This includes publicizing the workshop on Meetup, works on getting more women to teach, and makes sure everyone knows where they're going and what they are required to show up with (laptops, power cords). This role sends a lot of emails before the workshop, and is most visible to the students and teachers before the workshop happens.
 4 | 
 5 | Second, or the **stage director** (or logistics) role. This role includes stuff like planning food (if not handled by the venue), making sure the physical objects like extension cords and name tags get to the venue, and getting people signed in. There will probably be volunteers for any one of these tasks, but the stage director puts the volunteer there to do it.
 6 | 
 7 | Lastly is **circus ringmistress**, who welcomes everyone to the circus with an entertaining "what are we doing here" intro and sends people off to classes and be amazed by their own feats of strength. At the end this person inspires people to continue, with study groups and online resources, then points them to the after-party bar. (Our analogies sometimes break down.)
 8 | 
 9 | There's a technical requirement for the circus mistress because the presentations are maintained on Github and it's convenient if the circus master can clone and make pull requests as needed for their workshop. (Note, if you're a born circus-master but don't feel comfortable with git, we love git and always happily spread the good-git news.)
10 | 
11 | There are plenty of other things that could go into one person's bucket over the other. The three roles have more and less work at various points, so it might make sense for you to trade off being stage director before and during the weekend, in addition to your other role.
12 | 
13 | Mostly, talk to your co-organizer about their strengths, weaknesses, and what they want to do. Figure out how to have the most fun.
14 | 
15 | ### [Back to the Cookbook](README.md)
16 | 


--------------------------------------------------------------------------------
/Translation.md:
--------------------------------------------------------------------------------
 1 | # Translated Materials
 2 | 
 3 | To make ClojureBridge more accessible to people whose first language isn't English, you can help by translating the organizing materials and curriculum.  Fork the original repo from the ClojureBridge organisation, rename it to reflect the language, and link it here.
 4 | 
 5 | 
 6 | ## Organizing
 7 |     Example:
 8 |     [organizing-nl](www.github.com/username/organizing-nl) - Dutch organizing repo (in progress)
 9 |     
10 | ## Curriculum
11 | 
12 | - [curriculum-es](https://github.com/dialelo/curriculum-es) - Spanish curriculum repo (in progress)
13 | 


--------------------------------------------------------------------------------
/Venue.md:
--------------------------------------------------------------------------------
1 | The venue for your workshop should have the following:
2 | * Wireless internet access
3 | * An open area large enough to fit all participants (for the Installfest and intro/closing presentations)
4 | * Spaces for small groups 
5 |  * This could be meeting rooms, lounges, or any nook that is adequately sequestered from other groups.
6 | 
7 | Ideally, your small groups will have access to a white board or large sticky notes or some way of writing information on the board. They should also have a projector or monitor to look at things together, but if you have to pick between being able to write notes on the board and seeing a screen, choose writing notes. 


--------------------------------------------------------------------------------
/Workshop-Planning-Tasks.md:
--------------------------------------------------------------------------------
  1 | ## When You Sign Up
  2 | 
  3 | ### <a name="joinlistserve"/>Join the organizer's listserve
  4 | If you haven't already, join: https://groups.google.com/forum/#!forum/clojurebridge-workshops. You can email the list with questions, requests, panic, or jokes. We're all here to help.
  5 | 
  6 | ### <a name="confirmvenue"/>Confirm dates & details with the hosting venue
  7 | You'll want to confirm that the dates work for them, how much room they have (which you will use to guide the RSVP cap on Eventbrite), and lots of other details. So many, in fact, that we have a whole separate page: [hosting venue questions](Hosting-venue-questions.md).
  8 | 
  9 | ### <a name="meetmentor"/>Meet your mentor
 10 | If this is your first time organizing, the meta-organizers will set you up with a mentor to answer questions as they arise. Say hello now, in person or in the ether!
 11 | 
 12 | ### <a name="calendarlisting"/>Add your event to the ClojureBridge events website
 13 | 
 14 | Please see the [Workshops](https://github.com/ClojureBridge/Workshops) repo for details. You will need to create a GitHub issue in that repo using the template provided.
 15 | 
 16 | ### <a name="clojure.org"/>Submit a pull request to clojure/clojure-site
 17 | 
 18 | Upcoming events are displayed at [clojure.org/community/events](http://clojure.org/community/events). The Clojure website is backed by a Git repository which lives on [GitHub](https://github.com/clojure/clojure-site).
 19 | 
 20 | Before submitting a pull request to clojure/clojure-site you must sign the [Clojure Contributor Agreement](http://clojure.org/community/contributing_site#contributor).
 21 | 
 22 | Create a file similar to [clojurebridge\_berlin.adoc](https://github.com/clojure/clojure-site/commit/b1c8aed9430e24682f8286f83973b7dab5c66efa#diff-99d8e8fcb89e3797945e1248e063941c) then submit a pull request. When the pull request is merged the event will appear on the Clojure website.
 23 | 
 24 | ### <a name="bridgetroll"/>Post the event on Eventbrite
 25 | 
 26 | You can use whatever event hosting system you'd like, but most organizers have used Eventbrite.
 27 | 
 28 | Copy an old workshop, update the details with your own, and have someone else read through it before posting. Because most people forget to update at least one piece of information, to various levels of tragedy.
 29 | 
 30 | Eventbrite can be used to
 31 |  * Record and modify RSVPs for Students and Volunteers
 32 |  * Email all students and/or volunteers
 33 |  * Create signup sheets for students and volunteers on Installfest and Workshop days
 34 | 
 35 | _In the week before the event, send pings to your students through Eventbrite to remind them that they can return to Eventbrite to modify their RSVP, class level preference, dietary and child care needs._
 36 | 
 37 | ### <a name="survey"/>Survey the students and volunteers
 38 | 
 39 | Eventbrite can handle all pre-workshop surveying of students and volunteers.
 40 | 
 41 | ### <a name="catering"/>Arrange catering
 42 | 
 43 | As you are getting quotes for the catering, check out the [sample budget|sample budget](sample budget|sample budget.md). Totals will vary depending on the number of folks there and where you're getting the food, but you shouldn't spend more than $1,500 for the whole workshop.
 44 | 
 45 | ### Installfest
 46 | Installfest food is pizza and hopefully salad. If the host has a beer fridge or kegerator to share, that's awesome, otherwise, get some beer, too.
 47 | 
 48 | Amounts: 2-3 slices of pizza (20 inch) for each anticipated individual.
 49 | (I.e. Total Volunteers + Attendees = 80, 60% = 48: Roughly 144 slices needed- so 9 pizzas with 16 slices)
 50 | 
 51 | ### Breakfast
 52 | Workshop breakfast is usually coffee & bagels. Arrange to have everything delivered about 15 minutes before Volunteers arrive, so there is food and coffee to greet them.
 53 | 
 54 | Search around the workshop’s location to find a coffee shop which will deliver it to you, if possible.  Not everyone will drink, but make sure to have plenty as many will refill their cups throughout the day. Remember to request extra cups & cream.
 55 | 
 56 | ### Lunch
 57 | 
 58 | Ask the host location if they have any recommendations for catering companies that they have used before.
 59 | Give the Caterer estimated head count; usually 70% of that number of Yes RSVPs. Ask for a Vegetarian/Vegan option for about a third of the food, and if they will want help clearing away any of the set-up they bring. You can save some money if one of the organizers has a car and is willing to return the dishes to the company after the event.
 60 | 
 61 | If lunch will be delivered, please make sure they come at least 30 minutes beforehand so you & your team have time to set up.  When setting up, try to make sure the food is accessible by many at the same time (perhaps various stations?) as lunch time goes by so fast.
 62 | 
 63 | ###  <a name="cookies"/>Clojure cookies
 64 | We have a history of having cookies with the Clojure logo printed on them so students can "take a bite out of Clojure." These can get expensive, though, so make sure you have enough sponsorship before you order these. Most bakeries can do logo cookies.
 65 | 
 66 | ### <a name="afterparty"/>Make after-party reservations
 67 | It’s always great to thank volunteers for their time and help with a free drink after the event. This also gives the workshop goers a chance to socialize more and really build some networking connections that will help support them if they decide they now have the bug and want to actually delve into this awesome world of Clojure programming!
 68 | 
 69 | Find someplace close. The closer the after-party is to the workshop site, the more likely it is that people won’t get lost or distracted between workshop and party. A deserted bar is ideal, a casual restaurant is also good. Most workshops end at 4:30 or so on Saturdays, which tends to be a slow time for bars and restaurants, but it pays to check.
 70 | 
 71 | Make arrangements with the location ahead of time. If you can tell a place that X many people will be coming and you will buy Y many drinks (one for each of your volunteers), that’s often enough to encourage them to go out of their way to support what you’re doing. Some places will offer specials (free drinks, extra food) to entice large groups but even those that don’t should be informed before a horde of people descend on them.
 72 | 
 73 | Mention the after-party early and often. The more times you mention the fact and location of the after party the less likely it is that people don’t come because they don’t know about it.
 74 | 
 75 | If a potential host demands a minimum bar tab or rental fee, go elsewhere! Plenty of places don’t, but some places are in the business of hosting parties. This tends to run $1000 and up, which is too expensive unless you have an after-party sponsor.
 76 | 
 77 | ###  <a name="trainteachers"/>Train the teachers
 78 | Set up a teacher training. This often happens during the week of the workshop. If you can't get a separate evening, you can do it during the Installfest, but try to get extra volunteers if you do that. Don't want to leave the student high and dry while teachers discuss best practices.
 79 | 
 80 | Take a look at the teacher training slides, which live at [http://docs.railsbridge.org/workshop/more_teacher_training](http://docs.railsbridge.org/workshop/more_teacher_training).
 81 | 
 82 | This is very important, and we *strongly* recommend that you do this, in person, ahead of the actual workshop.
 83 | 
 84 | From Sean, the organizer of the first San Francisco workshop:
 85 | 
 86 | "[The training slide deck] has a few parts that are RailsBridge-specific but most of it is about how to encourage a safe, welcoming environment for learning, and how to ensure TAs are prepared to help everyone get the most out of the workshop: how to get students engaged, how to deal with potential issues before they escalate, how to make sure everyone is happy and learning, and not getting frustrated.
 87 | 
 88 | Yes, it's yet one more thing to organize on everyone's calendar, and it means one more space to find a host for and more food/drink to pay for but it really is absolutely worth the effort! Trust me, it made a huge difference for us in San Francisco!"
 89 | 
 90 | ### <a name="communicate"/>Communicate with everyone
 91 | A few of the things you'll do:
 92 | * Send Installfest instructions to attendees
 93 | * Send logistical info (detailed schedule, parking info, etc.)
 94 | * Ask people at every turn to update their RSVP on Eventbrite if they can't come or if their info needs changing.
 95 | 
 96 | You can find templates for emails in the [materials section](Templates-and-Materials.md) under "Communication".
 97 | 
 98 | 
 99 | ### <a name="childcare"/>Arrange childcare
100 | * Anecdotally, few people take you up on childcare; more people tend to use nursing/pumping space, actually.
101 | * It's worth checking with the people who said they needed childcare to make sure they still really do. Many do not realize that you really will provide it if they ask, and will try and make other arrangements after requesting it. Check in with them as soon as you can after the initial request to confirm.
102 | 
103 | Here are two resources you could use for finding childcare providers:
104 | * http://conferencechildcare.com/
105 | * https://www.urbansitter.com/
106 | 
107 | ### <a name="objects"/>Obtain necessary objects: power cords, flash drives, name tags, pens, etc.
108 | 
109 | ### <a name="swagbags"/>Swag bags
110 | If sponsors have given books or other giveaway goods, collect those items and bags in which to distribute them. Eric Normand has very generously offered his Intro to Clojure LispCast videos free of charge to ClojureBridge students, teachers, TAs, and organizers. So get in touch with him to find out how to distribute those: [http://purelyfunctional.tv/intro-to-clojure](http://purelyfunctional.tv/intro-to-clojure).
111 | 
112 | 
113 | ### <a name="slides"/>Update the pre- and post-workshop presentation slides
114 | * Templates and instructions live in [Templates and Materials](Templates-and-Materials.md)
115 | 
116 | ### <a name="levels"/>Figure out student class levels
117 | * Use the set up a rough guesstimate of number of groups and sizes. It is very helpful to arrange the sections again the night before, after everyone has checked in at the installfest; that way you have a much better idea of what your actual workshop attendance will be.
118 | 
119 | 
120 | ### [Go to Cookbook home](README.md)
121 | 


--------------------------------------------------------------------------------
/Workshop-Planning-Timeline.md:
--------------------------------------------------------------------------------
 1 | ### First Steps
 2 | * [Join the organizer's listserve](Workshop-Planning-Tasks.md#joinlistserve)
 3 | * [Meet your workshop mentor, if first time organizing](Workshop-Planning-Tasks.md#meetmentor)
 4 | * [Identify existing communities to collaborate with](Finding-space-sponsors-volunteers-and-students.md#find_community)
 5 | * [Recruit volunteers to teach, TA, and help you plan](Finding-space-sponsors-volunteers-and-students.md#find_volunteers)
 6 | * [Find a space](Finding-space-sponsors-volunteers-and-students.md#find_space)
 7 | * [Find a sponsor](Finding-space-sponsors-volunteers-and-students.md#find_sponsor)
 8 | * [Recruit participants](Finding-space-sponsors-volunteers-and-students.md#find_students)
 9 | * [Confirm dates & details with the hosting venue](Workshop-Planning-Tasks.md#confirmvenue)
10 | * [Add your event to the ClojureBridge events web site](Workshop-Planning-Tasks.md#calendarlisting)
11 | 
12 | ### Somewhere Around Three Weeks Before
13 | * [Post the event on Eventbrite](Workshop-Planning-Tasks.md#meetup)
14 | 
15 | ### Two Weeks Before
16 | * [Train the teachers](Workshop-Planning-Tasks.md#trainteachers)
17 | * [Survey the students and volunteers](Workshop-Planning-Tasks.md#survey)
18 | * [Arrange catering](Workshop-Planning-Tasks.md#catering)
19 | * [Make after-party reservations](Workshop-Planning-Tasks.md#afterparty)
20 | * [Communicate with everyone](Workshop-Planning-Tasks.md#communicate)
21 | * [Arrange childcare](Workshop-Planning-Tasks.md#childcare)
22 | 
23 | ### One Week Before
24 | * [Obtain necessary objects (power cords, flash drives, name tags, etc.)](Workshop-Planning-Tasks.md#objects)
25 | * [Update the pre- and post-workshop presentation slides](Workshop-Planning-Tasks.md#slides)
26 | * [Figure out student class levels](Workshop-Planning-Tasks.md#levels)
27 | 
28 | ### At the Installfest
29 | * [Set up a good Installfest space](Workshop-Planning-Tasks.md#installspace)
30 | * [Set up a welcome desk with class level confirmation](Workshop-Planning-Tasks.md#welcomedesk)
31 | * [Identify a Github point person for real-time updates](Workshop-Planning-Tasks.md#updates)
32 | * [Deal with inevitable issues](Workshop-Planning-Tasks.md#installfestissues)
33 | 
34 | ### At the Workshop
35 | * [Set up! Welcome desk, presentation space,  classrooms, & food](Workshop-tasks.md#setup)
36 | * [Greet, check in, and nametag students and volunteers](Workshop-tasks.md#greet)
37 | * [Give the opening presentation](Workshop-tasks.md#opening)
38 | * [Figure out who really showed up; match students & teachers accordingly](Workshop-tasks.md#remixlevels)
39 | * [Keep time: remind/make all groups take breaks](Workshop-tasks.md#timekeeper)
40 | * [Feed people lunch, make them go back to class](Workshop-tasks.md#lunch)
41 | * [Email post-workshop survey link](Workshop-tasks.md#postsurvey)
42 | * [Give the closing presentation](Workshop-tasks.md#closing)
43 | * [Facilitate the teacher retro](Workshop-tasks.md#teacherretro)
44 | * [Party party party!](Workshop-tasks.md#afterparty)
45 | 
46 | ### Aftermath
47 | * [Send follow-up encouragement to students, thank yous to teachers & host space](Aftermath.md#-send-follow-upsthank-yous-to-students-teachers-sponsors--host-space)
48 | * [Send a writeup and survey results to the organizer's listserve](Aftermath.md#-send-a-writeup-of-the-weekend-to-the-organizers-listserve)
49 | * [Get reimbursed](Aftermath.md)
50 | * [Update this wiki with your brilliant discoveries](Aftermath.md)
51 | 
52 | ### [Back to Cookbook Home](README.md)
53 | 


--------------------------------------------------------------------------------
/Workshop-tasks.md:
--------------------------------------------------------------------------------
 1 | ## Workshop Tasks
 2 | _These bulletpoints make great checklists.  If you need to refer to them day-of, copy, organize them to your liking, and print out a copy for your back pocket._
 3 | ### <a name="setup"/> Set up: welcome desk, presentation space, classrooms, & food
 4 | * Figure out where you're going to send people who show up without an Installfest Success Sticker so that a volunteer can check their install.
 5 | * Make sure you know how to turn on the projector for the opening presentation
 6 | * Figure out how many class spaces you need and double check that the classrooms/conference rooms have the necessary projectors or monitors & corresponding cords
 7 | * Helpful signs
 8 |   * Wifi Code & Social Hashtag - #ClojureBridge
 9 |   * Directions to the bathrooms
10 |   * Classrooms marked by class level
11 |   * Giant "check in here" sign for welcome desk
12 | * Put the food out in some kind of attractive manner.
13 | 
14 | ### <a name="greet"/> Greet, check in, and nametags
15 | * Pretty much the same drill as check in for the Installfest: check all attendees in on your signin sheet from Eventbrite with multiple 'checkeriners,' confirm volunteers' class level and assignment, hand out name tags, and if someone doesn't have the Installfest Success Sticker, send them to some area where their install can get checked. If they don't have a working machine by the time the opening presentation starts, send them home.
16 | * If the main breakfast area has a projector, it is really helpful to put up the class arrangements while people are eating. This way, once attendees are checked in, they can just see for themselves where they have been assigned.
17 | * When the first volunteer capable of this walks in, make them a 'checkeriner' and delegate.
18 | * Teachers & volunteers should again be clearly marked on their name tags
19 | 
20 | ### <a name="opening"/> Give opening presentation
21 | * This is where you tell the students a little bit about yourself, what brought you here, and go through those introductory slides that you updated. It’s also a good time to show a timeline for the day and mention that there will be a wrap-up session before everyone heads out the door. This beginning session sets the tone for the workshop and is intended to get people excited about what they’re going to learn today.
22 | * Give an overall schedule for the day so that both students and teachers are aware of what time breaks, lunch and end of class should be.
23 | * If the hosting venue or sponsor is giving a pitch or demo, confirm the time limit before hand and hold them to it.
24 | * It's also a great time to announce proper recycling/composting/landfilling procedures, where the water fountain is, and where the bathrooms are.
25 | 
26 | 
27 | ### <a name="remixlevels"/> Figure out who really showed up; match students & teachers accordingly
28 | * One good workflow is to meet with the teachers elsewhere in the space while the opening presentation is happening. You can confirm who is TAing and who is teaching, and any class level preferences. If you haven't already assigned classrooms, this is a good time to send the teacher/TA teams out to claim spaces.
29 | * There are a lot of different ways to get students into their small groups. Two strategies are outlined in great detail in the [class level grouping guide](Class-level-grouping-guide.md).
30 | 
31 | ### <a name="timekeeper"/> Keep time: remind/make all groups take breaks, eat lunch
32 | * Depending on how late you started, you may or may not need to enforce a morning break. Generally people are very focused, and you have to remind them to get some fresh air. (The conference rooms of most offices tend to get pretty stuffy with that much learning.)
33 | * A non-lunch afternoon break is *essential*.
34 | * Nominate the loudest organizer or volunteer to do the post-break "go back to your classes" yell.
35 | * If there's a class in the Installfest/presentation space, and that space is where the food is going to be, have them get their food first, so their class isn't interrupted by hordes of hungry coders.
36 | 
37 | ### <a name="lunch"/> Feed people lunch, make them go back to class
38 | * Deal with lunch when it arrives. Announce proper recycling/composting/landfilling procedures.
39 | * Get your yeller to send 'em back to class.
40 | 
41 | ### <a name="postsurvey"/> Email post-workshop survey link
42 | * Sometime after the last break, email the attendees a link to the post-workshop feedback survey. This currently is handled with a google docs form, but soon will be a Bridge Troll tool.
43 | 
44 | ### <a name="closing"/> Closing presentation
45 | * Ask people for some things they learned, and get them excited about what they’ve learned and who they’ve gotten to know as a network of support to keep them involved. Encourage them to come back again, either as an attendee or volunteer. Let them know that it is perfectly okay to alternate between student and volunteer from event to event.
46 | * Make sure you've trained your teachers & TAs to encourage students to come back in each of their classes. If they had a great participant who would be able to volunteer next time in any capacity, get their name right now and pass it to the organizers.
47 | * These handouts provide some resources for continuing learning.
48 | * At the end of the presentation, put up a map of how to walk to the after party and a bit.ly link to feedback survey. Tell everyone to take the survey during the teacher retro and you'll all travel to the place of parties together.
49 | 
50 | ### <a name="teacherretro"/> Retrospectives
51 | * Divide attendees up in order to do both a student and volunteer retrospective.
52 | * Projecting the "I liked... I wish... I will.." starting prompts is a good way to initiate feed back from the crowd. Students don't offer much for "I will...", but volunteers often do.
53 | * Or draw a happy face, a neutral face, a sad face. Ask people to give you feedback for each of them, along with ideas and questions.
54 | * Keep the discussion focused on what happened at that workshop. Kill tangents that go too far off-topic or need to have their own meeting devoted to them.
55 | * Get feedback on curriculum and organization.
56 | * Try not to lead the group down interesting tangents yourself.
57 | * Keep it under 20 minutes.
58 | * Take a picture of the whiteboard at the end and include those in your post-workshop write up.
59 | * Pass out drink tickets to volunteers!
60 | 
61 | ### <a name="afterparty"/> Party party party!
62 | * Go to the party.
63 | * Celebrate!
64 | * If you made pretty drink tickets, see if you can get them back from the bar for reuse.
65 | 


--------------------------------------------------------------------------------
/files/ClojureBridge-logo.svg:
--------------------------------------------------------------------------------
 1 | <?xml version="1.0" standalone="no"?>
 2 | <!--
 3 |     This has been exported from the original PSD file to SVG using Affinity Designer
 4 |     Original PSD can be found here: https://groups.google.com/d/msg/clojurebridge-workshops/JSnNPYTogdc/DBN6wR1EddkJ
 5 | -->
 6 | <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
 7 | <svg width="100%" height="100%" viewBox="0 0 3000 3000" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:1.41421;">
 8 |     <path id="Logo" d="M2447.62,2338.15C2397.29,2408.14 2337.17,2384.77 2352.85,2304.98C2368.61,2219.7 2432.77,2163.22 2510.1,2132.63C2495.94,2225.94 2477.24,2297.18 2447.62,2338.15ZM1203.6,2163.63C1191.77,2125.26 1246.35,2099.28 1315.46,2105.21C1296.01,2169.68 1210.85,2191.57 1203.6,2163.63ZM2228.6,1868.54C2215.85,1956.21 2189.23,1993.43 2169.69,1990.14C2148.05,1986.41 2144,1919.79 2151.07,1866.97C2158,1818.96 2177.4,1766.13 2210.07,1764.52C2216.23,1764.51 2221.04,1764.66 2226.15,1767.51C2225.97,1802.44 2226.38,1836.61 2228.6,1868.54ZM2539.74,1774.74L2534.88,1859.48C2520.76,1928.83 2498.04,1958.07 2481.28,1955.16C2458.97,1951.51 2454.23,1884.96 2462.66,1831.99C2469.59,1783.98 2488.31,1731.23 2521.66,1729.54C2529.85,1729.3 2538.34,1731.77 2545.03,1736.5C2542.87,1747.69 2540.85,1760.24 2539.74,1774.74ZM1658.26,1939.41C1661.8,1879.46 1617.51,1838.58 1564.52,1817.83C1596.94,1783.39 1618.29,1735.81 1618.61,1689.92C1618.81,1600.23 1522.98,1551.43 1413.78,1566.43C1235.93,1591.88 1108.68,1726.63 1102.24,1876.57C1097.86,1983.85 1160.71,2025.39 1230.48,2018.92C1306.94,2011.02 1278.75,1924.52 1278.75,1924.52C1238.21,1947.55 1161.79,1925.33 1159,1851.72C1154.45,1744.08 1249.42,1632.8 1390.02,1617.01C1464.38,1608.67 1530.83,1651.86 1529.85,1716.31C1529.74,1751.92 1517.91,1780.62 1499.15,1802.58C1484.58,1800.79 1470.98,1801.63 1458.14,1803.08C1401.51,1810.8 1391.95,1853.63 1432.82,1864.1C1461,1871.2 1489.24,1866.67 1515.21,1854.17C1544.53,1871.41 1564.85,1906.09 1559.36,1966.94C1549.94,2072.04 1464.48,2091.22 1394.69,2085.37C1405.77,2049.9 1410.15,2009.7 1405.97,1966.37C1382.27,1730.83 1421.2,1687.44 1421.2,1687.44C1418.17,1660.4 1361.19,1628.46 1324.68,1687.32C1291.16,1742.42 1343.25,1834.46 1319.79,2076.66C1218.23,2074.37 1126.56,2123.68 1138.95,2185.26C1153.45,2253.45 1270.4,2240.32 1345.06,2167.6C1360.44,2152.18 1372.89,2135.04 1382.25,2114.83C1505.69,2129.03 1647.91,2085 1658.26,1939.41ZM1863.61,2165.51C1917.47,2169.73 1938.24,2135.23 1928.14,2106.25C1928.14,2106.25 1910.21,2123.32 1881.65,2112.83C1844.37,2097.85 1835.81,1966.71 1867.07,1842.73C1882.25,1782.84 1877.88,1774.43 1774.69,1794.23C1711.68,1806.1 1690.02,1777.73 1690.02,1777.73C1690.02,1777.73 1682.06,1786.15 1681.02,1789.01C1662.12,1815.77 1673.42,1849.41 1701.91,1865.38C1699.86,1914.21 1689.64,1975.59 1671.81,2017.97C1671.81,2017.97 1672.57,2018.58 1672.64,2019.25C1678.06,2030.96 1692.56,2032.07 1701.1,2010.58C1718.63,1965.49 1731.19,1918.9 1737.3,1875.78C1746.24,1876.14 1756.46,1875.68 1767.8,1873.04L1773.81,1871.68C1732.18,2055.69 1772.63,2159.98 1863.61,2165.51ZM2046.25,1756.22C2061.76,1723.67 2058.36,1699.41 2015.07,1685.79C1979.68,1675.39 1944.39,1690.3 1940.01,1730.5C1937.79,1759.5 1949.91,1788.25 1984.1,1794C2007.09,1797.58 2034.11,1782.22 2046.25,1756.22ZM989.64,1690.57C940.82,1761.76 878.52,1737.27 894.203,1657.48C911.528,1567.92 981.097,1510.83 1062.64,1481.14C1050.72,1563.93 1028.64,1635.54 989.64,1690.57ZM2253.18,1429.07C2243.64,1490.38 2236.36,1559.64 2231.33,1630.71L2221.04,1636.66C2114.9,1697.17 2080.44,1585.36 2113.24,1493.38C2164.68,1347.97 2270.93,1312.77 2253.18,1429.07ZM2392.09,1960.47C2408.29,1994.22 2434.57,2012.63 2465.19,2006.94C2497.41,2001.27 2517.21,1976.45 2529.05,1947.75C2526.54,1986.36 2523.12,2023.02 2519.48,2057.65C2419.93,2103.74 2338.82,2186.09 2320.53,2285.34C2288.95,2455.21 2440.47,2457.37 2520.11,2343.7C2554.38,2295.36 2578.63,2212.55 2595.03,2108.72C2641.37,2100.78 2688.55,2100.28 2728.97,2106.69C2801.54,2119.08 2821.72,2158.57 2821.72,2158.57C2856.39,2125.93 2855.24,2042.55 2764.85,2023.95C2713.61,2012.59 2658.48,2015.35 2605.08,2027.51C2611.25,1966.58 2614.7,1899.8 2616.5,1830.46C2618.33,1724.85 2643.54,1693.27 2643.54,1693.27C2611.96,1668.06 2573.88,1670.29 2553.87,1711.55C2544.77,1703.67 2533.87,1698.05 2522,1695.96C2445.14,1682 2382.42,1751.33 2375.25,1852.07C2373.3,1878.63 2375.06,1903.15 2379.95,1924.52C2367.09,1960.65 2348.76,1987.48 2331.41,1985.68C2310.68,1983.9 2305.66,1926.96 2306.94,1865.22C2308.1,1826.76 2311.9,1732.55 2318.92,1636.62C2377.11,1612.29 2436.68,1612.45 2491.83,1622C2563.8,1635.14 2583.83,1673.28 2583.83,1673.28C2618.49,1640.64 2618.7,1557.1 2527.64,1538.58C2452.65,1523.04 2381.47,1547.46 2322.53,1577.35C2325.94,1534.53 2330.1,1492.31 2334.49,1458.27C2366.42,1200.06 2111.48,1337.51 2039.66,1526.97C1988.14,1665.54 2085.83,1767.52 2228.24,1688.56L2225.96,1735.36C2221.6,1733.11 2217.32,1731.53 2211.76,1730.79C2134.22,1716.91 2071.51,1786.24 2064.33,1886.98C2062.83,1907.49 2063.54,1926.79 2066.26,1944.3C2053.57,1989.17 2032.88,2029.65 2012.38,2027.65C1994.35,2025.57 1981.03,1998.32 1987.86,1931.16C1994.47,1861.97 2016.21,1830.09 2016.21,1830.09C1959.39,1799.51 1912.47,1826.68 1902.96,1912.62C1891.95,2009.69 1923.04,2067.12 1975.55,2071.49C2020.7,2074.92 2056.13,2037.69 2077.43,1986.65C2093.13,2025.87 2121.37,2047.98 2154.95,2041.77C2205.27,2032.69 2224.81,1975.06 2233.63,1931.63C2239.77,1986.38 2257.69,2024.07 2293.91,2029.59C2336.41,2035.41 2370.41,2005.7 2392.09,1960.47ZM1325.98,1150.4C1342.92,1045.14 1326.79,999.035 1240.82,1038.12C1240.82,1038.12 1255.43,1064.54 1240.6,1170.25C1227.26,1264.84 1248.6,1332.95 1305.46,1333.41C1349.33,1333.96 1377.14,1282.92 1391.36,1238.89C1397.95,1352.46 1422.43,1405.84 1457.98,1429.91C1499.41,1457.43 1574.21,1446.98 1617.61,1364.07C1628.4,1344.38 1618.93,1333.12 1605.63,1336.67C1605.03,1337.42 1604.36,1337.5 1604.36,1337.5C1575.43,1396.87 1526.69,1407.82 1500.75,1384.04C1470.9,1355.9 1465.14,1249.77 1472.31,1149.03C1477.56,1073.83 1500.1,1012.43 1500.1,1012.43C1457.09,976.876 1395.29,993.398 1390.82,1093.83C1389.95,1122.68 1389.53,1149.42 1388.81,1173.46C1375.3,1248.22 1352.13,1285.73 1334.7,1282.89C1314.49,1279.69 1312.71,1233.34 1325.98,1150.4ZM914.002,1071.39C918.809,1071.53 922.941,1071.75 927.825,1072.57C916.589,1100.53 945.767,1128.74 978.896,1131.18C985.132,1131.85 990.615,1131.92 997.451,1131.84C1003.63,1150.31 1007.34,1171.11 1006.31,1192.45C1002.26,1266.14 960.484,1320.8 916.242,1323.03C874.704,1324.95 851.217,1280.36 854.74,1208.09C857.884,1132.45 880.727,1073.75 914.002,1071.39ZM1560.87,974.808C1521.4,1007.3 1541.94,1104.93 1543.02,1260.88C1542.9,1284.16 1536.08,1296.56 1536.08,1296.56C1602.13,1317.9 1623.28,1286.77 1624.78,1153.81C1658.08,1041.93 1683.42,999.381 1700.85,1002.22C1717.75,1006.48 1705.64,1057.12 1676.24,1093.96C1676.24,1093.96 1758.76,1127.82 1774.47,1072.67C1801.03,980.017 1778.91,953.751 1743.08,951.614C1704.54,949.78 1662.05,973.716 1626.33,1070.13C1630.83,994.334 1643.73,981.248 1643.73,981.248C1643.73,981.248 1602.75,939.305 1560.87,974.808ZM1900.16,1174.23C2055.72,1102.7 2075.83,952.588 1948.19,943.645C1858.57,937.963 1795.56,1010.75 1788.08,1108.79C1781.28,1206.75 1844.67,1265.34 1897.34,1271.06C1987.34,1280.13 2067.27,1217.76 2087.09,1144.35C2092.77,1121.81 2081.65,1114.16 2069.26,1119.66C2068.58,1119.73 2068.66,1120.41 2068.66,1120.41C2054.68,1178.79 1992.24,1232.35 1934.17,1227.23C1879.56,1222.41 1866.92,1146.48 1875.5,1088.7C1882.43,1040.7 1903.15,969.236 1931.78,974.236C1959.65,978.636 1970.02,1107.53 1898.63,1148.4C1874.23,1162.77 1900.16,1174.23 1900.16,1174.23ZM767.103,823.667C789.431,839.641 760.512,972.257 693.229,1122.87C706.883,976.224 740.34,804.768 767.103,823.667ZM1089.48,1088.57C1070.01,1093.71 1050.61,1095.21 1031.74,1095.82C1011.24,1041.3 970.893,1029.41 943.951,1051.6C936.136,1049.05 927.196,1048.69 916.905,1048.47C833.078,1051.72 769.545,1132.1 767.933,1233.58C767.408,1259.45 771.122,1282.37 778.295,1302.1C766.052,1335.5 749.314,1360.12 733.758,1355.84C704.153,1348.21 687.922,1276.79 688.886,1200.02C804.609,974.835 842.231,767.318 778.138,751.241C685.943,728.736 610.841,1004.8 610.072,1186.96C610.167,1224.99 613.173,1259.55 619.494,1289.3C601.316,1352.74 535.264,1411.21 477.929,1405.78C410.166,1399.69 356.038,1295.57 375.934,1155.75C376.307,1152.97 376.679,1150.19 377.651,1146.66C437.206,1134.5 494.718,1110.25 540.345,1071.58C632.951,994.107 629.279,869.942 557.605,859.508C474.288,849.011 345.552,927.806 298.644,1095.3C222.149,1092.61 145.214,1075.43 86.8791,1050.54C277.439,449.582 839.743,14.1406 1503.75,14.1406C2324.58,14.1406 2990,679.558 2990,1500.39C2990,1613.3 2977.41,1723.26 2953.48,1828.97L2950.44,1829.93C2949.77,1830.01 2949.84,1830.69 2949.84,1830.69C2935.86,1889.07 2873.43,1942.62 2815.36,1937.51C2760.74,1932.69 2748.11,1856.76 2756.68,1798.98C2763.61,1750.97 2784.34,1679.51 2812.96,1684.51C2840.84,1688.91 2851.2,1817.8 2779.81,1858.67C2755.41,1873.05 2781.34,1884.51 2781.34,1884.51C2936.9,1812.97 2957.01,1662.87 2829.38,1653.92C2739.76,1648.24 2676.74,1721.03 2669.27,1819.06C2662.47,1917.02 2725.86,1975.62 2778.52,1981.34C2837.75,1987.3 2892.61,1962.34 2928.79,1923.49C2746.7,2538.21 2177.59,2986.64 1503.75,2986.64C682.917,2986.64 17.5,2321.22 17.5,1500.39C17.5,1372.73 33.5958,1248.82 63.9037,1130.54C117.771,1148.8 199.329,1162.42 285.196,1158.41L283.113,1176.44C265.293,1359.15 357.255,1440.54 441.096,1449.61C523.751,1458.15 600.282,1402.32 631.522,1330.96C645.263,1366.49 666.106,1390.75 694.898,1399.9C731.841,1411.19 769.142,1377.71 792.209,1330.65C815.3,1367.3 853.017,1386.69 894.53,1385.7C986.848,1384.92 1040.43,1270.76 1042.74,1187.67C1044.29,1164.91 1042.16,1145.98 1040.26,1129.08C1053.36,1126.84 1066.47,1123.83 1078.96,1120.23C1076.94,1130.81 1075.92,1142.68 1076.09,1155.86C1078.29,1242.55 1077.86,1324.05 1072.54,1398.57C972.149,1437.22 884.426,1515.52 861.88,1637.84C830.376,1808.39 975.441,1820.17 1056.67,1708.37C1096.49,1654.62 1122.84,1572.26 1141.79,1460.62C1187.45,1452.75 1231.92,1452.55 1270.31,1459.19C1342.89,1471.58 1362.99,1510.39 1362.99,1510.39C1398.41,1478.35 1398.02,1395.57 1306.8,1375.69C1260.52,1365.83 1207.79,1365.59 1154.09,1375.04C1160.71,1318.17 1166.49,1253.86 1171.6,1183.47C1177.94,1081.46 1196.17,1060.93 1197.37,1059.42C1160.15,1037.76 1112.35,1043.99 1089.48,1088.57ZM542.314,887.92C596.785,897.547 596.587,987.238 527.991,1040.8C490.689,1068.26 441.957,1085.37 387.879,1091.44C421.599,952.809 487.167,878.367 542.314,887.92ZM1214.87,989.696C1229.7,957.228 1226.3,932.969 1183.09,920.023C1148.3,908.871 1113.01,923.784 1109.3,963.901C1105.73,993.051 1119.2,1021.66 1152.04,1027.55C1175.7,1031.06 1202.73,1015.7 1214.87,989.696Z" style="fill:rgb(51,52,62);"/>
 9 | </svg>
10 | 


--------------------------------------------------------------------------------