Difference between revisions of "The Scurvy Curs"
Marcus Gauer (talk | contribs) (→Team Members) |
|||
| Line 17: | Line 17: | ||
|[[User:Savakian1 | Saro]]|| Avakian || B || [mailto:savakian1@myseneca.ca?subject=oop344 savakian1] || Github:[http://github.com/saro-avakian saro-avakian] | |[[User:Savakian1 | Saro]]|| Avakian || B || [mailto:savakian1@myseneca.ca?subject=oop344 savakian1] || Github:[http://github.com/saro-avakian saro-avakian] | ||
|[[Special:Contributions/Savakian1 | Savakian1]] ||skullman || [http://skullman012291@blogspot.ca Skullman's Blog] | |[[Special:Contributions/Savakian1 | Savakian1]] ||skullman || [http://skullman012291@blogspot.ca Skullman's Blog] | ||
| + | |- | ||
| + | |[[User:Marcus Gauer | Marcus]]|| Gauer || A || [mailto:mgauer@myseneca.ca?subject=oop344 mgauer] || Github:[http://github.com/gauer gauer] || [[Special:Contributions/Marcus Gauer | Marcus Gauer]] || wizardsgambit || [http://http://gambitkun.blogspot.ca/ Epic Adventures] | ||
|- | |- | ||
<!-- use this to add rows to this table: | <!-- use this to add rows to this table: | ||
| Line 25: | Line 27: | ||
|} | |} | ||
| + | |||
==Issues and Status == | ==Issues and Status == | ||
=== Issue description and/or number (1)=== | === Issue description and/or number (1)=== | ||
Revision as of 14:03, 15 October 2012
Contents
The Scurvy Curs (Team XV)
Project Marking Percentage
- due immediately
Group work: XX% (25 <= xx <= 50) Individual work: XX% + (50 <= xx <= 75) ------------------------- Total 100%
Repository
- repo Github id:
Team Members
| First Name | Last Name | Section | Seneca Id | Github ID | wiki id | IRC nick | Blog URL |
|---|---|---|---|---|---|---|---|
| Saro | Avakian | B | savakian1 | Github:saro-avakian | Savakian1 | skullman | Skullman's Blog |
| Marcus | Gauer | A | mgauer | Github:gauer | Marcus Gauer | wizardsgambit | Epic Adventures |
Issues and Status
Issue description and/or number (1)
- Assigned to: FULLNAME
- Code review by: FULLNAME
- Status:
- (being developed/pull request/being reviewed/pushed to master)
- comments:
Issue description and/or number (2)
- Assigned to: FULLNAME
- Code review by: FULLNAME
- Status:
- (being developed/pull request/being reviewed/pushed to master)
- comments:
Coding Rules
meetings
- latest will be on top
