TA Meeting 3 - Tuesday January 30th 2018

All members must be present during TA Meetings, otherwise we'll be losing points. We can change the meeting time to ensure everyone can be present.

Everyone need to be coding.

We must use github for everything, including images.

we should have everything written (storypoints) so that the TA reviews them and answers any questions we may have.

We can only start coding with the approval of the TA (the client)

We need to do a dummy pull request (Jenkins)

Make the architectural pattern more abstract than design pattern. (architectural diagram)

Of the planned features, solve Equations, s ave value, rotate screen are all good for spring 2.

Any team member can approve the test of another member.

For the unit test backend test is fine.

In the grading scheme the plan for next release is what will be discussed with the TA during the meeting.

Coding style must be documented in the wiki, and must be verified during code reviews.