release 0.3

Release 0.3

Due Date

Sunday November 20 by midnight

Overview

In Release 0.1 and the initial Labs, you were asked to become familiar working on an open source project on GitHub. This included working with git, filling issues, creating pull requests, receiving and conducting code reviews, etc.

In Release 0.2, you were asked to take what you'd learned in 0.1, and start to expand your abilities, working on 4 pull requests in various open source projects. This helped to prepare you to work on larger and more complex projects

For your 0.3 release, you are asked to continue this progression, focusing on:

working collaboratively in larger open source groups
going deeper into projects vs. always finding new repos to work on
gaining more experience doing code reviews

Requirements

For 0.3 you will work on at least two new Pull Requests and two Code Reviews:

First, you are asked to work on a larger issue in an existing open source project (i.e., a project external to the course). This can be one of the repos you contributed to during Hacktoberfest, or something that you wanted to do but didn't have time during 0.2

Second, you are asked to contribute something meaningful to an open source project run by the class. There are four "internal" projects to choose from:

The Telescope project: https://github.com/Seneca-CDOT/telescope
VSCode Seneca College extension: https://github.com/Seneca-CDOT/vscode-seneca-college
My Photohub project: https://github.com/humphd/my-photohub
The Modernization of the IPC144 C Programming Curriculum: https://github.com/Seneca-ICTOER/Intro2C

Third, you are asked to contribute two Code Reviews to one or both of the Telescope/IPC144 repos. Find Pull Requests that need to be reviewed and test, review, and help improve the code so that it can be merged.

1. External Project Contribution

Create at least 1 new Pull Request (i.e., you can do more if you want) in an external open source project on GitHub. This PR must be a bit larger than anything you did for 0.2 (i.e., continue your progression). As a result, this can't be a 1-line fix or typo correction. If you are unsure about the scope of your PR, speak to your professor. You don't have to write 10,000 lines of code, so don't pick something so big that you guarantee that you'll fail in the time that you have. Pick something a bit bigger or a bit more complex or a bit more rewarding than your 0.2 PRs.

For your external project PR, I suggest you consider working on a repository/project that you've already worked on in the past and have setup on your machine. You could also work on a repo that one of your friends/classmates did during Hacktoberfest, and they recommend. You could also work on a repo together with other students in the course (i.e., create a team, and fix some bugs in the same project code so you can help each other vs working along). If you want to work on something new, that's fine too. Just leave yourself enough time to get it setup properly and learn the code.

The external PR does not need to be merged by the deadline to be counted.

2. Internal Project Contribution

Create at least 1 new Pull Request (i.e., you can do more if you want) to fix something in the Telescope Issues or IPC144 Issues. You are not limited to the existing Issues, and can file new ones, or have someone in the community suggest/file one for you. Discuss your ideas in Slack or with your professor.

With lots of other students all working in the same project, you'll have to work together to break things down into small enough pieces, so everyone can collaborate on the same code. Make sure you work with other people, and don't try to do things alone.

Your internal project PR must be merged to count, so if you don't work with the community, you'll be unlikely to get your work merged. Communication is key, in Issues and on Slack.

3. Internal Code Reviews

Having lots of students all contribute to the same projects means that there will be many pull requests needing to be reviewed and tested on a regular basis. You are asked to contribute at least two Code Reviews (i.e., you can do more if you want) to one or both of the Telescope/IPC144 repos. A proper code review takes time and helps the author improve their work. Multiple people can and should review the same pull request (i.e., it's fine for 6 people to all do a review of the same pull request). However, try to pick pull requests that don't have a review before you join another one.

Blog Posts

Write blog posts about all of your work (i.e., 1-per PR and 1 for all of your code reviews) discussing what you did, the process by which you did it, and what you learned as you went. Try to show how you are measuring your progress from 0.2 with these PRs, and how successful you were. Make sure you include links to everything.