# rails engine DTR

#### Group Member Names:
andy dymond, cameron johnson

#### Project Expectations: What does each group member hope to get out of this project?
we would both like to shoot for early completion so that we have time to work on writing docs as an extension.
learn how to test controllers

#### Goals and expectations:
we will use a rebase workflow and implement waffle.io to keep our issues separate and expectations clear
learn as much as possible about json and writing rake tasks

#### Team strengths:
cameron likes to write testing suites and debugging.
andy has some experience working with APIs and is good at debugging
we both prefer a rebase workflow

#### How to overcome obstacles:
set a time limit of struggling before reaching out, but always giving it our best attempt before reachng out. we will utilize mentors and other resources when necessary. we will also re DTR if an issue comes up we haven't addressed and find a solution that works for the group as a whole.
keep communication open and honest

#### Schedule Expectations (When are we available to work together and individually?):
we plan on not staying at turing past seven pm. we also plan on calling it a night around nine pm if possible. we plan on delegating tasks between us and communicating often with progress reports.

#### Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
we will use slack as a primary line of communication. we will also exchange phone numbers. we plan on commenting and poroviding feedback on each other's PRs on github. we will keep waffle cards very clear and explicit.

#### Abilities Expectations (Technical strengths and areas for desired improvement):
we both want to improve our skills in active record. i want to learn as much about json and APIs as possible. improve SRP in controllers

#### Workload Expectations (What features do we each want to work on?):
stick to our roles as person a and person b. not working on each other's duties, but also helping each other by pairing if one team member finishes their responsibility. cameron is person a and andy is person b.

#### Git Workflow Expectations
we will use a rebase workflow. we will protect our master branch by enforcing member review before a merge is committed. we will also disable a member's ability to merge their own PRs. we will leave comments in our PR describing what changes we made to the project, and we will leave comments on PRs when merging. we will look into utilizing Hound to help keep our code sanitized.

## these are subject to change as the scope of the project increases and we will each contribute to every aspect of the project.

#### Expectations for giving and receiving feedback:
clear, open and honest communication is always the best approach. remember to listen and respond to what a group member is saying rather than reacting on emotion. remember positive reinforcement and to have fun!

#### Agenda to discuss project launch:
- project to be complete by thursday morning the day before due

#### Ideas:
- docs

#### Tools:
hound
waffle.io

#### Additional Notes: