Difference between revisions of "WonderCode 20123 - OOP344"

From CDOT Wiki
Jump to: navigation, search
(WonderCode)
(Team Members)
Line 26: Line 26:
 
|[[User:Diao Qiang He|Diao Qiang]]||He||A||[mailto:dqhe1@myseneca.ca?subject=oop344 dqhe1]||[[Special:Contributions/Diao Qiang He|Diao Qiang He]]||Antares||diaoqianghe|| [http://itactics.wordpress.com/ Diao Qiang He's Blog]
 
|[[User:Diao Qiang He|Diao Qiang]]||He||A||[mailto:dqhe1@myseneca.ca?subject=oop344 dqhe1]||[[Special:Contributions/Diao Qiang He|Diao Qiang He]]||Antares||diaoqianghe|| [http://itactics.wordpress.com/ Diao Qiang He's Blog]
 
|-
 
|-
|[[User:Jieming Feng|Jieming]]||Feng||B||[mailto:jmfeng1@myseneca.ca?subject=oop344 jmfeng1]||[[Special:Contributions/Jie Ming Feng|Jie Ming Feng]]||jayfeng||jayfeng|| [http://jayfeng.wordpress.com/ Blue Jay C++]
+
|[[User:Jie Ming Feng|Jie Ming]]||Feng||B||[mailto:jmfeng1@myseneca.ca?subject=oop344 jmfeng1]||[[Special:Contributions/Jie Ming Feng|Jie Ming Feng]]||jayfeng||jayfeng|| [http://jayfeng.wordpress.com/ Blue Jay C++]
 
|-
 
|-
 
|}
 
|}

Revision as of 10:01, 16 October 2012


OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

Team WonderCode

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

WonderCode
First Name Last Name Section Seneca Id Github ID wiki id IRC nick Blog URL
Guiwen Chen B gchen42 Guiwen Chen chgw guiwen Guiwen's Blog
Linpei Fan B lfan9 Linpei Fan Lilyaj lilyfan Learning Path to Software Development
Hye Young (Rody) Choi B hychoi6 Hye Young Choi RodyChoi rodychoi Happy Life
Diao Qiang He A dqhe1 Diao Qiang He Antares diaoqianghe Diao Qiang He's Blog
Jie Ming Feng B jmfeng1 Jie Ming Feng jayfeng jayfeng Blue Jay C++

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
  1. topic and date1
  2. topic and date2

discussions