OSD & DPS909 Fall 2019 - Release 0.3

Introduction

DUE: Friday Nov 15

In Release 0.1, you were asked to become familiar working on an open source project on GitHub. This included 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. These pull requests were due weekly, which didn't give much time to work on larger tasks.

For your 0.3 release, you are asked to continue your progression on two fronts. First, you are asked to work on a larger issue in an existing open source project; second, you are asked to contribute a feature to an open source project run by your peers.

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. If you want to work on something new, that's fine too. Just leave yourself enough time to get it setup.

For your internal project PR, you are required to find an area of the project that you want to "own." With 50+ 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, Slack, and the classroom.

You will be marked on the expanded scope and scale of the work you take on during this release. It will not be acceptable to do small "README fixes," single-line typos, or the like during this release. You should look for opportunities to fix a bug, add a feature, or otherwise make a more meaningful code contribution.

Requirements

1. Create 1 larger Pull Request in an external project. This must be larger than anything you did for 0.2, so this probably shouldn't be a "good first issue" type bug fix. If you are unsure, speak to your professor. NOTE: this PR does not need to be merged to be counted.
2. Create 1 Pull Request for a feature in the class' open source project. You are required to pick an area of code in the project, research it, and get it merged into the repository. NOTE: this PR must be merged to count (i.e., creating a PR is not enough).
3. Write a blog post about these two PRs, discussing what you did, the process by which you did it, and what you learned as you went. If you want to split this into two parts, that's also fine.

Submission

@GitHubName - FirstName LastName

Pull Requests

1. (URL to PR in external project)
2. (URL to PR in internal class project)

Blog Post(s)

• Blog Post URL or URLs if you write more than one

---

@Fluffiest Bunny - Bowei Yao

External

• Issue: Coming soon...
• PR: Coming soon...

Internal

• Issue: https://github.com/Seneca-CDOT/telescope/issues/5
• PR: https://github.com/Seneca-CDOT/telescope/pull/9

Blog Post(s)

• https://ragnarokatz.wordpress.com/2019/11/03/some-thoughts-on-internal-group-project/

---

@cyh0968 - Yohan Choi

Pull Requests

1. External-
2. Internal-

Blog Post(s)

• TBA

---

@Thomas Luu - Thomas Luu

External

• Issue: Coming soon...
• PR: Coming soon...

Internal

• Issue: Coming soon...
• PR: Coming soon...

Blog Post(s)

• https://thomasopensourceblog.wordpress.com/2019/11/04/in-search-for-a-long-term-side-project/

---