Update leader resources

Began making all the leader resources complete and robust.

1. Add becoming a leader details
2. event play book and ideas (needs refinement)
3. Leadership overview contains expectations and responsibilities for
most roles (needs refinement)
4. Added a goals section for us to track what we are aiming for (needs
refinement)

leadership-resources/README.md

@@ -6,20 +6,28 @@ If you're interested in becoming part of the leadership team please see our [bec
 
 ### Table of Contents
 1. [Our Leadership Team](our_leaders.md)  
-2. [Leadership Overview/ Expectations]()  
-3. [Team Norms]()
-4. [Education Team]()
-5. [Network Team]()
-6. [Netowrk Goals]()
+2. [Leadership Overview/ Expectations](leadership_overview.md)  
+3. [Netowrk Goals](network-goals.md)
+4. [Event Inspiration](event-inspiration.md)
+5. [Meetup Playbook](event-playbook.md)
 7. [Becoming a Leader](becoming_a_leader.md)  
 
 
 
 #### Education Team
 
-  The education team coordinates technical events for women to learn and build things related to a specific technology or language.  These events inlcude reoccuring "communites" for specific topics and one off tehcnology events for areas of interest that may not have a reoccuring community interest!
-  
+The education team coordinates technical events for women to learn and build things related to a specific technology or language.  These events inlcude reoccuring "communites" for specific topics and one off tehcnology events for areas of interest that may not have a reoccuring community interest!
+
 #### Network Team
 
-  The network team works on communication, outreach, and partnerships throughout Richmond. They also organize the events targeted towards building the professional networks and skills for all members including public speakers, networking sessions, brunches, etc. 
+ The network team works on communication, outreach, and partnerships throughout Richmond. They also organize the events targeted towards building the professional networks and skills for all members including public speakers, networking sessions, brunches, etc. 
+
+#### New Leads 
+
+Please see our [New and Prospective Leads](becoming_a_leader.md) page for more information about being a lead with Women Who Code Richmond, as well as the [Leadership Overview/ Expectations](leadership_overview.md) information pertaining to leadership roles within the different groups.
+
+#### Existing Leads
+
+Please see the [Leadership Overview/ Expectations](leadership_overview.md) for details on our roles and responsibilities within our network. As we grow and evolve this group we will continue to revist this! 
 
+**Please take note!** This GitHub repository is the main form of institutional memory for our organization. **Issues and Pull-Requests in this repository also serve as a key way for us to make decisions as a group.** Please take note of how to find this repository and [familiarize yourself with git if you need to](https://try.github.io).

leadership-resources/becoming_a_leader.md

@@ -7,12 +7,14 @@ or
 In either case, you're probably a good fit for the job!
 
 Next steps in getting involed are:
+
 ##### Definitely:
-- Read through our [Leadership Overview / Roles and Responsibilities]() to get an idea of what you're thinking of signing up for.
+- Read through our [Leadership Overview & Expectations](leadership_overview.md) to get an idea of what you're thinking of signing up for.
 - If you're interested in leading a specific language group (including algorithms), attend a few meetups to get a feel for how they work
   - Introduce yourself to the current leads. Even if it seems like there are enough leads, they'll still be interested in hearing from you. While it may be possible in the future, we have yet to have too many leads for a group.
 - If you're not in our Slack, [sign up](https://wwcrva-slack.herokuapp.com/)
 
 ##### Probably:
-- Contact our  [Community](https://twitter.com/trishmahan?lang=en) or [Network](https://twitter.com/bcrabb63?lang=en) Directors and say hi if you're not sure what you want to be involved with
-  - _tip:_ If you want to be a language group lead but you don't know which group, attend a few of the ones you might be interested to check it out. Language leads know best how their groups work since they're closer to the day to day aspects of organizing them.
+- Contact our Directors (Trish Mahan, Bri Augenreich, Michele Matthews, or Elisa Parkins) on slack and say hi if you're not sure what you want to be involved with.
+
+  _tip:_If you want to be a language group lead but you don't know which group, attend a few of the ones you might be interested to check it out. Language leads know best how their groups work since they're closer to the day to day aspects of organizing them._

leadership-resources/event-inspiration.md

@@ -0,0 +1,72 @@
+# Meetup Inspiration 
+
+Wondering what type of event you could host, coordinate, and reuqest. Below is a list of "out of the box" ideas and their description to setup! 
+
+**Have an event idea? Submit a PR to add to the list**
+
+We have an assortment of meetup that can be delivered in most languages bascially Out of the Box. 
+
+#### Suggested Meetup Types
+1. Beginner's Night (Install Party!)
+
+    By the end of the night, everyone should have 100% of the tools they need on their computer to be a professional developer
+
+2. Beginner's Night (Coding basics)
+
+    Getting started is hard! At a night like this, we teach beginners `Hello World`, Recursion, or whatever you think they might need
+
+3. Demo Night/Tech Talk 
+
+    Lead(s) or(and) participant(s) gives a talk(s) about cool things they're working on
+
+4. Crash other meetups
+
+    eg, Let's get 20 of us to go to RVA Python together
+
+5. Get a job / Linkedin Updates
+
+  We all meet together and update our LinkedIn + talk about interviews and other things we've needed in getting jobs
+
+6. Happy Hour
+
+7. "How do you google for language X", "How to read the docs"
+
+  more than half of software development can be just reading the docs and searching google. It's a skill that we can teach!
+
+8. Intro to Git for Language X
+
+    Our goal is to have a weekly Git tutorial, rotating across our meetups. We want to be Git evangelists
+
+9. Tech talk planning sessions
+
+    Every one of our members can talk about some technical area. This workshop is a how-to as well as a planning + reviewing platform.
+
+10. Popular Speakers
+
+    Where we pick a topic and invite a speaker to present for us
+
+11. Conference recap 
+
+    people go to large conferences and talk about lessons learned / we show some recorded talks
+
+13. Code Review
+
+    having prepared ahead of time, one or more members present and walk through (a section of) their code. This will allow less experienced coders to learn and experienced coders the space to improve their code.
+
+    _this event differs from **3** (Demo Night) because this event will have a facilitated conversation between the person presenting code and the people reviewing the code (aka everyone else), where Demos are typically less conversational_
+
+14. Study Night 
+
+    TODO 
+
+15. Workshop
+
+    TODO
+
+16. Movie night 
+
+    TODO 
+
+17. Book Club
+
+    TODO 

leadership-resources/event-playbook.md

@@ -0,0 +1,68 @@
+# Event PlayBook 
+
+### Table of Contents 
+
+### Before the Meetup
+- The newest lead and her mentor (the person who recruited her) are responsible for the planning and creation of the Meetup.com event
+  - If you don't have a mentor/know who your mentor is, please bring this up in the Core Team Leads channel or your specific language leads channel!
+  - This **does not imply she must personally create the Meetup.com event or even attend the meetup**
+  - It _is_ the newest lead's responsibility to ask people to volunteer to create the Meetup.com event, commit to attending, etc.
+  - This responsibility will remain with her until another newest lead is recruited
+- Meetups should be sent to the Directors to schedule **on Meetup.com** _at least two weeks (we want months right?) before_ the event. Two weeks is about right for our hosts to feel comfortable that we wont stand them up & for people to make plans to attend but not forget
+- Before a meetup is scheduled on Meetup.com, at least two team leads must commit to being there for the night
+- Please consult the [Location Manager]()for your location logisitcs. and consider the following
+    1. Space for people seated and working? How will it be configured? What is the max number of peopel 
+    2. Outles, projector, wifi logistics
+    3. Who is hosting? (space & wifi) Who is sponroing (food & extras)... be sure to let the host and sponsor know they will have an opprotunty to speak
+    4.
+
+### Day-of Meetup Agenda
+#### Before (6:15-6:30 for a 6:30 event)
+- Arrive 15 Minutes before listed meetup time
+- Make sure you have the host’s phone number
+- At the front door: post signs “Yes! Women Who Code is here!” w/ phone number and directions to the room if necessary
+- In the meetup room write: 
+  - wifi username & password in unambiguous characters
+  - link to slack (`https://wwcrva-slack.herokuapp.com/`)
+  - an ask to tweet to us! @WWCodeRichmond
+
+#### During (6:30-8:00pm)
+- Introduction to  Women Who Code Richmond, our other events, details about your team
+  - Consider saying out [Mission Statement]()
+- Mention wifi, WWC slack, twitter, meetup format, active projects
+- Go around the room and ask everyone to say:
+  - Their name & some background information
+  - What they hope to accomplish at the meetup
+- Encourage people to communicate on Twitter and Slack during the meetup
+- Take attendance! We are looking into the best way to have people sign in 
+- Be asking people what they're working on & **if they'd be comfortable giving a demonstration** 
+  - between 5-20 minutes
+    - we could give them a whole evening if they want!
+  - that night or another week
+- Ask if you can post a picture on Twitter
+
+
+
+#### Demo / Tech Talk Time / Wrap Up (8:00-8:30pm)
+- Try to schedule a demo / project share for 8pm.
+- Go around once more and have everyone say:
+  - Their name
+  - What they accomplished at the meetup
+    - Everyone accomplished something, but they usually don't realize it at first
+    - Ask prodding or clarifying questions. Try to get them to quickly bestow their new knowledge to everyone else in the room. 
+- Make sure they aren’t forgetting things
+- Wrap up with an applaud her 
+
+#### Directly Afterwards
+- Check for forgotten items at the end
+
+#### In the Following Days
+- Follow up on Slack with at least two members.
+  - Ask them about something they said they were working on
+  - See if they need help
+  - Send them another resource 
+  - See if they might be interested in speaking at an event in the future!
+** A simple hello a day or two after the meetup will have a HUGE effect on them coming back and being involved**
+
+- Brag about your members by contributing blog posts and on twitter with an #applaudHer
+- People are eligible for an #ApplaudHer for any measurable accomplishments. First push to GitHub? Applaud Her. New promotion? Applaud Her.  

leadership-resources/leadership_overview.md

@@ -0,0 +1,88 @@
+# Leadership Overview & Expectations 
+
+TODO : Some intro about being volunteer led. Can particapte without being a lead (help a group not commit past that). 
+Help with one event but not mroe. Outlines the expectations of the leads and your responsibilities.  
+
+### Expectation of all Leads 
+
+**Work toward the 2018 Netowrk goals**
+
+- At the end of each year we will come together as a team to recap and plan for the following year. In this we will identify new or recurring [Goals](network-goals.md) for our network
+
+**The most important requirement for our leadership team is that they are active members of the RVA Women Who Code Network.**
+
+- Attend at least 2 meetups a month. You should be visible and engage. This doesn’t mean you have to LEAD but you should be particpating. (going to tons of leadership meetings doesn't count!) 
+- Be active on slack. 
+    1. Welcome new members (the leads who attended a Meetup should each reach out to two newer attendees to follow up about something
+                            leads who didn't attend the Meetup should monitor Slack to welcome new members in the channel by @name)                          
+    2. encourage conversations in the general group 
+    3. provide technical community through slack (post in your repsective technology domain channels )
+
+    **slack is as active as we make it**
+- Attend one quartely lead meeting with directors 
+
+**Be open and committed**
+- When life hits the fan just let us know you need to step back. This is why we have multiple people filling roles, But remember your commitments to your positions 
+- Update github with resources & links posted in relevant channels for your events
+- Coordinate with your leads on a regular basis (consider making a private slack channel to collaborate. for ex: all python leads would join #python-leads)
+- Lean in! (something about helping other areas, coming up with ideas, and invtiting others to join)
+- If you need help making an event, speak to one of the other leads or ask in #core-team on Slack.
+
+**Be a wwcode example**
+- Uphold our [Code of Conduct](../code_of_conduct.md)
+- Know our [mission and vision](https://www.womenwhocode.com/about)
+- Guide new leaders through expectations of being a lead 
+- Hone your craft & develop your self 
+
+
+### Education Team Roles and Responsibilites
+
+**Directors**
+
+- TODO: Responsible for .... smooth education. (one one off a quarte & several communities a month)
+    - Insuring teams have enough bandwidth & gauging lead investment 
+    - Schedule meetups 
+    - Attend newly created meetups for leadership support & one off events
+    - Keep backalog of events and source one-offs/hackathon events 
+    - Grow communites as bandwidth is satisfied 
+
+**Community Leads** 
+
+TODO: responsible for coordinating rercurring meetups around specific technology topic. 
+- Help ensure Communities have to have at least 2 leads, grow to 3 leads. 
+- Leads facilitate scheduling with director on a quarterly basis (can be one event a quarter, a month, a week etc) 
+- Set direction for your community. Take a look at our [event inspiration ](event-inspiration.md) for ideas on types of events your community could have (eel free to mix it up!).
+- Send directors details (Dates, Space, event details) of upcoming meetups in a timley manor (3 months out). Review the [playbook](event-playbook.md) for gudiance on how to approach coordinating meetups.     
+- Share pictures / blurbs for social 
+
+
+
+**One Off leads** 
+
+TODO: responsible for coordinating one off technical meetups as badnwidth and speaker/content availbility allow. 
+- Leads should be actively monitoring the one-off backlog for potential events 
+- Send directors details (Dates, Space, event details) of upcoming meetups in a timley manor (3 months out). Review the [playbook](event-playbook.md) for gudiance on how to approach coordinating meetups.     
+- Share pictures / blurbs for social 
+
+### Network Roles & Responsibilities 
+
+
+**Directors**
+
+Check in with leads on content and networking
+Grow partnerships: update partnerships log
+
+
+**Content Lead** 
+
+TODO: repsonsbile for sharing wwcode mission and values and creating presence in richmond and beyon 
+- Strong understanding of the WWCode core values and mision. 
+- Manage Social Media precesne, Email, Blog Posts, meeting minutes?.
+- Strong communication skills 
+
+
+
+**Leads** 
+
+Brews && Broads; Donuts as examples - two per quarter 
+Dates, Space, Sponsor determined 3 months in advance and sent to director

leadership-resources/network-goals.md

@@ -0,0 +1,14 @@
+# Goals 
+
+#2018 
+
+TODO : 
+
+One of our goals as an organization is to increase the visibility of women in the tech scene in the region. One of the ways we work to accomplish this is to provide the platform for our women to speak! We'd like for all of our leads to be evangelists about
+
+
+#2017 
+
+TODO : 
+
+- host one event per month