Difference between revisions of "DPS909/OSD600 Fall 2017 Lab 5"
(→Submission) |
(→Submission) |
||
(13 intermediate revisions by 12 users not shown) | |||
Line 89: | Line 89: | ||
|- | |- | ||
| 10 | | 10 | ||
− | | Sean Prashad | + | |Sean Prashad |
− | | https://github.com/SeanPrashad | + | |https://github.com/SeanPrashad |
− | | | + | |https://medium.com/seanprashad/success-d70c84da9217 |
|- | |- | ||
| 11 | | 11 | ||
Line 101: | Line 101: | ||
| Marvin Sanchez | | Marvin Sanchez | ||
| https://github.com/msanchez5 | | https://github.com/msanchez5 | ||
− | | | + | | https://marvinrsanchez.wordpress.com/finding-your-first-good-bug-in-the-community/ |
|- | |- | ||
| 13 | | 13 | ||
Line 126: | Line 126: | ||
| Marco Beltempo | | Marco Beltempo | ||
| https://github.com/marcobeltempo | | https://github.com/marcobeltempo | ||
− | | | + | | http://www.marcobeltempo.com/misc/mozilla-thimble-issue-1918/ |
|- | |- | ||
| 18 | | 18 | ||
Line 169: | Line 169: | ||
|- | |- | ||
| 26 | | 26 | ||
− | + | | Teddy Prempeh | |
− | + | | https://github.com/teddypee | |
− | + | | https://teddyprempeh.wordpress.com/2017/10/07/my-first-bug/ | |
− | |||
− | |||
− | | | ||
|- | |- | ||
| 27 | | 27 | ||
− | | | + | | Mithilan Sivanesan |
− | | | + | |https://github.com/mithilan16 |
− | | | + | |https://mithilanblog.wordpress.com/2017/10/25/enabling-eslint-my-first-bug/ |
|- | |- | ||
| 28 | | 28 | ||
− | | | + | | Ojavi Hewitt |
− | | | + | |https://github.com/ojhew |
− | | | + | |https://osbdotcom.wordpress.com/2017/11/02/my-first-bug/ |
|- | |- | ||
| 29 | | 29 | ||
− | | | + | | Haoyu Yang |
− | | | + | |https://github.com/feihaozi77 |
− | | | + | |https://haoyu1337.blogspot.com/2017/11/working-on-thimble-quickedit-ui.html |
|- | |- | ||
| 30 | | 30 | ||
− | | | + | | Leonel Jara |
− | | | + | | https://github.com/lejara |
− | | | + | | https://lejara.wordpress.com/2017/10/04/my-first-bug-adventure/ |
|- | |- | ||
| 31 | | 31 | ||
− | | | + | | Hans van den Pol |
− | | | + | | https://github.com/HansvandenPol |
− | | | + | | https://opensourcetoronto.wordpress.com/2017/11/28/progress-first-bug/ |
|- | |- | ||
| 32 | | 32 | ||
− | | | + | | Arpit Gandhi |
− | | | + | | https://github.com/aagandhi1 |
− | | | + | | https://arpit1667.wordpress.com/2017/12/19/bug-in-progress/ |
|- | |- | ||
| 33 | | 33 | ||
− | | | + | | Igor Naperkovskiy |
− | | | + | | https://github.com/naperkovskiy |
− | | | + | | https://naperkovskiyblog.wordpress.com/2017/12/20/my-first-steps-with-test-pilot/ |
|- | |- | ||
| 34 | | 34 | ||
− | | | + | | Eric Suarez |
− | | | + | | https://github.com/ericsuhn |
− | | | + | | https://esoscode.wordpress.com/2017/12/05/working-on-my-first-bug/ |
|- | |- | ||
| 35 | | 35 |
Latest revision as of 16:19, 5 January 2018
Contents
Catch Up on Any Outstanding Work
1. Make sure Lab 1, Lab 2, Lab 3, Lab 4 are all completed and posted. If you are late on any of these labs, please complete them and let your professor know so he can mark them.
2. Make sure you have bugs chosen and assigned for DPS909/OSD600 0.1 Release. You must have at least 2 bugs chosen by today, and if you don't, you need to talk to your professor today on Slack and/or during office hours (12:00-3:00, DB1038)
3. Add all your bugs to the DPS909 & OSD600 Fall 2017 Bug List
4. If you have not done so already, set up git and GitHub fully (see below)
5. Work on your chosen bugs. Talk to each other and your professor on Slack about your progress.
6. Write a blog post about how your bugs are going this week. What are you learning as you go? How has it been working on new code? What is the community like? What do they do that's new to you? What are you noticing? What problems are you encountering? Who else is working on the same project as you (e.g., other students in the course)? Have you talked with them, or read their blogs? How are they doing?
New Class Resource Page
Everyone please feel free to checkout and contribute to the newly created resources page.
Setup Git with Github
We'll need an account on Github. If you haven't done so before, take a few minutes to do the following:
- create an account
- verify your email address
- consider enabling two-factor authentication
- add info to your account bio
- consider changing your profile picture
We'll also need to do a bit more setup with git. Specifically, we need to set some global config
options, SSH keys, etc:
- set your username locally
- set your email address locally
- set your line endings
- consider setting other global defaults while you're at it (e.g., your default editor)
- set up SSH keys