lundgrea · August 19, 2019 23:46 · Aug 19, 2019 · Aug 19, 2019 · Aug 19, 2019 · Aug 19, 2019
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -60,4 +60,4 @@ Day 1 Agenda:
 - [x] Setup repository 
 - [x] mkdir file structure (app, planets, people, vehicles, scrolling)
 - [x] Ideate components and methods
-- [ ] Submit to Travis/Robbie
+- [x] Submit to Travis/Robbie
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -59,5 +59,5 @@ Day 1 Agenda:
 - [x] GitHub projects
 - [x] Setup repository 
 - [x] mkdir file structure (app, planets, people, vehicles, scrolling)
-- [ ] Ideate components and methods
+- [x] Ideate components and methods
 - [ ] Submit to Travis/Robbie
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -59,5 +59,5 @@ Day 1 Agenda:
 - [x] GitHub projects
 - [x] Setup repository 
 - [x] mkdir file structure (app, planets, people, vehicles, scrolling)
+- [ ] Ideate components and methods
 - [ ] Submit to Travis/Robbie
-- [ ] other?
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -56,7 +56,7 @@
 Day 1 Agenda:
 - [x] DTR
 - [x] Wireframe
-- [ ] GitHub projects
+- [x] GitHub projects
 - [x] Setup repository 
 - [x] mkdir file structure (app, planets, people, vehicles, scrolling)
 - [ ] Submit to Travis/Robbie

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -59,4 +59,5 @@ Day 1 Agenda:
 - [ ] GitHub projects
 - [x] Setup repository 
 - [x] mkdir file structure (app, planets, people, vehicles, scrolling)
+- [ ] Submit to Travis/Robbie
 - [ ] other?
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -58,5 +58,5 @@ Day 1 Agenda:
 - [x] Wireframe
 - [ ] GitHub projects
 - [x] Setup repository 
-- [ ] mkdir file structure (app, planets, people, vehicles, scrolling)
+- [x] mkdir file structure (app, planets, people, vehicles, scrolling)
 - [ ] other?
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -57,6 +57,6 @@ Day 1 Agenda:
 - [x] DTR
 - [x] Wireframe
 - [ ] GitHub projects
-- [ ] Setup repository 
+- [x] Setup repository 
 - [ ] mkdir file structure (app, planets, people, vehicles, scrolling)
 - [ ] other?
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -1,44 +1,42 @@
 # DTR: Define the Relationship
 
-## Project: 
-SWAPIbox
-#### Group Members: 
-Gregory Anderson and Alyssa Lundgren
+## Project: SWAPIbox
+### Group Members: Gregory Anderson and Alyssa Lundgren
 
-### Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
+#### Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
  - Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
 
-### Team strengths & collaboration styles (consider discussing your Pairin qualities here):
+#### Team strengths & collaboration styles (consider discussing your Pairin qualities here):
  - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests.
  - Committed and positive and encouraging
 
-### How we can use our strengths to overcome obstacles:
+#### How we can use our strengths to overcome obstacles:
  - Talk it out.
  - Async testing not taught until next week - so we will do this next week
  - Good strong communication
  - Establishing schedule/timelines/checkpoints/goals
  - Breaking things down into managable chunks and figure out challenges early
  - Don't struggle for too long
 
-### Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
+#### Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
  - Friday night expectations (made Wednesday night), assign weekend homework, leave async testing for the end (next week).
  - After school/during work time is best
  - Early morning check-in before school
  - Setup meeting rooms
  - Close to final product by the end of Monday (ideally only some async testing and README to go by the end of the day Monday)
  - Friday 11pm - Sunday 5pm Greg out of state for a wedding - team to split up work prior to the start of the weekend for individual coding 
 
-### Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
+#### Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
  - Face to face, slack, maybe some slack video this weekend
 
-### Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
+#### Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
  - Both of us getting as much out of: async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
 
-### Workload Expectations (What features do we each want to work on?):
+#### Workload Expectations (What features do we each want to work on?):
  - Begin meetings with review, attempt to split work up and work individually for 1/2 hour or so
  - Evenly split the work 
 
-### Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
+#### Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
  - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests. 
  - Atomic commits
  - Utilize issues for functionality not 
@@ -48,11 +46,11 @@ Gregory Anderson and Alyssa Lundgren
  - Daily checkins (except Saturday)
  - GitHub projects
 
-### Expectations for giving and receiving feedback:
+#### Expectations for giving and receiving feedback:
  - Early and often
  - Kind and specific
 
-### Project management tools we will use (GitHub projects or Trello are popular tools):
+#### Project management tools we will use (GitHub projects or Trello are popular tools):
  - GitHub projects
 
 Day 1 Agenda:

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -1,7 +1,9 @@
 # DTR: Define the Relationship
 
-## Project: SWAPIbox
-#### Group Member Names: Gregory Anderson and Alyssa Lundgren
+## Project: 
+SWAPIbox
+#### Group Members: 
+Gregory Anderson and Alyssa Lundgren
 
 ### Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
  - Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -57,6 +57,6 @@ Day 1 Agenda:
 - [x] DTR
 - [x] Wireframe
 - [ ] GitHub projects
-- [x] Setup repository 
+- [ ] Setup repository 
 - [ ] mkdir file structure (app, planets, people, vehicles, scrolling)
 - [ ] other?
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -57,6 +57,6 @@ Day 1 Agenda:
 - [x] DTR
 - [x] Wireframe
 - [ ] GitHub projects
-- [ ] Setup repository 
+- [x] Setup repository 
 - [ ] mkdir file structure (app, planets, people, vehicles, scrolling)
 - [ ] other?
diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -55,7 +55,7 @@
 
 Day 1 Agenda:
 - [x] DTR
-- [ ] Wireframe
+- [x] Wireframe
 - [ ] GitHub projects
 - [ ] Setup repository 
 - [ ] mkdir file structure (app, planets, people, vehicles, scrolling)

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -1,7 +1,7 @@
 # DTR: Define the Relationship
 
 ## Project: SWAPIbox
-## Group Member Names:
+#### Group Member Names: Gregory Anderson and Alyssa Lundgren
 
 ### Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
  - Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -3,40 +3,40 @@
 ## Project: SWAPIbox
 ## Group Member Names:
 
-1. Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
+### Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
  - Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
 
-1. Team strengths & collaboration styles (consider discussing your Pairin qualities here):
+### Team strengths & collaboration styles (consider discussing your Pairin qualities here):
  - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests.
  - Committed and positive and encouraging
 
-1. How we can use our strengths to overcome obstacles:
+### How we can use our strengths to overcome obstacles:
  - Talk it out.
  - Async testing not taught until next week - so we will do this next week
  - Good strong communication
  - Establishing schedule/timelines/checkpoints/goals
  - Breaking things down into managable chunks and figure out challenges early
  - Don't struggle for too long
 
-1. Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
+### Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
  - Friday night expectations (made Wednesday night), assign weekend homework, leave async testing for the end (next week).
  - After school/during work time is best
  - Early morning check-in before school
  - Setup meeting rooms
  - Close to final product by the end of Monday (ideally only some async testing and README to go by the end of the day Monday)
  - Friday 11pm - Sunday 5pm Greg out of state for a wedding - team to split up work prior to the start of the weekend for individual coding 
 
-1. Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
+### Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
  - Face to face, slack, maybe some slack video this weekend
 
-1. Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
+### Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
  - Both of us getting as much out of: async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
 
-1. Workload Expectations (What features do we each want to work on?):
+### Workload Expectations (What features do we each want to work on?):
  - Begin meetings with review, attempt to split work up and work individually for 1/2 hour or so
  - Evenly split the work 
 
-1. Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
+### Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
  - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests. 
  - Atomic commits
  - Utilize issues for functionality not 
@@ -46,11 +46,11 @@
  - Daily checkins (except Saturday)
  - GitHub projects
 
-1. Expectations for giving and receiving feedback:
+### Expectations for giving and receiving feedback:
  - Early and often
  - Kind and specific
 
-1. Project management tools we will use (GitHub projects or Trello are popular tools):
+### Project management tools we will use (GitHub projects or Trello are popular tools):
  - GitHub projects
 
 Day 1 Agenda:

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -1,42 +1,42 @@
-DTR: Define the Relationship
+# DTR: Define the Relationship
 
-Project: SWAPIbox
-Group Member Names:
+## Project: SWAPIbox
+## Group Member Names:
 
-Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
+1. Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
  - Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
 
-Team strengths & collaboration styles (consider discussing your Pairin qualities here):
+1. Team strengths & collaboration styles (consider discussing your Pairin qualities here):
  - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests.
  - Committed and positive and encouraging
 
-How we can use our strengths to overcome obstacles:
+1. How we can use our strengths to overcome obstacles:
  - Talk it out.
  - Async testing not taught until next week - so we will do this next week
  - Good strong communication
  - Establishing schedule/timelines/checkpoints/goals
  - Breaking things down into managable chunks and figure out challenges early
  - Don't struggle for too long
 
-Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
+1. Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
  - Friday night expectations (made Wednesday night), assign weekend homework, leave async testing for the end (next week).
  - After school/during work time is best
  - Early morning check-in before school
  - Setup meeting rooms
  - Close to final product by the end of Monday (ideally only some async testing and README to go by the end of the day Monday)
  - Friday 11pm - Sunday 5pm Greg out of state for a wedding - team to split up work prior to the start of the weekend for individual coding 
 
-Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
+1. Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
  - Face to face, slack, maybe some slack video this weekend
 
-Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
+1. Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
  - Both of us getting as much out of: async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
 
-Workload Expectations (What features do we each want to work on?):
+1. Workload Expectations (What features do we each want to work on?):
  - Begin meetings with review, attempt to split work up and work individually for 1/2 hour or so
  - Evenly split the work 
 
-Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
+1. Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
  - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests. 
  - Atomic commits
  - Utilize issues for functionality not 
@@ -46,11 +46,11 @@ Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/De
  - Daily checkins (except Saturday)
  - GitHub projects
 
-Expectations for giving and receiving feedback:
+1. Expectations for giving and receiving feedback:
  - Early and often
  - Kind and specific
 
-Project management tools we will use (GitHub projects or Trello are popular tools):
+1. Project management tools we will use (GitHub projects or Trello are popular tools):
  - GitHub projects
 
 Day 1 Agenda:

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -54,7 +54,7 @@ Project management tools we will use (GitHub projects or Trello are popular tool
  - GitHub projects
 
 Day 1 Agenda:
-- [ ] DTR
+- [x] DTR
 - [ ] Wireframe
 - [ ] GitHub projects
 - [ ] Setup repository 

diff --git a/SWAPIbox DTR.md b/SWAPIbox DTR.md
@@ -0,0 +1,62 @@
+DTR: Define the Relationship
+
+Project: SWAPIbox
+Group Member Names:
+
+Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
+ - Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
+
+Team strengths & collaboration styles (consider discussing your Pairin qualities here):
+ - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests.
+ - Committed and positive and encouraging
+
+How we can use our strengths to overcome obstacles:
+ - Talk it out.
+ - Async testing not taught until next week - so we will do this next week
+ - Good strong communication
+ - Establishing schedule/timelines/checkpoints/goals
+ - Breaking things down into managable chunks and figure out challenges early
+ - Don't struggle for too long
+
+Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
+ - Friday night expectations (made Wednesday night), assign weekend homework, leave async testing for the end (next week).
+ - After school/during work time is best
+ - Early morning check-in before school
+ - Setup meeting rooms
+ - Close to final product by the end of Monday (ideally only some async testing and README to go by the end of the day Monday)
+ - Friday 11pm - Sunday 5pm Greg out of state for a wedding - team to split up work prior to the start of the weekend for individual coding 
+
+Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
+ - Face to face, slack, maybe some slack video this weekend
+
+Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
+ - Both of us getting as much out of: async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises. 
+
+Workload Expectations (What features do we each want to work on?):
+ - Begin meetings with review, attempt to split work up and work individually for 1/2 hour or so
+ - Evenly split the work 
+
+Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
+ - Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests. 
+ - Atomic commits
+ - Utilize issues for functionality not 
+ - Always work on a branch
+ - Never merge our own pull requests
+ - Deal with merge conflicts locally before pushing
+ - Daily checkins (except Saturday)
+ - GitHub projects
+
+Expectations for giving and receiving feedback:
+ - Early and often
+ - Kind and specific
+
+Project management tools we will use (GitHub projects or Trello are popular tools):
+ - GitHub projects
+
+Day 1 Agenda:
+- [ ] DTR
+- [ ] Wireframe
+- [ ] GitHub projects
+- [ ] Setup repository 
+- [ ] mkdir file structure (app, planets, people, vehicles, scrolling)
+- [ ] other?
No results found