Group Member Names: Beth, Penny
1. 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?
Schedule here: https://docs.google.com/spreadsheets/d/1QjxyP7p08GaC4Ncxw_rbkp8lwWO6ticnu_-L6dQEp90/edit#gid=0
Penney: Mornings are better
Beth: Mornings are better, crash ~4.
2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack, phone Set up day in morning, check in and out around major work sessions.
3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Penney: Want to touch everything: js, html, tests Beth: same
4. What does each group member hope to get out of the project? Penney: Better understanding of javascript Beth: Javascript, being efficient with my time
5. What is the agreed upon Git workflow? Who will review pull requests, and when? What project management tool will be used? Use Waffle, avoid pushing to master at all costs. Commit more frequently. If we're working independently, other person should merge. Individual who merges should pull down branch, merge with master locally, run test suite...only after all tests pass should they merge remotely. Practice communicating with PRs.
6. What is expected of group members when they run into problems implementing a feature? If no progress in 15-20 min, ask for help.
7. How does each group member want feedback (both positive and constructive) to be delivered?
Penney: However.
Beth: Include suggestions and help me understand what you do want if what I'm doing isn't helpful.
8. Is there anything else the group should know about personal work/communication styles? Work on asking for help at the right times, knowing what questions to ask when stuck on logic.