update with new exercises for new cohort

explore/blog-interviews.md

@@ -1,14 +1,15 @@
 ##Writing a Post. 
 
-**GOAL:** Write a blog post about the challenge(s) or problem(s) you hope to address throughout the fellowship. 
+**GOAL:** Write a blog post about the fellow fellow you interviewed. 
 
 **FORMAT:** Post on MSL's blog
 
-**TECHNOLOGY:** Wordpress. You should have usernames and logins via Abby. 
+**TECHNOLOGY:** Wordpress. You should have usernames and logins via Aurelia. 
 
 **TIME TO COMPLETE:** 1-2 hours (depending on how fast you write!). 
 
-Using your ideas and notes from the [challenge exercise](https://github.com/mozillascience/fellows-class-2015/blob/master/challenge_exercise.md), write a blog post about what challenges/problems you hope to tackle.
+Using your ideas and notes from the [interview exercise](https://github.com/mozillascience/fellows-class-2016/blob/master/fellow-interviews.md), write a blog post about what challenges/problems you hope to tackle.
+
 The post should be no longer than 700 words (short and sweet). Keep the tone casual, and be sure to use jargon-free or jargon-lite lanaguage so your ideas are accesible to as many of our readers as possible. [Mozilla Foundation Director Mark Surman’s blog](http://marksurman.commons.ca/blog/) is a great model/resource for writing good posts. The bolded statements, the bullet points, these “action items” he uses highlighs key ideas and makes takeaways evident. Feel free to inculde images, diagrams, etc-- the more visuals the better!
 
 NOTE: DO NOT PUBLISH THE POST.  Save it as a draft, we'll publish them after your intro interview posts go out. 

explore/blog-intro.md

@@ -4,11 +4,12 @@
 
 **FORMAT:** Post on MSL's blog
 
-**TECHNOLOGY:** Wordpress. You should have usernames and logins via Abby. 
+**TECHNOLOGY:** Wordpress. You should have usernames and logins via Aurelia. Or your own blog, we can fork the content over. 
 
 **TIME TO COMPLETE:** 1-2 hours (depending on how fast you write!). 
 
-Using your ideas and notes from the [challenge exercise](https://github.com/mozillascience/fellows-class-2015/blob/master/challenge_exercise.md), write a blog post about what challenges/problems you hope to tackle.
+Using your ideas and notes from the [goal exercise](https://github.com/mozillascience/fellows-class-2015/blob/master/goal-setting.md), write a blog post about what challenges/problems you hope to tackle.
+
 The post should be no longer than 700 words (short and sweet). Keep the tone casual, and be sure to use jargon-free or jargon-lite lanaguage so your ideas are accesible to as many of our readers as possible. [Mozilla Foundation Director Mark Surman’s blog](http://marksurman.commons.ca/blog/) is a great model/resource for writing good posts. The bolded statements, the bullet points, these “action items” he uses highlighs key ideas and makes takeaways evident. Feel free to inculde images, diagrams, etc-- the more visuals the better!
 
-NOTE: DO NOT PUBLISH THE POST.  Save it as a draft, we'll publish them after your intro interview posts go out. 
+NOTE: DO NOT PUBLISH THE POST.  Save it as a draft, we'll publish them after and throughout October.

explore/blog-roadmapping.md

@@ -1,14 +1,15 @@
 ##Writing a Post. 
 
-**GOAL:** Write a blog post about the challenge(s) or problem(s) you hope to address throughout the fellowship. 
+**GOAL:** Write a blog post about the roadmap you designed for your fellowship. 
 
 **FORMAT:** Post on MSL's blog
 
-**TECHNOLOGY:** Wordpress. You should have usernames and logins via Abby. 
+**TECHNOLOGY:** Wordpress. You should have usernames and logins via Aurelia. 
 
 **TIME TO COMPLETE:** 1-2 hours (depending on how fast you write!). 
 
-Using your ideas and notes from the [challenge exercise](https://github.com/mozillascience/fellows-class-2015/blob/master/challenge_exercise.md), write a blog post about what challenges/problems you hope to tackle.
-The post should be no longer than 700 words (short and sweet). Keep the tone casual, and be sure to use jargon-free or jargon-lite lanaguage so your ideas are accesible to as many of our readers as possible. [Mozilla Foundation Director Mark Surman’s blog](http://marksurman.commons.ca/blog/) is a great model/resource for writing good posts. The bolded statements, the bullet points, these “action items” he uses highlighs key ideas and makes takeaways evident. Feel free to inculde images, diagrams, etc-- the more visuals the better!
+Using your ideas and notes from the [goal exercise](https://github.com/mozillascience/fellows-class-2015/blob/master/goal-setting.md), write a blog post about how you will try to break down these goals.
 
-NOTE: DO NOT PUBLISH THE POST.  Save it as a draft, we'll publish them after your intro interview posts go out. 
+The post should be no longer than 700 words (short and sweet). Keep the tone casual, and be sure to use jargon-free or jargon-lite lanaguage so your ideas are accesible to as many of our readers as possible. 
+
+NOTE: DO NOT PUBLISH THE POST.  Save it as a draft, we'll publish them accordingly.

explore/description.md

@@ -9,23 +9,20 @@ The end goal of this exercise will be to share your work with the group, incorpo
 
 **TECHNOLOGY:** Your favorite text editor or program to write in, a whiteboard (or paper to scribble on), and a timer. (Feeling distracted? Try Focus Writer or [one of these tools](http://lifehacker.com/5689579/five-best-distraction-free-writing-tools) - many have word counts baked in.
 
-**TIME:** 2.5-3 hours.
+**TIME:** 2 hours.
 
 ===========
 
 ###What is the general idea? (25 words)
 
-***Free-write for 6 minutes; then refine your answer for 5 minutes.***
-
 What change do you want to see as a result of this project? Give us a sense of the context in which this project exists. Main items to include: what is the **problem**, **help needed**, and **desired outcome**. Note: This should be a high-level description (not a full-project roadmap), and written so that a lay-person can understand. 
 
 ###Major work in this space (300 words):
 
-***Note: This is a two-part exercise. Give yourself the full-time allotted for this section, and feel free to go above the time limits listed if you need.***
 
 - **Research (1 hour - 50 words)**: What is the major related work in this field relevant to your problem area? List 5-10 most noteworthy projects addressing the same subjects, issues, or problems, and add a short (1-3 line) summary and/or a link. 
 
-- **Summary (30 minutes - 250 words)**: Now, refine what you've found, and spend the next 30 minutes working to answer the questions below. This summary should include references to important publications or results of other significant efforts in the field. The proposer should describe how his or her work differs from, contributes to, or complements this work.
+- **Summary (10 minutes - 250 words)**: Now, refine what you've found, and spend the next 30 minutes working to answer the questions below. This summary should include references to important publications or results of other significant efforts in the field. The proposer should describe how his or her work differs from, contributes to, or complements this work.
 
 - Some questions to get you started:
  - What was the last big thing to happen on this topic? 
@@ -39,7 +36,7 @@ What change do you want to see as a result of this project? Give us a sense of t
 
 ###What you're going to do (300 words):  
 
-*Spend __20-30 minutes__ sketching out (on paper or a whiteboard) various ways to address your the problem listed in your "General Idea" answer above. (It's OK to go back and refine that, too!). At the end of that brainstorm, __spend the next 30 minutes__ filling in the sections below, paying mind to the word count and flow of the idea. Feel free to work through these questions for various solutions. The answers to the questions below will shape the project description shared in your README in your repository.*  
+*Spend __20 minutes__ sketching out (on paper or a whiteboard) various ways to address your the problem listed in your "General Idea" answer above. (It's OK to go back and refine that, too!). At the end of that brainstorm, __spend the next 30 minutes__ filling in the sections below, paying mind to the word count and flow of the idea. Feel free to work through these questions for various solutions. The answers to the questions below will shape the project description shared in your README in your repository.*  
 
 - Idea summary (25 words):
 - Who is the audience? (25 words):
@@ -52,9 +49,6 @@ What change do you want to see as a result of this project? Give us a sense of t
 
 ###What does progress look like? (50 words):
 
-***Free-write for 6 minutes; then refine your answer for 5 minutes.***
-
-
 - What does success look like for this project? 
 - Who will this affect?
 - How are you measuring success? 

explore/elevator_pitch.md

@@ -10,9 +10,9 @@ Key points of the elevator pitch are to be:
 
 **GOAL:** We want you to be able to build community and buzz around your projects.  With busy schedules and other work projects competing for attention, it can be difficult to get someone to sit down and have a conversation.  Having a succinct, memorable way to explain what you’re doing and WHY you’re doing it can get people to stop, listen, and even share your passion.  At the end of this exercise you should have a 30 second to one minute “elevator pitch” to get people excited about what you’re doing.
 
-**FORMAT:** Solo writing combined with oral practice.  **You will give your polished pitch to the Mozilla Science Lab team on the January 6th, 2016 Fellows call.**
+**FORMAT:** Solo writing combined with oral practice.  **You will give your polished pitch to the Mozilla Science Lab team on the upcoming 2016 Fellows Call.**
 
-**TIME TO COMPLETE:** 50 mins - 1 hr 15 mins
+**TIME TO COMPLETE:** 50 mins
 
 **TECHNOLOGY:** A timer or stopwatch to time your pitch. Pen and paper or your favorite text editor.  Skype or Google Hangouts for pitching to friends, family, Fellows.  Video is recommended over just audio so body language and eye contact can be practiced along with the text of the pitch.
 
@@ -60,11 +60,11 @@ Refine your pitch again based on your Fellow partner feedback.
 
 How do you feel about your pitch?  Has this process helped you clarify your goals for the project?  Do you feel like you could start up a conversation about your project at your next cocktail party?
 
-Now you’re ready to pitch it to the Mozilla Science Lab team at the **January 6** call!
+Now you’re ready to pitch it to the Mozilla Science Lab team at the next Community Call!
 
 **PITCH PARTNERS:**  
-Joey & Jason pitch to each other.  
-Christie & Richard pitch to each other.
+Kirstie & Bruno pitch to each other.  
+Danielle & Teon pitch to each other.
 
 **HELPFUL RESOURCES ON ELEVATOR PITCHES:**  
 [The Problem with Your Elevator Pitch and How to Fix It](http://www.fastcompany.com/3004484/problem-your-elevator-pitch-and-how-fix-it)  

explore/fellow_interviews.md

@@ -1,18 +1,18 @@
-##Intro blog post for fellows (interview format).
+##Interview your fellow fellow.
 
 **GOAL:** We want our community to know about you, where you are coming from, what inspires and motivates your work in open science, and what projects or potential projects you’re excited about. As part of encouraging conversation and engagement within the Fellows cohort, we’re asking you to collaborate on these posts and interview each other.  
 
 **FORMAT:** Interview. Each fellow interviews another for ~30 minutes; you’re interviewed by a different person than the one you interview.
 
-**TIME TO COMPLETE:** 2 hours (30 mins prep, 30 mins scheduling/tech download and testing, 30 mins interviewing, 30 mins editing & admin etc)  
+**TIME TO COMPLETE:** 1 hour (20 mins prep, 30 mins interviewing, 10 mins editing & admin etc)  
 
-**TECHNOLOGY:** Recording audio  via Skype may be the best option; there are a number of apps/plugins for recording audio from Skype. No-cost options for Mac are limited, but free short-term trials of software is available. If you have another solution, please let us know. 
+**TECHNOLOGY:** Recording audio via Skype may be the best option; there are a number of apps/plugins for recording audio from Skype. No-cost options for Mac are limited, but free short-term trials of software is available. If you have another solution, please let us know. 
 
 ###PROCESS:
 * Get your interview assignment from MSL (see section at the end of this document)
 * Schedule interviews in the next week.
 * Send MSL the recorded audio file; we will have the interviews transcribed and sent to you for editing
-* Zannah is available assist with the editing the text for the blog post as needed. 
+* Aurelia is available assist with the editing the text for the blog post as needed. 
 * Let us know if you have any questions!
 
 ###For INTERVIEWER:
@@ -21,16 +21,15 @@
 * Ask open ended questions “Tell me about x…” “How would you define x…?” “What is your vision for x?” “Why is x important to you?”;  avoid yes or no questions. 
 * Feel free to follow up with “Why?” and “How” questions to clarify or go deeper on a topic.
 * Let the interview be a conversation, keep it relaxed and personable. 
-* Don’t fear tangents if they come up-- it’s OK to drift a bit if your interviewee seems to want to head in a direction that you didn’t have in mind
 * Use the 80/20 rule: you should be listening 80% of the time, talking only 20%
-* Have a pad and pen handy to jot down great question or insight comes to mind while your interviewee is speaking. 
 * Have fun!
 
 ###For INTERVIEWEE:
 * Get specific-- particular projects, concrete examples, real-world first person stories will help anchor your ideas and provide helpful detail. 
 
 ###INTERVIEW ASSIGNMENTS:
-* Joey interviews Richard (presentation: http://blahah.net/fellows-onboarding-talk/#1 )
-* Richard interviews Jason (presentation: http://www.jasonbobe.net/files/Bobe_Mozilla_2015_1014.pdf )
-* Jason interviews Christie (presentation: http://dx.doi.org/10.6084/m9.figshare.1608319 )
-* Christie interviews Joey (presentation: http://joeyklee.github.io/presentations/onboarding/#/ )
+
+* Kirstie interviews Bruno 
+* Bruno interviews Teon 
+* Teon interviews Danielle 
+* Danielle interviews Kirstie 

explore/presentation.md

@@ -1,16 +1,16 @@
-## Presentation:
+##Presentation.
 
 **GOAL:** Distill your project idea into a short presentation to deliver to your peers for feedback and review. 
 
 **FORMAT:** Slide presentation (with notes). 
 
 **TECHNOLOGY:** Your favorite presentation software. 
 
-**TIME TO COMPLETE:** 1.5 hours.
+**TIME TO COMPLETE:** 1 hour.
 
 ### PROCESS: 
 
-Building off your answers to the [project description exercise](https://github.com/mozillascience/fellows-class-2015/blob/master/explore/2-project_description_exercise.md) and your [elevator pitch](https://github.com/mozillascience/fellows-class-2015/blob/master/explore/3-elevator_pitch_exercise.md), this exercise will marry the two into a final presentation to deliver to the group. This will feature your main project idea for the fellowship, explain the problem space, and talk about how your work will address that problem. Try to compose something with images rather than only text, and give yourself some presenter's notes to complement what might turn into a nice TED talk at some point.
+Building off your answers to the [project description exercise](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/2-project_description_exercise.md) and your [elevator pitch](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/3-elevator_pitch_exercise.md), this exercise will marry the two into a final presentation to deliver to the group. This will feature your main project idea for the fellowship, explain the problem space, and talk about how your work will address that problem. Try to compose something with images rather than only text, and give yourself some presenter's notes to complement what might turn into a nice TED talk at some point.
 
 The aim of this exercise is to work on packaging up your project idea and communicate your idea to a diverse audience, so that they can understand your proposal and provide useful feedback.
 

explore/roadmapping.md

@@ -14,6 +14,8 @@ Creating a roadmap helps others understand the current status of your project an
 
 This can be as simple as a collection of issues in your issue tracker, or a detailed timeline complete with milestones. It's up to you to choose what works best for your community!
 
+You can use the `roadmap.md` template in this repo to start, and add in specific work and tasks that are particular to your projects and work.
+
 ####What should be in a roadmap?
 
 **Mission**
@@ -43,3 +45,5 @@ If your project is hosted on GitHub, placing your roadmap in an issue is:
 * easy to update,
 * allows you to easily link each task to the corresponding issue and
 * enables discussion.
+
+For the purpose of this exercise, putting it in your folder should work, try to title it `roadmap.md` or something intuitive so we know where to check.

reference/fellows.md

@@ -30,7 +30,7 @@ A cell biologist and Neuroscience PhD candidate at [Oregon Health and Science Un
 
 **bio**
 
-Teon Brooks is a soon-to-be postdoctoral researcher at the Center for Reproducible Neuroscience and the Department of Psychology at Stanford University. He studies the cognitive processes and temporal dynamics of the brain during reading. He is a core developer for MNE, a community-driven project for analyzing time-series brain data in Python; and OpenEXP, an open science platform founded to be a "GitHub for Experiments" and a tool for running both behavioral and physiological experiments using open-source web-based tools.
+Teon Brooks is a postdoctoral researcher at the Center for Reproducible Neuroscience and the Department of Psychology at Stanford University. He studies the cognitive processes and temporal dynamics of the brain during reading. He is a core developer for MNE, a community-driven project for analyzing time-series brain data in Python; and OpenEXP, an open science platform founded to be a "GitHub for Experiments" and a tool for running both behavioral and physiological experiments using open-source web-based tools.
 He is also developing curriculum, DIYCogSci, for teaching experimental research methods and coding using low-cost electronics and open-source hardware.
 
 * **twitter:** [@teon_io](https://github.com/teon_io)

roadmap.md

@@ -50,8 +50,10 @@ You’ll be doing project research and development planning exercises and contri
 **Exercises** :
 
 * [Goal-setting](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/goal-setting.md)
-* [Blog response on intro to msl](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/blog-intro.md)
-* [Fellow-Fellow Interviews](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/fellow_interviews.md)
+* [Blog response on intro to MSL](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/blog-intro.md)
+* Start [résumé](https://github.com/mozillascience/fellows-class-2016/blob/master/prototype/resume.md)
+* Work on Zines
+
 
 
 	> **Events** : Onboarding
@@ -63,6 +65,7 @@ You’ll be doing project research and development planning exercises and contri
 **Exercises** :
 
 * [Elevator pitch](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/elevator_pitch.md) (polished! jargon free, to be 	presented on Oct 13 call)
+* [Fellow-Fellow Interviews](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/fellow_interviews.md)
 * [Describing (and testing) your idea](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/description.md)
 * [Blog response on Interviews](https://github.com/mozillascience/fellows-class-2016/blob/master/explore/blog-interviews.md)
 
@@ -94,7 +97,6 @@ You’ll be working on testing and building out your proposed project(s) through
 
 **Exercises** :
 
-* Start [résumé](https://github.com/mozillascience/fellows-class-2016/blob/master/prototype/resume.md)
 * [Project schedule](https://github.com/mozillascience/fellows-class-2016/blob/master/prototype/project_schedule.md)
 * [Blog response on scheduling/time management](https://github.com/mozillascience/fellows-class-2016/blob/master/prototype/blog-time_mgmt.md)