Difference between revisions of "Knock-Knock!!"
(→Team Members) |
(→Team Name (Knock-Knock!!)) |
||
| Line 3: | Line 3: | ||
* due immediately | * due immediately | ||
<big> | <big> | ||
| − | Group work: | + | Group work: 48% (25 <= xx <= 50) |
| − | Individual work: | + | Individual work: 52% + (50 <= xx <= 75) |
------------------------- | ------------------------- | ||
Total 100% | Total 100% | ||
| Line 12: | Line 12: | ||
== Team Members == | == Team Members == | ||
{| class="wikitable sortable" border="1" cellpadding="5" | {| class="wikitable sortable" border="1" cellpadding="5" | ||
| − | |+ Team Name ( | + | |+ Team Name (Knock-Knock!!) |
! First Name !! Last Name !! Section !! Seneca Id !! Github ID !! wiki id !! IRC nick !! Blog URL | ! First Name !! Last Name !! Section !! Seneca Id !! Github ID !! wiki id !! IRC nick !! Blog URL | ||
|- | |- | ||
| Line 45: | Line 45: | ||
* Rule 1: The asterisk must be beside the variable type when declaring a pointer. (ex) int* number; | * Rule 1: The asterisk must be beside the variable type when declaring a pointer. (ex) int* number; | ||
* Rule 2: Declare each variable separately. | * Rule 2: Declare each variable separately. | ||
| − | * Rule 3: Aline open curly bracket from close curly bracket. | + | * Rule 3: The signature for a safeguard is _KK_HEADERNAME_H_ |
| + | |||
| + | * Rule 4: Always use a open curly bracket and a close curly even if the statement is one line of code. | ||
| + | * Rule 5: Aline open curly bracket from close curly bracket. | ||
if(...) | if(...) | ||
Revision as of 18:46, 15 October 2012
Contents
Team Name (Knock-Knock!!)
Project Marking Percentage
- due immediately
Group work: 48% (25 <= xx <= 50) Individual work: 52% + (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 |
|---|---|---|---|---|---|---|---|
| Jeremiah | Guevarra | B | jrguevarra | Jeremiah Reyes Guevarra | jrguevarra | jrguevarra | Jeremiah's Blog |
| Ran | Li | A | rli64 | Ran Li | ranli | lynnli | 22yue6 |
| Minh Khoa | Nguyen | A | mknguyen2 | Mknguyen2 | kennguyen | kennguyen | Ken's Blog |
| Soohyun | Park | A | spark69 | Soohyun Park | jessica0610 | jessica0610 | Jessica's Blog |
| TianHang (Tim) | Zhouchen | B | thzhouchen | Tian Hang Zhouchen | thzhouchen | thzhouchen | Tim's OOP344 |
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
- Rule 1: The asterisk must be beside the variable type when declaring a pointer. (ex) int* number;
- Rule 2: Declare each variable separately.
- Rule 3: The signature for a safeguard is _KK_HEADERNAME_H_
- Rule 4: Always use a open curly bracket and a close curly even if the statement is one line of code.
- Rule 5: Aline open curly bracket from close curly bracket.
if(...)
{
.....
}
meetings
- latest will be on top
