Difference between revisions of "OSD & DPS909 Fall 2019 - Release 0.4"

From CDOT Wiki
Jump to: navigation, search
(Blog Post(s))
(Blog Post(s))
(2 intermediate revisions by the same user not shown)
Line 27: Line 27:
 
* Blog Post URL or URLs if you write more than one
 
* Blog Post URL or URLs if you write more than one
  
 +
===[https://github.com/ragnarokatz @Fluffiest Bunny] - Bowei Yao===
 +
 +
====Pull Requests====
 +
====External====
 +
* Issue1: https://github.com/mozilla/addons-code-manager/issues/1193
 +
* PR1: coming soon...
 +
* Issue2: https://github.com/mozilla/addons-code-manager/issues/1246 (inquiry)
 +
 +
====Internal====
 +
* Issue1: coming soon...
 +
* PR1: coming soon...
 +
====Blog Post(s)====
 +
* coming soon...
 +
<hr>
  
 
===[https://github.com/nazneennahare] - Nazneen Nahar===
 
===[https://github.com/nazneennahare] - Nazneen Nahar===

Revision as of 13:46, 16 November 2019

Introduction

DUE: Friday Dec 6

In your 0.3 release, you were asked to continue your progression from 0.1 and 0.2, by working on both an external and internal open source project. In 0.4, you are asked to continue your work in both directions, getting better at open source involvement as you do.

Continue in 0.4 by working on another PR in an external project. Again, it should be larger than anything you did in 0.2. I suggest you consider working on the same repository/project that you've already worked on in the past. Also, make sure you are following-up on any review comments in your 0.3 PR.

For your internal project PR, you are required to continue your work that you started in 0.3. Find another feature or large bug you can address. Ideally, this would build on your PR from 0.3, but it doesn't have to if you have another idea. Once again, 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

Pull Requests

External

Internal

  • Issue1: coming soon...
  • PR1: coming soon...

Blog Post(s)

  • coming soon...

[1] - Nazneen Nahar

Pull Requests

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

Blog Post(s)