-
Notifications
You must be signed in to change notification settings - Fork 1
Customer Meeting 1
Alex edited this page Jan 31, 2018
·
1 revision
January 26th, 2018
SOEN 341 - UC4
Start time: 12:53 PM
End time: 2:05 PM
Attendees: Evan, Ivan, Nico, Andrew, Hannah, Beeri, Alex, Peter, TA Li
NULL
- Everyone physically but not emotionally present
- Just need to check with grading scheme (on moodle) and everything listed is done
- Add issues on github for features
- Next week check in with TA Li that stuff is done
- Plan for sprint 2 (info on issues, or document in repo)
- Descriptive commit logs
- Everything referenced (issue numbers) i.e. git commit -m “[#3] made X better”
- Discussion and review on github
- Assign tasks to peeps
- Just show up to the meeting
Just cloned? start here - Ready, Set, Debug! - Compiling front-end - Go back home
Below are some useful coding standards you should abide by.
- Create branches per user story / feature as much as possible.
- Make sure your commit passed CI before making a PR.
- Write descriptive commits that reference issues.
- Specify
fixes | closes #<issue id>
at the end of your commits when appropriate. - HTML & CSS
- Javascript
Below are the minutes from each team meeting.
This is a good place to get help.