cs2113-ay1819s1-w12-1 / main Goto Github PK

Well-defined features in the form of user stories and use cases.
List down all the available features.
Update in the projects dashboard too.

• Edit the title of this issue
• Edit the labels

• Migration of addressbook data from old pc to new pc can be done by just copying the storage file.

• As a student who uses multiple organization tool, I want to export my data to other applications such as Google Calendar so that…

• Edit the title of this issue
• Edit the labels

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

Recommended progress for the upcoming milestone

• Issue labels set up e.g., type.*, priority.* (:exclamation: try to do by next milestone)
• 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 (:heavy_check_mark: well done!)
• 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 @linnnruoo

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 @driedmelon

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 @elstonayx

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 @jitwei98

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 @junweiljw

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 (:heavy_check_mark: well done!)

Tutor: @okkhoy

Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2018-10-10 02: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.

The current icon is ugly. It needs to be changed

Display empty calender before the implementation of metting scheduling features.
Add functional command: calender

test new command : calender

• Edit the title of this issue
• Edit the labels

@jitwei98 can help me take a look into this? I wanted to edit the dummy content but it's not showing after it's rebuilt

[]

Ref #58

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-3 or AB-4 (:exclamation: try to do by next milestone)
• 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 @linnnruoo

• 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!)
• Merged changes to java/fxml (:heavy_check_mark: well done!)
• linnnruoo.png uploaded and linked from AboutUs page, merged (:exclamation: try to do by next milestone)

Individual progress of @driedmelon

• Used forking workflow:
  • Created PRs (:exclamation: try to do by next milestone)
  • Reviewed PRs (:heavy_check_mark: well done!)

• Merged updates to documents (:exclamation: try to do by next milestone)
• Merged changes to java/fxml (:exclamation: try to do by next milestone)
• driedmelon.png uploaded and linked from AboutUs page, merged (:exclamation: try to do by next milestone)

Individual progress of @elstonayx

• 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!)
• Merged changes to java/fxml (:heavy_check_mark: well done!)
• elstonayx.png uploaded and linked from AboutUs page, merged (:exclamation: try to do by next milestone)

Individual progress of @jitwei98

• 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!)
• Merged changes to java/fxml (:heavy_check_mark: well done!)
• jitwei98.png uploaded and linked from AboutUs page, merged (:exclamation: try to do by next milestone)

Individual progress of @junweiljw

• 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)
• Merged changes to java/fxml (:exclamation: try to do by next milestone)
• junweiljw.png uploaded and linked from AboutUs page, merged (:exclamation: try to do by next milestone)

Tutor: @okkhoy

Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2018-10-03 02: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.

• Edit the title of this issue
• Edit the labels

Put user stories in GitHub issues

• As a meticulous student, I want to open the file location of my address book data so that I can make a backup of it.

• "open ."

• Remember to save to the storage file before opening file explorer.