Setting Group Expectations
- Ash Vaid, Mike Centrelli, Marc Fidelman, JF Lalonde
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?
- Marc: Thursday constraint on location, can work remotely. Possible event tomorrow night Tues. Otherwise no.
- JF: May have a weekend day off to see family.
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
- Slack works for everyone, possibility of phone/texts.
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
- Marc: would like more exposure with Authentication/Authorization
- Being more comfortable with join tables and auth/auth, possibility of Favorites as an extension
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 be using Waffle, name git branches with purpose (feature-name, .1, .2, etc. for sub-branches), for PRs anyone of the other team (if splitting into sub-teams) or anyone but the person submitting the PR can accept.
- Everyone look at PRs and comment on them.
- They should do as much research on their own but let the team know if things are taking longer than expected. Can create a PR to have others look at code if they have any questions.
- Verbally (personal), or slack/ written.