@zachlatta @maxwofford

For the below tasks

https://gist.github.com/jonleung/e79e1de50a0724bf3337

1. Make sure that they're not already tasks in the Kanban
2. If they are not already a task, create the task and make the description human readable such that anyone in the organizaiton would be able to complete it.

Go through feedback/reflect on cohort 1 and create a list of tasks to do this week to build the curriculum for our second cohort.

Will need to work with @maxwofford and @andreadeng synchronously doing.

• read q
• read thorough own notes
• Look through GWC
• funcs
• you have lots if project time
• testing knowledge
• training how?
• idea of tutting everything
• lack of motivation in beginning

Whenever someone applies, automatically send them an email that's like, "Hey, we got your application, we're doing admissions on a rolling basis. We'll get back to you by at least 2 weeks before the cohort starts, let us know if you need to know earlier.

Please feel free to reach out for questions.

If it's helpful, it's easy to write a script in Google Scripts so that when you receive a form, it can make a post request somewhere (but it's probably jsut eaiser to do this in AJAX on a e.onClick event and don't prevent callback.

cheerios
oatmeal
bananas
mandarins

research for more energizers through transformative institute and improv website

We should add something like "Transportation: Students are responsible for their own transportation to and from our San Francisco venue and to special field trips."

@zachlatta Please reword for unknown location.

• Make sure you are prepared to record all the energizers
• Make sure you are prepared to record all the video lectures.

Thoughts on changing that header background image to the following?

Hold off on this for now, waiting on getting a higher res version of the replacement image from @gemmabusoni

These are things to communicate with parents and students.

Make sure they both know this information (i.e. perhaps email them)

• Forms SUNDAY
  • Waiver
  • Health Form
    • Make sure this asks for allergies / food restrictions
  • Media Release Form
• Send Information to Students
  - [x] *Link Pre-Program Questionnaire - ask @andreadeng
  • Times
    • Start time 9:20am, please arrive on time
    • End time 4:30
    • You are encouraged to stay afterwards to Hack
  • Food
    • Breakfast will be provided
    • We're encouraging you to pack lunch because there will be very limited time during class.
• Things to Bring
  • Laptop
  • Charger
  • Writing Implement
  • Notebook
  • Lunch
• Timing
  • Remind people that it starts at 9:20am - 4:20pm
• First Day
  • Meet at Galvanize, 44 Tehama Street
  • Just drop off the kids

The deadlines listed are hopeful:

Monday

• Negotiate with R*** to finalize contract with G********
• Member Agreement Signed
• Memo of Understanding Sent (@zachlatta)
• Members Onboarding

MVP Done June 1st

• Classroom Upgrading (they may continue to renovate after june 1st in the evenings)

1. Figure out what main phaser-like examples should be (note this is not necessarily to create them but they can be found as well). Each example should be very small and only focus on a very specific concept and one and only one concept. Also, there should be many examples to illustrate a wide variety of concepts. For CSS for example:
   a. w3 school examples
   b. css tricks
2. Outline the examples you are planning on making and review your potential examples with team (do this earlier rather than later)
3. Create the examples
4. Publish the examples so that they are in a JS Bin like place (note that examples that focus on javascript should not be in JS bin because the debugger cannot be properly used.

Note: As an example, in phaser, they have an example for merely how to (1) add a sprite, (2) add an image, (3) add multiple sprites, (4) make the sprite do just 1 thing, (5) make the sprite do just this other thing. Link.

People are currently expecting to know about application decisions within the next week or so, no matter what dates they said that they could go to (i.e. even if they signed up for late July).We need to make their expectations so that they know that they may not receive an admissions email until much later in the summer.

I've been talking to people on the phone a lot and they're expecting to know about admissions decisions much earlier (like within the next 2 weeks). Feel free to run copy by me.

• Allocate days for each energizer
• Allocate days for student led energizers
• Ensure that there are enough breaks built in
• For w2d1, start having students try to run he energizers
• Allocate start and end times for
  • standups at 9am for 10 minutes
  • camp itself
  • breakfast
  • lunch
  • breaks (including a longer break)
  • review time after class (30 mins)
    • Potential Format:
      • Review:
        • What could be improved on
        • What went well
        • What may we do for tomorrow

Create a bullet point list of topics covered and deliverables for each day for the course of the three weeks.

Something along the lines of:

• we want to try our best to make hack camp great for anyone who comes
• right now it is not in our ability to provide housing

@maxwofford @zachlatta

Ask students if they can make the day.

Something along the lines of:

If you've coded before, can you briefly (3-5 sentences) talk about a project or anything that you've worked on and how it works? My objective is to get to know their coding ability.

Does your school have AP CS?
Have you taken AP CS at your school?

(Knowing if their school had AP cs lets us say we provided this experience to X number of people who wanted to learn to code but didn't have AP CS)

(Knowing whether they took it lets us quickly where their level is)

A folder where we can put our personal notes and observations from cohort 2.

• 4 beginners, no coding experience
• 2 some experience, not finished a project

We need to talk to these guys ASAP: https://www.insurancefornonprofits.org/ to figure out what kind of insurance we need to get!

http://cl.ly/322v0K23443h
http://cl.ly/2S2v0Q1m1k18
http://cl.ly/413X0q190c1w

• Attendance Sheet - add names
• Pre Program Survey (first time they take "Camp Questionarre")
  • Add the questions to get a sense of where someone is before they enter
    • "List the programming languages have you used before?"
    • "If you have worked with code before, briefly describe one of the most difficult projects that you've worked on and how it was technically implmeented"
  • Mindset / Grit
• Middle Questionaire
• Post Program Survey
  • Mindset / Grit (first time they take "Camp Questionarre")
  • Change the first question to "What would you say to a student who is condering attending hack camp but is on the fence?"
• Read Sooz's email on how we may be able to quantify mindset
• Max review it :)
• Review Sooz's self efficacy

@maxwofford @zachlatta

Create a memo-of-understand with Galvanize and get both parties to sign it to confirm the venue in writing.

Probably @jonleung

• First, outline all of the things that needs to be covered, the requirements!

Outline flow of new technical curriculum such that every day has...

• an objective
• a vehicle
• concepts covered
• what is shipped at the end of each day
  • presentation?
  • github website?

Strategy: focus on breadth, not depth!

w1d1

• shout
• mention coldcalling
• github

w2d1

• A letter to yourself

1. Figure out what main phaser-like examples should be (note this is not necessarily to create them but they can be found as well). Each example should be very small and only focus on a very specific concept and one and only one concept. Also, there should be many examples to illustrate a wide variety of concepts.
2. Outline the examples you are planning on making and review your potential examples with team (do this earlier rather than later)
3. Create the examples
4. Publish the examples so that they are in a JS Bin like place (note that examples that focus on javascript should not be in JS bin because the debugger cannot be properly used.

Note: As an example, in phaser, they have an example for merely how to (1) add a sprite, (2) add an image, (3) add multiple sprites, (4) make the sprite do just 1 thing, (5) make the sprite do just this other thing. Link.

Willing to experiment with this current system first @zachlatta it feels a little bit difficult for people who are not the PM at the moment to contribute with the way things are currently lined up. Perhaps Org mode is analogous to my spreadsheets, it's where you do your own work but we need some public place like the spreadsheet where the PM is done. Definitely ask about this on your calls but I don't feel comfortable right now not being able to easily access and find things in a familiar format.

1. Figure out what main phaser-like examples should be (note this is not necessarily to create them but they can be found as well). Each example should be very small and only focus on a very specific concept and one and only one concept. Also, there should be many examples to illustrate a wide variety of concepts. For HTML for example:
   a. w3 school examples
   b. css tricks
2. Outline the examples you are planning on making and review your potential examples with team (do this earlier rather than later)
3. Create the examples
4. Publish the examples so that they are in a JS Bin like place (note that examples that focus on javascript should not be in JS bin because the debugger cannot be properly used.

Note: As an example, in phaser, they have an example for merely how to (1) add a sprite, (2) add an image, (3) add multiple sprites, (4) make the sprite do just 1 thing, (5) make the sprite do just this other thing. Link.

Create a script that sets up LiveReload with Cloud9.

Right now we're accessing the environment directly to get configuration, like so:

auth.client_id = ENV['CLIENT_ID')

What we should be doing is:

set :gdrive_client_id, ENV['CLIENT_ID']

auth.client_id = settings.gdrive_client_id

Haven't checked the other date ranges yet, but I had a parent reach out to me to clarify July 6th - July 20th and whether the camp ends on Friday the 17th or Monday the 20th. I believe the other date ranges have this issues as well.

All our questions are above the alumni projects area already, with 3 trailing questions in the faq.

1. Figure out what main phaser-like examples should be (note this is not necessarily to create them but they can be found as well). Each example should be very small and only focus on a very specific concept and one and only one concept. Also, there should be many examples to illustrate a wide variety of concepts.
2. Outline the examples you are planning on making and review your potential examples with team (do this earlier rather than later)
3. Create the examples
4. Publish the examples so that they are in a JS Bin like place (note that examples that focus on javascript should not be in JS bin because the debugger cannot be properly used.

Note: As an example, in phaser, they have an example for merely how to (1) add a sprite, (2) add an image, (3) add multiple sprites, (4) make the sprite do just 1 thing, (5) make the sprite do just this other thing. Link.

For brainstorming exercises
-post-its (large pack maybe of 10?)
-markers (2 packs of colored markers 12 pens each)