Proposal

README.md

@@ -2,52 +2,76 @@ Project Outline
 ============
 
 ## Overview of Points
-* Project Proposal = 10 pts  
-* Vote = 5 pts
-* Project Outline = 15 pts
-* Meeting w/ Mike = 10 pts
-* Milestone 1 = 25 pts
-* Milestone 2 = 25 pts
-* Halfway Check-in = 10 pts
-* Milestone 3 = 25 pts
-* Milestone 4 = 25 pts
-* Final Outcome = 50 pts  
+- [x] Project Proposal = 10 pts  
+- [x] Vote = 5 pts
+- [x] Project Outline = 15 pts
+- [x] Meeting w/ Mike = 10 pts
+- [ ] Milestone 1 = 25 pts
+- [ ] Milestone 2 = 25 pts
+- [ ] Halfway Check-in = 10 pts
+- [ ] Milestone 3 = 25 pts
+- [ ] Milestone 4 = 25 pts
+- [ ] Final Outcome = 50 pts  
 --> 200 Total
 
 ## Team Members
-* Person 
-* Person
-* Person
-* Person
-* Person
+* [Josh Ferge](www.github.com/JoshFerge) - [email protected]
+* [Alexia Newgord](www.github.com/alne4294) - [email protected]
+* [Chris Wittenberg](www.github.com/cwitty1919) - [email protected]
+* [Nikita Voskoboynik](www.github.com/nikitavoskoboynik) - [email protected]
+* [Justin McBride](www.github.com/dare599z) - [email protected]
+* [Daniel Nolan](www.github.com/dano8957) - [email protected]
 
 ## GitHub Repo 
-[As a way to share your project code and handle submissions, please create a GitHub Repo and place the link here so we know where to find your work]
+
+[Reactive_Art_Piece Repository](https://github.com/alne4294/Reactive_Art_Piece)
 
 ## Project Sketch
 [Use this section to sketch out the working parts of your project.  The project may change as you go, but try your best.  Describe how you intend to capture your data, clean it, analyze it, dump it, and vizualize it.  How will you set up your hardware?  What things are still uncertain and what things do you feel confident about?  What will be your process to get each of these things in working order?  How would you like your display to be 'triggered' in the installation?]
 
+![Warhol pic](http://www.online-tech-tips.com/wp-content/uploads/2011/06/John-Lennon-Andy-Warhol_thumb.png)
+
 ## Hardware
 [This is a preliminary list; it will be finalized in a meeting with Mike (see below)]
 
-1. List
-2. of
-3. needed 
-4. Hardware
+1. Mic?
 
 ## Roles
 Given the varying expertise and interests, I'd like you to outline what team member will be responsible for what parts of the project.  It's okay if 2 people want to share certain responsibilities.  This is mostly for your own organization and, if things get rocky, so Mike knows who to talk to in the group.
 
+###### 1. Data spec/storage (what it looks like when it comes in), e.g. Mongo?
+Nikita, Chris
+###### 2. Server
+Josh, Justin
+###### 3. Sound collection
+Chris
+###### 4. Managing visualizations as they come together
+Alexia, Daniel
+###### 5. Parse portrait image into 3+ classes/changeable parts (CSS classes), start with Steve Wozniak?  Add command line info to top of image?
+Alexia, Chris, Daniel
+###### 6. Creating scales for colors
+Josh
+###### 7. Hardware, mics etc.
+Justin
+###### 8. Light collection
+Nikita
+
+
 ## 4 Milestones
 [Please list 4 Project Milestones you'll complete week-to-week to show your progress.  You will need to turn in some tangible example to prove you've completed 1 milestone each week.  Some combination of code snippets, data, screenshots, picture of the hardware setup, etc.  If these milestones need to change slightly, that's OK, as long as you tell Mike and Tom at least 2 days before submission (and as long as you haven't arbitrarily reduced the workload)]
 
-1. 
-2. 
-3. 
-4. 
+1. Milestone 1: how will image(s) come together/collaboration?, prototype/wireframe of design ** Code snippet/screenshot ** Use artificial data
+2. Milestone 2: data snippet with response/change ** DUE: Monday after Thanksgiving ** Live data: we need a web server that pulls live data down ** Someone needs to get snippets of data and share ** Demonstrate API call, pull data, and inject into the visualization
+3. Milestone 3: prototype => going to lobby ** By first week of December
+4. Milestone 4: pure awesomeness, perfecting
 
 ## Propose 3 Meeting Times
 [You'll need to meet with Mike sometime during the week of 11/10 to finalize these details.  For this your whole team should try to be available for a **30 minute** meeting.  Mike is unavailable from 12-1 MWF and 12-2 TTh so don't propose those times.]
 
+- Tues. November 11th 5:00 - 5:30 PM
+- Tues. November 11th 4:30 - 5:00 PM
+- Tues. November 11th 5:30 - 6:00 PM
+
+***Finalized meeting time: Thursday, November 13th at 5:30pm.***
 
 AND FINALLY... Remember to have fun!  This is going to be a challenging project, and there is going to be some tough hurdles, but it should be a good time if you get into it and get excited about what we're creating.  Mike will do his best to be available and around ATLAS so that in the evenings if students need to come in and work or try things, we can set times to do this.  Also we'll have a hardware expert [Abhishek Narula] from ATLAS who will help us in the process.