ay1920s1-cs2103-f10-3 / main Goto Github PK

So that I can complete my quizzes on time

So that I can study on my own.

So that I can feel a sense of achievement

So that I can learn from my mistakes

So that I can make the application better to benefit more CS2103/T students.

So that I can get to lectures on time and access facilities easily

So that I can test myself on coding proficiency too.

So that I will not forget to do revision.

So that I do not have to refer to Luminus.

So that I can learn better

Team progress for v1.1

• Product website available at the expected URL(:heavy_check_mark: well done!)
• PR created from team repo to our repo(:heavy_check_mark: well done!)
• README page:
  • Some parts not related to your product are removed(:heavy_check_mark: well done!)
  • se-education.org acknowledged(:heavy_check_mark: well done!)
  • Ui.png has been updated(:heavy_check_mark: well done!)
• Product website title changed to match your product(: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 @khiangleon for v1.1

• Team repo forked to your GitHub account https://github.com/khiangleon/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs #12 #11 #9 #8 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs (:exclamation: try to do by next milestone)
• Merged updates to documents(:heavy_check_mark: well done!)
• khiangleon.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @ShaunNgTX for v1.1

• Team repo forked to your GitHub account https://github.com/shaunngtx/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs #4 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs (:exclamation: try to do by next milestone)
• Merged updates to documents(:heavy_check_mark: well done!)
• shaunngtx.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @neoshh for v1.1

• Team repo forked to your GitHub account https://github.com/neoshh/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs #5 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs (:exclamation: try to do by next milestone)
• Merged updates to documents(:heavy_check_mark: well done!)
• neoshh.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @jxofficial for v1.1

• Team repo forked to your GitHub account https://github.com/jxofficial/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs #2 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs (:exclamation: try to do by next milestone)
• Merged updates to documents(:heavy_check_mark: well done!)
• jxofficial.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @wilfredbtan for v1.1

• Team repo forked to your GitHub account https://github.com/wilfredbtan/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs #6 #7 #3 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs (:exclamation: try to do by next milestone)
• Merged updates to documents(:heavy_check_mark: well done!)
• wilfredbtan.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Tutor: @kthSim

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-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.}

So that I can sort the questions easily and save time searching for them

So that I will not have to spend as much time studying the easy concepts.

So that I won’t feel lonely

So that I can revise for those topics.

So that I can motivate other students.

So that I can revise for my other modules using this application as well.

So that I can make the application better and customise it for myself.

So that I can teach better

So that I can gauge my level of progress in completing the syllabus.

So that I know what to expect on results release day.

So that I can refer back to the question when I am free.

So that I can learn using spaced-retrieval

So that I can further increase my work efficiency

So that I can save time.

So that I can raise them up during tutorials.

So that I will study

Progress of this week

• Team org and repo set up with the correct names

• Product website available at the expected URL(:heavy_check_mark: well done!)

• PR created from team repo to our repo(:exclamation: try to do by next milestone)

Individual progress of @khiangleon

• Team repo forked to your GitHub account https://github.com/khiangleon/main (:heavy_check_mark: well done!)

• A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

• A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @ShaunNgTX

• Team repo forked to your GitHub account https://github.com/shaunngtx/main (:exclamation: try to do by next milestone)

• A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

• A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @neoshh

• Team repo forked to your GitHub account https://github.com/neoshh/main (:heavy_check_mark: well done!)

• A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

• A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @jxofficial

• Team repo forked to your GitHub account https://github.com/jxofficial/main (:exclamation: try to do by next milestone)

• A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

• A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @wilfredbtan

• Team repo forked to your GitHub account https://github.com/wilfredbtan/main (:exclamation: try to do by next milestone)

• A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

• A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Tutor: @kthSim

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-20 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.}

So that I can set new targets and goals.

So that I can refer to it conveniently for revision.

So that I can become more proficient with Git.

So that I can go directly to studying

• Update project website

• Update UG

• Update DG