Difference between revisions of "Team K - OOP344 20133"
(→tasks) |
|||
Line 80: | Line 80: | ||
== tasks == | == tasks == | ||
− | === | + | === Release 0.2 === |
− | * | + | * Chose Dmytro Rudeshko's console class |
− | * | + | * Dmytro Rudeshko |
− | * | + | * Complete |
− | |||
== meetings == | == meetings == |
Revision as of 15:03, 15 December 2013
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
Team Name
Team K
Project Marking Percentage
- due right after study break
Group work: 50% (25 <= xx <= 50) Individual work: 50% + (50 <= xx <= 75) ------------------------- Total 100%
Repository
- repo path: https://github.com/Seneca-OOP344/Team-K
Master Branch Status
Status
- Open/Closed
- Open: you can merge now.
- Closed: Wait for the repo to get opened
Logs
- DateTime, Merged/being Merged by full name, ircnick: mynick, any other info
Coding Style and Standards
- No Tab Character allowed. (replace tabs with spaces)
- Each object must have its own type:
int a;
int b;
CDialog D;
Github Class Setup
1. Go to https://github.com/Seneca-OOP344/Team-K/issues and create a "New Issue".
- "Title" -> 2.*_IssueName -> For example 2.1_CFieldMockups, 2.2_CLabelMockups, etc. - "No one is assigned" gear icon -> Assign yourself to this issue. - "No milestone" gear icon -> 0.2 Milestone - Submit it
2. Go to your GitHub shell, and create a branch with the same name.
- git branch 2.*_IssueName -> For example git branch 2.1_CFieldMockups. - git checkout 2.*_IssueName -> For example git checkout 2.1_CFieldMockups (this will switch to the newly created branch).
3. Create two files with the names of your issues.
- vi cfield.h - Copy and Paste the code from http://zenit.senecac.on.ca/wiki/index.php/The_CIO_Framework_-_OOP344_20123#CField - Save the file. - Create empty .cpp file for this too. - Add #include "filename.h" into the "cio.h" - Make sure it compiles.
4. Submit the changes to our "Team-K" repo.
- git add cfield.* -> cfield should be different in your case. - git commit -m "Added class CField" - git push origin 2.*_IssueName -> Name used in steps 1 and 2 - Branch name - git checkout master - git merge 2.*_IssueName - git push origin master
5. Repeat steps 1 through 4 for all your issues.
Team Members
First Name | Last Name | Section | Seneca Id | wiki id | IRC nick | Blog URL |
---|---|---|---|---|---|---|
Joanna | Madden | C | jmadden | Joanna Madden | jmadden | Talk Nerdy To Me: An Adult's Guide To Back To School |
Dima | Rudeshko | C | drudeshko | Dmytro Rudeshko | sQuaDx | Dima Rudeshko's Blog |
Dmitry | Yastremskiy | B | dyastremskiy | Dmitry Yastremskiy | Hamabama | Hamabama's world |
Eric | Dallo | B | eadallo | Eric Andrew Dallo | eadallo | Eric's Blog |
tasks
Release 0.2
- Chose Dmytro Rudeshko's console class
- Dmytro Rudeshko
- Complete
meetings
- latest will be on top