Changes

Jump to: navigation, search

OSD & DPS909 Fall 2019 - Release 0.1

12 bytes added, 11:56, 11 September 2019
Filing Issues
You are asked to file '''2 separate Issues''', each in a '''different repository''' from the [https://wiki.cdot.senecacollege.ca/wiki/DPS909_%26_OSD600_Fall_2019_-_Lab_2#Submission Lab 2 Submissions list]. See [https://help.github.com/en/articles/creating-an-issue this article on GitHub] for more details on how to file an issue.
The '''first issue should be to fix or improve something in the repository's existing code'''. Try running the code, and see if you can find any bugs. Read the code and see if there are any problems you notice with the way it's been written. You're looking for a way to help make the app and/or code better than it currently is. This does not include making coding style changes. Respect the existing coding style of the author vs. your own preferences.
The '''second issue should be to add a new feature to a second repository'''. You can use the [https://wiki.cdot.senecacollege.ca/wiki/DPS909_%26_OSD600_Fall_2019_-_Lab_2#Step_7:_Add_Something_Cool list of suggested features from Lab 2] or suggest your own. You'll need to convince the repository's owner that your idea is worth doing, and give enough detail about your change for them to think it necessary.
In both cases, before you file any new issues in a repository, take a look at the other issues that are already filed, and any pull requests that have been made. Don't duplicate someone else's work, or get in the way of another contributor.

Navigation menu