Difference between revisions of "DPS909/OSD600 Fall 2017 Lab 5"

From CDOT Wiki
Jump to: navigation, search
m (Submission)
Line 1: Line 1:
 
==Catch Up on Any Outstanding Work==
 
==Catch Up on Any Outstanding Work==
  
1. Make sure '''[[DPS909/OSD600 Fall 2017 Lab 1]], [[DPS909/OSD600 Fall 2017 Lab 2]], [[DPS909/OSD600 Fall 2017 Lab 3]], [[DPS909/OSD600 Fall 2017 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.
+
1. Make sure '''[[DPS909/OSD600 Fall 2017 Lab 1|Lab 1]], [[DPS909/OSD600 Fall 2017 Lab 2|Lab 2]], [[DPS909/OSD600 Fall 2017 Lab 3|Lab 3]], [[DPS909/OSD600 Fall 2017 Lab 4|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)
 
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)
Line 85: Line 85:
 
|-
 
|-
 
| 10
 
| 10
|  
+
| Sean Prashad
|
+
| https://github.com/SeanPrashad
|
+
| TBD
 
|-
 
|-
 
| 11
 
| 11

Revision as of 21:36, 4 October 2017

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?

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:

  1. create an account
  2. verify your email address
  3. consider enabling two-factor authentication
  4. add info to your account bio
  5. 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:

  1. set your username locally
  2. set your email address locally
  3. set your line endings
  4. consider setting other global defaults while you're at it (e.g., your default editor)
  5. set up SSH keys

Submission

# Name GitHub Account (URL, eg. https://github.com/humphd) Blog Post (URL)
1
2
3
4
5
6
7
8
9
10 Sean Prashad https://github.com/SeanPrashad TBD
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40