search

mqchau / EECS22L_Project2

GNU General Public License v3.0
0 stars 0 forks source link

code schedule #2

Open mqchau opened 10 years ago

mqchau commented 10 years ago

Experience from last project is that we need a well - defined schedule so everybody knows how much they are expected to complete. Here is the schedule I drafted. If you have any obligations, you must state now. Otherwise please reply "Agree". We will follow this schedule after we all agree on this.

https://drive.google.com/a/uci.edu/#folders/0B6hFDKbQXelUUlFwRVE4d0pGWFU

Quan.

rmorrison23 commented 10 years ago

Agree

On Feb 11, 2014, at 11:17 PM, mqchau notifications@github.com wrote:

Experience from last project is that we need a well - defined schedule so everybody knows how much they are expected to complete. Here is the schedule I drafted. If you have any obligations, you must state now. Otherwise please reply "Agree". We will follow this schedule after we all agree on this.

https://drive.google.com/a/uci.edu/#folders/0B6hFDKbQXelUUlFwRVE4d0pGWFU

Quan.

— Reply to this email directly or view it on GitHub.

hanchelc commented 10 years ago

Agree!

On Tue, Feb 11, 2014 at 11:59 PM, rmorrison23 notifications@github.comwrote:

Agree

On Feb 11, 2014, at 11:17 PM, mqchau notifications@github.com wrote:

Experience from last project is that we need a well - defined schedule so everybody knows how much they are expected to complete. Here is the schedule I drafted. If you have any obligations, you must state now. Otherwise please reply "Agree". We will follow this schedule after we all agree on this.

https://drive.google.com/a/uci.edu/#folders/0B6hFDKbQXelUUlFwRVE4d0pGWFU

Quan.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/2#issuecomment-34846761 .

Hanchel

antrinh commented 10 years ago

Agreed

On Wed, Feb 12, 2014 at 10:19 AM, hanchelc notifications@github.com wrote:

Agree!

On Tue, Feb 11, 2014 at 11:59 PM, rmorrison23 <notifications@github.com

wrote:

Agree

On Feb 11, 2014, at 11:17 PM, mqchau notifications@github.com wrote:

Experience from last project is that we need a well - defined schedule so everybody knows how much they are expected to complete. Here is the schedule I drafted. If you have any obligations, you must state now. Otherwise please reply "Agree". We will follow this schedule after we all agree on this.

https://drive.google.com/a/uci.edu/#folders/0B6hFDKbQXelUUlFwRVE4d0pGWFU

Quan.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub< https://github.com/mqchau/EECS22L_Project2/issues/2#issuecomment-34846761> .

Hanchel

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/2#issuecomment-34898382 .

ghost commented 10 years ago

Agree

On Feb 11, 2014, at 11:17 PM, mqchau notifications@github.com wrote:

Experience from last project is that we need a well - defined schedule so everybody knows how much they are expected to complete. Here is the schedule I drafted. If you have any obligations, you must state now. Otherwise please reply "Agree". We will follow this schedule after we all agree on this.

https://drive.google.com/a/uci.edu/#folders/0B6hFDKbQXelUUlFwRVE4d0pGWFU

Quan.

— Reply to this email directly or view it on GitHub.

mqchau commented 10 years ago

Jamie and Kevin, Did you guys read this schedule yet? What are your opinions? Quan.

duongkt commented 10 years ago

Hmm i sure i said agree a few days back... Guess i forgot to hit send. Woops

AGREE

On Fri, Feb 14, 2014 at 2:51 PM, mqchau notifications@github.com wrote:

Jamie and Kevin, Did you guys read this schedule yet? What are your opinions? Quan.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/2#issuecomment-35133002 .

jamiesl commented 10 years ago

Sorry, forgot to reply. Agree