Skip to content
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.

Latest commit

 

History

History
106 lines (65 loc) · 3.19 KB

CS3282Schedule.md

File metadata and controls

106 lines (65 loc) · 3.19 KB
Raw

CS3282 Schedule

Stage 1 : Learning

Week 1

  • Set up the dev environment in your Computer. Follow instructions provided by the project for new contributors.

  • Lecture : Module Intro

  • Saturday: Code Sprint 0900- 1600 (SR10)

    The code sprint is an opportunity for you to spend an extended amount of time on the project so that you get a solid start to the coding activities. Some project mentors may be available during this time for you to discuss project related matters with them.

    • 0930 - 1200 : Project work, mock interviews
    • 1200 - 1300 : Lunch break (lunch not provided)
    • 1300 - 1500 : Project work, mock interviews
    • 1500 - 1530 : Pizza! 🍕
    • 1530 - 1700 : Project work, mock interviews

Week 2

  • Try to have about 5 ongoing PRs at all times. We cannot predict how long a PR will take to merge.

  • When selecting issues to work on, it is ok to pick 1 or 2 low-hanging fruits (to increase your PR count) but also pick progressively harder PRs related to your selected area.

  • By Wednesday midnight: Create a PR against this repo to report weekly progress.

    • Follow the folder/file convention and the template used by this placeholder file students/AY1617S2/johnDoe/JohnDoe-Progress.md.
    • Only merged PRs can be included. A merged PR can be included in any future week (not restricted to the week it was merged).
    • PRs done prior to the semester can be included in this week or in a future week.
    • Work done for any of the three internal projects can be included, not just your main project.
    • Use PR number (not the issue number) and link to the PR.
    • Effort : Your estimated number of hours the work should have taken in retrospect. Use only values 1, 2, 4, 8, 16, 32 (rounded to the nearest number).
    • Type : Indicates whether you are the developer (D) or the reviewer (R). Use O for other type of work such as demos, research, user support, etc.
    • Format for PR title and the commit title is Week 2 Progress: John Doe. Squash all changes into one commit.
    • Use a different branch for each PR. The branch name can be something like john-doe-week2-progress. This way it is easier to keep your master branch exactly same as upstream repo.

  • Lecture : Project specific discussions

Week 3

  • Please get your PRs reviewed by 1-2 peers before requesting reviews from senior devs.

  • Continue to submit weekly progress by creating PRs. Marks will be uploaded to IVLE in due course.

  • Lecture : Project specific discussions

Stage 2 : Contributing

Week 4

  • Lecture : Project specific discussions

Week 5

  • Lecture : Project specific discussions

Week 6

  • Lecture : Project specific discussions

======================== RECESS ==============================

Week 7

  • Lecture : Project specific discussions

Week 8

  • Lecture : Project specific discussions

Week 9

  • Lecture : Project specific discussions

Stage 3 : Managing

Week 10

  • Lecture : Project specific discussions

Week 11

  • Lecture : Project specific discussions

Week 12

  • Lecture : Project specific discussions

Week 13

  • Wednesday: STePS
  • Thursday: No session