Giter Site home page Giter Site logo

cs2103-ay1819s1-t13-4 / main Goto Github PK

View Code? Open in Web Editor NEW

This project forked from nus-cs2103-ay1819s1/addressbook-level4

0.0 0.0 5.0 14.55 MB

CAPTracker

Home Page: https://cs2103-ay1819s1-t13-4.github.io/main/

License: MIT License

Shell 0.32% Java 98.65% CSS 1.02% HTML 0.01%

main's People

Contributors

alexkmj avatar alexlmeow avatar amberkj avatar chao1995 avatar cheec avatar damithc avatar edmundmok avatar eugenepeh avatar jeremiah-ang avatar jeremyyew avatar josephambe avatar konglomerator avatar kychua avatar lejolly avatar limmlingg avatar lixiaoooowei avatar m133225 avatar mightycupcakes avatar ndt93 avatar nicholaschuayunzhi avatar okkhoy avatar pierceandy avatar pyokagan avatar rinder5 avatar verylazyboy avatar vivekscl avatar yamgent avatar yamidark avatar yl-coder avatar zhiyuan-amos avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

main's Issues

Feedback on week 8 project progress

Subject: feedback on week 8 project progress

See v1.1 progress guide for more details of the activities mentioned below.
Mid-milestone progress reports are FYI only. They are not graded.

Team progress

Leftovers from v1.1

  • Auto-publishing set up for the team repo and the website is available at link (:heavy_check_mark: well done!)
  • README page:
    • Some parts not related to your product are removed (:heavy_check_mark: well done!)
    • se-edu/addressbook-level[3/4] acknowledged (:exclamation: try to do by next milestone)
    • Ui.png has been updated (:heavy_check_mark: well done!)

Recommended progress for the upcoming milestone

  • Issue labels set up e.g., type.*, priority.* (:heavy_check_mark: well done!)
  • Milestones created: v1.2 v1.3 v1.4 [Please ensure milestones are setup until 'v1.4'] (:heavy_check_mark: well done!)
  • Issues marked as type.Story e.g., (:exclamation: try to do by next milestone)
  • Some issues prioritized using priority.* labels e.g., link (:heavy_check_mark: well done!)
  • Milestone v1.2 planned
    • A suitable deadline set (:exclamation: try to do by next milestone)
    • Issues allocated to v1.2 e.g., link (:heavy_check_mark: well done!)
    • Issues allocated to v1.3 e.g., (:exclamation: try to do by next milestone)
  • Build passing (:exclamation: try to do by next milestone)

Individual progress of @alexkmj

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @jeremiah-ang

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @jeremyyew

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @josephambe

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @BugEyedBug

Leftovers from v1.1

  • Used forking workflow:
    • Forked team repo (:heavy_check_mark: well done!)
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Tutor: @parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-11 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Update Error Message in Results Display Panel

Correct the current message displayed when user enters invalid command. Match it to Modules/CAPGOAL APP rather than People/ADDRESSBOOK APP. Show proper example that will work for CAPGOAL purposes.

Feedback on week 9 project progress

Subject: feedback on week 9 project progress

See v1.2 progress guide for more details of the activities mentioned below.

Team progress

Leftovers from v1.1

  • Auto-publishing set up for the team repo and the website is available at link (:heavy_check_mark: well done!)
  • README page:
    • Some parts not related to your product are removed (:heavy_check_mark: well done!)
    • se-edu/addressbook-level[3/4] acknowledged (:exclamation: try to do by next milestone)
    • Ui.png has been updated (:heavy_check_mark: well done!)

Recommended progress for v1.2

  • Issue labels set up e.g., type.*, priority.* (:heavy_check_mark: well done!)
  • Milestones created: v1.4 v1.2 v1.3 [Please ensure milestones are setup until 'v1.4'] (:heavy_check_mark: well done!)
  • Some issues marked as type.Story e.g., link (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., link (:heavy_check_mark: well done!)
  • Milestone v1.2 managed systematically
    • A suitable deadline set (:heavy_check_mark: well done!)
    • Issues allocated to v1.2 e.g., link (:heavy_check_mark: well done!)
    • All issues/PRs in it are closed/merged. (:heavy_check_mark: well done!)
    • Milestone closed (:exclamation: try to do by next milestone)
    • Code tagged as v1.2 (:heavy_check_mark: well done!)
  • Build passing (:heavy_check_mark: well done!)
  • Some issues assigned to milestone v1.3 e.g., link (:heavy_check_mark: well done!)

Not graded:

  • Updated User Guide for v1.2 (:+1: Kudos!)

Individual progress of @alexkmj

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for v1.2 milestone (:heavy_check_mark: well done!)

Individual progress of @jeremiah-ang

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for v1.2 milestone (:heavy_check_mark: well done!)

Individual progress of @jeremyyew

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for v1.2 milestone (:heavy_check_mark: well done!)

Individual progress of @josephambe

Leftovers from v1.1

  • Used forking workflow:
    • Forked team repo (:heavy_check_mark: well done!)
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:exclamation: try to do by next milestone)
  • josephambe.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Recommended progress for v1.2

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Merged updates to the Developer Guide (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for v1.2 milestone (:exclamation: try to do by next milestone)

Individual progress of @BugEyedBug

Leftovers from v1.1

  • Used forking workflow:
    • Forked team repo (:heavy_check_mark: well done!)
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)
  • Merged updates to documents (:exclamation: try to do by next milestone)
  • bugeyedbug.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Recommended progress for v1.2

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Merged updates to the Developer Guide (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for v1.2 milestone (:exclamation: try to do by next milestone)

Tutor: @parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-18 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Update documentation to resolve issues pointed out by TA

Update documentation to resolve issues pointed out by TA in PR#12

README.adoc

  • Change "ideal" CAP to "target" CAP
  • AB-4 should be part of acknowledgements

docs/UserGuide.adoc

  • Clarify the format for edit

docs/DeveloperGuide.adoc

  • Should be "An" NUS student not "A" NUS student
  • Duplicate must have story (5 and 6)
  • Seems too vague. How do you track progress with only grades? What do you track progress of?

src/main/java/seedu/address/logic/commands/CapCommand.java

  • "Shows" (descriptive style) instead of "Show"
  • Avoid unnecessary line breaks between import statements
  • "Parses" instead of "Parse"

docs/AboutUs.adoc

  • Suggested Jeremiah to change to a bigger photo

Feedback on week 7 project progress

Subject: feedback on week 7 project progress

See v1.1 progress guide for more details of the activities mentioned below.

Team progress

  • Team org and repo set up correctly (:heavy_check_mark: well done!)
  • PR created from team repo to AB-4 (:heavy_check_mark: well done!)
  • Auto-publishing set up for the team repo (:heavy_check_mark: well done!)
  • README page:
    • Ui.png has been updated (:heavy_check_mark: well done!)
  • User Guide: some content has been updated (:heavy_check_mark: well done!)
  • Developer Guide: some content has been updated (:heavy_check_mark: well done!)
  • Team repo git tagged as v1.1 (:heavy_check_mark: well done!)

Individual progress of @alexkmj

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • alexkmj.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @jeremiah-ang

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • jeremiah-ang.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @jeremyyew

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • jeremyyew.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @josephambe

  • Used forking workflow:
    • Created PRs (:exclamation: try to do by next milestone)
    • Reviewed PRs (:exclamation: try to do by next milestone)
  • Merged updates to documents (:exclamation: try to do by next milestone)
  • josephambe.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @BugEyedBug

  • Used forking workflow:
    • Created PRs (:exclamation: try to do by next milestone)
    • Reviewed PRs (:exclamation: try to do by next milestone)
  • Merged updates to documents (:exclamation: try to do by next milestone)
  • bugeyedbug.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Tutor: @parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-04 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Feedback on week 6 project progress

Subject: feedback on week 6 project progress

See mid-v1.1 progress guide for more details of the activities mentioned below.

Team progress

Progress noted (well done! ๐Ÿ‘):

  • Team org and repo set up with the correct names.
  • PR created from team repo to AB-4 accordingly.

Suggestions (to do soon):

None

Individual progress of @alexkmj:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.
  • PRs created to update documents.

Suggestions (to do soon):

  • Create PRs to do a local change to the Java code.

Individual progress of @jeremiah-ang:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.
  • PRs created to update documents.

Suggestions (to do soon):

  • Create PRs to do a local change to the Java code.

Individual progress of @jeremyyew:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.

Suggestions (to do soon):

  • Create PRs for your share of updating documents.
  • Create PRs to do a local change to the Java code.

Individual progress of @josephambe:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.

Suggestions (to do soon):

  • Create PRs for your share of updating documents.
  • Create PRs to do a local change to the Java code.

Individual progress of @BugEyedBug:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.

Suggestions (to do soon):

  • Create PRs for your share of updating documents.
  • Create PRs to do a local change to the Java code.

Tutor: @parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 19/9/2018 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Fix bug for ParserUtil.tokenizer

Tokenizer does not split properly with multiple white-spaces or non space white-spaces. This PR address this issue and adds test cases for it.

Extract CapGoal as a Class

Extract as another class CapGoal (Similarly to Module parameter)

Checks for validity and also has a NIL value

Feedback on week 10 project progress

Subject: feedback on week 10 project progress

See mid-v1.3 progress guide for more details of the activities mentioned below.

Team progress

Recommended progress for v1.3

  • Milestone v1.3 managed systematically
    • A suitable deadline set (:exclamation: try to do by next milestone)
    • Issues allocated to it e.g., link (:heavy_check_mark: well done!)
  • A new jar file has been released on GitHub (:exclamation: try to do by next milestone)

Individual progress of @alexkmj

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @jeremiah-ang

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @jeremyyew

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @josephambe

Leftovers from v1.2

  • Merged updates to the Developer Guide (:exclamation: try to do by next milestone)

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @BugEyedBug

Leftovers from v1.2

  • Merged updates to the Developer Guide (:exclamation: try to do by next milestone)

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Tutor: @parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-25 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.