Group Member Names:
- When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?
Everyone is generally available to work at any time. Drew would prefer to leave earlier when possible. Ali needs to run home and let dog out occasionally after school.
- How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
Group communication will generally be over Slack, but will share cell numbers as well.
- Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
Ali wants to deal with ActiveRecord queries Drew doesn't want to do styling. Will deal with user roles. Everyone wants RSpec
- What does each group member hope to get out of the project?
Fuller understanding of Rails and CRUD. Ali: better understanding of Capybara Drew: better RSpec testing Jon: User roles
- What is the agreed upon Git workflow? What project management tool will be used? What is the agreed upon procedure for conducting code reviews before merging into master: who will review pull requests, and when?
Make pull request right away with WIP tag. Branching and Sub-branching Git merge master into branch before removing WIP tag.
- What is expected of group members when they run into problems implementing a feature?
Spend no more than 20-30 minutes and then reach out to other group members.
- How does each group member want feedback (both positive and constructive) to be delivered?
Direct, face-to-face if possible. At the Vault.
- Is there anything else the group should know about personal work/communication styles?
Ali: cries himself to sleep at night, don't interrupt. Drew: needs flip flops Jon: liss-is-more