write CONTRIBUTING.md

[janethuangg]

Each team must collaboratively draft a CONTRIBUTING.md - a Markdown document exclusively dedicated to how others might contribute to this project. This document is essentially a contract agreed-upon by all developers and contributors, and includes at a minimum:

Details on the team's values and process:

• the Team Norms
• the Git workflow that the team follows
• a detailed description of the rules of contributing and any considerations or how and what to contribute
• instructions for setting up the local development environment in order to work on this project
• instructions for building and testing the project (update with that information once the project reaches that stage) This documents allows potential contributors, whether in the open source community or in a private organization, to see the project's rules and processes for contributions. It should be well-formatted with clear headings and subheadings.

GitHub provides a link to this document automatically to any user who creates a Pull Request on this project

[janethuangg]

• sprint retro & kickoff (one meeting) on the mon/tues of the sprint's starting week – need to set a time for sprint 1 planning (must be done before wed)
• async standup? using geekbot in slack

[janethuangg]

github workflow: https://knowledge.kitchen/Feature_branch_version_control_workflow

[janethuangg]

@cindy to ask tutor if we can do async / how many times per week / how demo works @janethuangg to send out lettucemeet to get a rough sense of weekly availabilities

team norms

• prettier
• PRs: include screenshot for visual changes - 1 person's approval before merging?
• just slack for help

[janethuangg]

based on https://lettucemeet.com/l/mX0Yr, seems like Tu/Th 9pm might be the best time for standup!