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?
Pat - Doing meet and greet this weekend and moving to Denver next weekend. Good at remote work. Pat will be here from 9-4. Pending weekend hours. Will check in again on Friday re weekend. More inclined to work in the morning.
Yoseph - Wants to attend to meetups. Usually occur at 5-6. Will give us 24 hour notice. Arrives at 7, no time restriction to leave.
Jason - Here from 8 till we are done working for the day. May need to go home to let dog out. Will need to leave at around 6 today, but open otherwise.
David - Available to work anytime. Would like to attend improv if that's happening. Usually arrive at 9 but can arrive earlier if needed.
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
Slack channel, daily check-ins at the beginning of our work time for the day
Pat - Realizes importance of commenting in git
We will ask Josh about using WIP to comment on code
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
Jason - open to working on anything. Could use extra time with front-end design
Pat - Wants to explore some ideas, particularily with JS on front-end or API. Feels comfortable with backend and testing and can help with everything
Yoseph - Also wants to explore JS. Wants to touch on back-end and POROs. Exploration - drones and JS
David - Wants to take a couple pages to design to brush up on front-end, but gravitates towards backend
Jason - Fours... or threes... or just pass
David - Be a generalist and have good sense of what's going on
Pat - Wants to be technically challenged every step of the way. Getting better at using a staging environment and using git
Yoseph - Also wants to challenged
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?
We'll use waffle. We will create feature branches and push to a development branch and then push to master when it's ready for production. Don't merge your own pull request. Have someone who didn't submit pull request review code and add comments.
Problems should be timeboxed before reaching out for help. Ask for help.
Just say it
Jason - Would like to break things down and pair on them
David - Pair whenever possible
Only have all four of us coding together when needed
Pat - prefers to work in the morning, on board with pairings
Yoseph - Also on board with pairing through the project