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

From CDOT Wiki
Jump to: navigation, search
(→‎Submission)
(→‎@Cadesh - Andre Rosa)
Line 40: Line 40:
 
====Blog Post(s)====
 
====Blog Post(s)====
 
* Comming Soon!
 
* Comming Soon!
 +
<hr>
 +
 +
===[https://github.com/Cadesh @Cadesh] - Andre Rosa===
  
 +
====External====
 +
* #issue: soon
 +
* #pr: soon
 +
====Internal====
 +
* #issue: soon
 +
* #pr: soon
 +
====Blog Post(s)====
 +
* #1: soon
 
<hr>
 
<hr>
  
Line 144: Line 155:
 
===[https://github.com/eekbatani/ @eekbatani] - Ehsan Ekbatani===
 
===[https://github.com/eekbatani/ @eekbatani] - Ehsan Ekbatani===
  
−
====Pull Requests====
+
 
 
====External====
 
====External====
 
* Issue: https://github.com/uber/baseweb/issues/2364
 
* Issue: https://github.com/uber/baseweb/issues/2364

Revision as of 18:27, 23 November 2019

Contents

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


@cyh0968 - Yohan Choi

Pull Requests

External

  • Issue: Comming Soon!
  • PR: Comming Soon!

Internal

  • Issue: Comming Soon!
  • PR: Comming Soon!

Blog Post(s)

  • Comming Soon!

@Cadesh - Andre Rosa

External

  • #issue: soon
  • #pr: soon

Internal

  • #issue: soon
  • #pr: soon

Blog Post(s)

  • #1: soon

@Fluffiest Bunny - Bowei Yao

Pull Requests

External

Internal

Blog Post(s)

[1] - Nazneen Nahar

Pull Requests

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

Blog Post(s)

@agarcia-caicedo - Ana Garcia

Pull Requests

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

Blog Post(s)

@Grommers00 - James Inkster

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

@vitokhangnguyen - Ngoc Nam Khang Nguyen

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

@ODAVING - Sina Lahsaee

External

Issues

Pull Request

Blog Post(s)

  • #1: Coming Soon...

Internal

Issues

Pull Request

Blog Post(s)

  • #1: Coming Soon...

@jerryshueh - Cheng-Tuo Shueh

Issues

  1. https://github.com/mmohrhard/crash/issues/45 (external)
  2. WIP (internal)

Pull Requests

  1. https://github.com/mmohrhard/crash/pull/53 (external)
  2. WIP (internal)

Blog Post(s)

@eekbatani - Ehsan Ekbatani

External

Internal

Blog Post(s)
  • #1: Coming Soon...


@ultimabgd - Brett Dennis

External

Issues
  • #1: Soon

Pull Requests

  • #1: Soon

Internal

Issues
  • #1: Soon

Pull Requests

  • #1: Soon

Blog Post(s)

@RyanWils - Ryan Wilson

External

Issues
  • #1: Coming Soon

Pull Requests

  • #1: Coming Soon

Internal

Issues
  • #1: Coming Soon

Pull Requests

  • #1: Coming Soon

Blog Post(s)

@s-arika - Sarika Hanif

Pull Requests

  1. external
  2. internal

Blog Post(s)

@dbeigi - Daniel Beigi

Pull Requests

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

Blog Post(s)

@jordanhui19 - Jordan Hui

External

Issues
  • #1:
Pull Requests
  • #1:

Internal

Issues
  • #1:
Pull Requests
Blog Post(s)

@lozinska - Krystyna Lopez

External

Issues

Internal

Issues
Pull Requests

Blog Post(s)

@PavanKKAmra - Pavan Kamra

Pull Requests

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

Blog Post(s)

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OSD_%26_DPS909_Fall_2019_-_Release_0.4&oldid=142186"