Group Member Names: Jared, Josh, Sunny
-
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? Anytime. Josh needs to catch the last train but thats pretty late.
-
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Private slack channel
-
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Jared: Does not want to work on style. Sunny: Is ok doing some style. Sunny would like us all to touch the new things we are doing, and focus on splitting basic crud functionality. Sunny also wants to work on Nefarious things. Josh: I am open to whatever
-
What does each group member hope to get out of the project? Sunny: API knowledge, solidifying rails knowledge, styling Jared: Comfort with rails Josh: Passing scores and somewhat polished portfolio piece
-
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? Try to avoid rebasing with proper commits, Never merge your own pull requests. Waffle is our project management tool of choice. Pull requests will be reviewed together as a group during the day, or by another person as organized through slack.
-
What is expected of group members when they run into problems implementing a feature? Ask other group members for assistance ASAP
-
How does each group member want feedback (both positive and constructive) to be delivered? Jared: Passive aggressive sticky notes left on his laptop. Sunny: Whatever your feeling Josh: Prefer in person feedback or through slack if im not here and it cant wait.
-
Is there anything else the group should know about personal work/communication styles? Sunny wants everyone to be open with him.