-
Notifications
You must be signed in to change notification settings - Fork 1
Standup Meeting 1
Alex edited this page Jan 31, 2018
·
1 revision
January 30th, 2018
SOEN 341 - UC4
Start time: 10:08 PM
End time: 10:23 PM
Attendees: Evan, Nico, Andrew, Hannah, Beeri, Alex, Peter Absent: Ivan
Follow up on Laravel learning
- Procedures for standup meetings
- No longer than 10-15 minutes
- Main objective: progress updates and plans for time until next meeting
- Should occur 2-3 times per week
- Laravel learning progress
- Beeri : I started looking at the tutorials on github for laravel. I started also looking at the structure of our project tools setup using laragon so I can understand it and to better utilize it as time goes along and tasks are taken on.
- Evan: Difficult understanding. Will improve in the future.
- Nico : Watched all laracasts videos, and should be good.
- Andrew : Spent some time learning TDD within the Laravel framework.
- Hannah: I’ve looked a a few general videos
- Alex: Started reading on how to write database migrations to create tables only using PHP.
- Peter: did some light reading on es6 notations/laravel framework, haven't started tutorial
- Beeri : Continue the tutorials and get more understanding of laravel framework and how to change or add things.
- Evan: Will do some research and will continue learning Laravel.
- Nico : Will wait for evan to finish learning laravel to do questions.
- Andrew : Will write unit tests for User model, login & password recovery features.
- Hannah: Will do try out some tutorials
- Alex: Will work with Nico to create simple table layout for the database for sprint 1.
- Peter: start a laravel tutorial and create something close to my first task (front end at least)
- We all need to do our tasks
- Determine best times for standup meetings based on doodle poll results
- Start planning out the database design
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.