Differences

This shows you the differences between two versions of the page.

--- leadership:roadmaps:2016_spring_semester [2015/12/11 23:47]
kluong [Unsorted Comments]
+++ leadership:roadmaps:2016_spring_semester [2021/09/19 21:59] (current)
@@ Line 11: / Line 11: @@
 ===== Things to Do =====
   - Roadmap discussion
-    - Goals for next semester
+    - <del>Goals for next semester</del>
-  - List of equipment to buy
+  - List of equipment to buy by end of winter break
-  - Management discussion
+  - <del>Management discussion</del>
     - Figure out groups
     - List of mentors and their specialties
-    - <del>Find our next generation leadership group!</del>
+    - Find our next generation leadership group!
       - *IMPORTANT*
       - Need to start training them and give them guidance/help
@@ Line 23: / Line 23: @@
     - Documentation of project work for each group
     - Maintain and add to wiki
-  - Move from Dropbox to Google Drive
+  - <del>Move from Dropbox to Google Drive</del>
     - Both the SCEL general folder and leadership folder
   - Get new students on board
-    - Send out surveys
+    - <del>Send out surveys</del>
-    - Ask for bios
+    - <del>Ask for bios</del>
-    - Give access to Discourse, Wiki, Slack
+    - Give access to Wiki and Slack
-    - Give access to SCEL Google Calendar
+    - <del>Give access to SCEL Google Calendar</del>
-    - Give access to Google Drive folder
+    - <del>Give access to Google Drive folder</del>
-  - Plan orientation meeting
+    - //Figure out room schedule//
-  - Determine All Hands Meeting dates and schedule of events for the semester
+  - <del>Plan orientation meeting (by the end of the break)</del>
+  - <del>Plan mentorship training meeting (by the end of the break)</del>
+  - Figure out final presentation format
+  - <del>Determine All Hands Meeting dates and schedule of events for the semester</del>
   - Figure out a good way to handle finances
-  - Make list of people in lab
+  - <del>Make list of people in lab</del>
-  - Figure out how to open the leadership planning a little more.
+  - Figure out how to open the leadership planning a little more
   - Plan new layout for the lab
+  - Finish updating and deploying new website
+  - Plan and create Github/Git tutorial
 ===== Teams =====
@@ Line 51: / Line 59: @@
 | XBee                | Ernesto                   |
 | Wind Sensor         | Keoni                     |
-|                     |                           |
-|                     |                           |
-|                     |                           |
+=====Plan for 196/296 Students=====
+[[leadership:roadmaps:2016_spring_semester:Weatherbox Challenge:start]]\\
+[[leadership:roadmaps:2016_spring_semester:196 Curriculum:start]]\\
 ===== Unsorted Comments =====
+These comments are unsorted, and may not be fully applicable or used moving forward. This reflects some of the leadership team's thoughts at the beginning of the semester.
   * Need to figure out a better way to plan budgets. We're growing a lot more and we need to be more organized about how we spend our money and how much we have left.
@@ Line 67: / Line 85: @@
   * **Not sure how to tackle 296 students during the off semesters**. What happens to 296 students when they're done with their semester project? Do they stay or do they go?
   * **Figure out how to open up the leadership planning** - we should figure out how to open up the leadership things a little more. Our planning documents maybe should be public somewhere (for specific things) and the minutes can be continue to be closed up. This will help with our PR and documenting everything. Maybe we can figure out something where we can release our old planning documents.
-  * **Seriously consider how to make the workspace environment better** - we will be at a very serious advantage if we structure our lab correctly and it's nice to work in. Having a room where it sounds and feels nice to be in will come a far way towards making it easier for people to integrate into the lab. A deticated, nice meeting space will also help with this. We want to make people come in and say "wow", this is kinda cool. We can use this stuff: https://acousticalsolutions.com/
+  * **Seriously consider how to make the workspace environment better** - we will be at a very serious advantage if we structure our lab correctly and it's nice to work in. Having a room where it sounds and feels nice to be in will come a far way towards making it easier for people to integrate into the lab. A dedicated, nice meeting space will also help with this. We want to make people come in and say "wow", this is kinda cool. We can use this stuff: https://acousticalsolutions.com/
   * **We should come up with a manifesto** - write a manifesto or some sort of similar document that helps us document why the lab exists and what it exists for. See this for more details: http://www.gnu.org/gnu/manifesto.en.html
   * **Consider the case if 396 students want to do a micromouse** - if students want to do a micromouse for 396, I feel like we should let them do it. If they've done a 296 with us and agreed to stay on the project alongside micromouse it would be a great opportunity for them to switch to micromouse for a semester. It would be a good test of what they learned in our lab. My opinion is that they'll come back to our lab with a great new perspective.
@@ Line 83: / Line 101: @@
-=====Plan for 196/296 Students=====
-==== Possible Weatherbox "Challenge" ====
-We currently have a lot of students who came from micromouse - they learned a lot of teamwork/circuit design skills in their 296/396 projects that are really useful to our lab. If students do a 296 with us, we'd like them to get the same experience and opportunity to learn these skills.
-These are just the initial thoughts I had about the project. Open to suggestions for names.
-**Vision/Mission Statement**: the weatherbox challenge will provide students with an experience in using EE/CompE concepts to build technologies that can be used in sustainability efforts. Students will learn the necessary skills to be able to contribute to renewable energy efforts and build the next generation of sustainable technologies.
-Categories:
-  * Power efficiency
-  * Cost
-  * Ecological Impact (materials used, etc)
-  * Ease of assembly
-  * (... more categories if necessary)
-Skills:
-  * Software
-  * PCB Design
-  * System Design
-  * (... add more to this)
-What people need to know at the beginning (tutorials?):
-  * How to implement I2C
-  * How to implement SPI
-  * How to read analog from a pin
-  * How to use interrupts
-  * Use an AVR with just a breadboard
-  * (... need to add more to this)
-====Possible Tutorials Students Should Go Through====
-  * Could incorporate some of these as tutorial as sessions where we teach them for the weatherbox challenge project
-  * 296 tutorials students could go through
-    * Read through the wiki, learn how to use it, and find projects you are interested in
-    * Arduino
-      * Choose an instructables project and make it- be able to explain code and the schematic for assmembling up the parts, maybe mini presentation
-    * Eagle
-    * Google sketch up
-    * Codecademy
-      * Python, ruby on rails, html, javascript
-    * Github
-    * Intro to weatherbox project:
-      * Read papers on weatherbox
-      * Read/understand code, parts in the weatherbox, assembling the hardware, housing
-      * Assemble and program an apple weatherbox
-    * Intro to wind sensor project:
-      * Read papers on wind sensor
-      * Learn about set up of wind sensor and how it works
-      * Learn about testing and how to test the wind sensor, assemble the wind sensor
-    * Intro to forecasting:
-      * Go through notes on the wiki for the forecasting sessions
-      * Attend forecasting sessions