Difference between revisions of "OSD600 and DPS909 Winter 2018 Lab 5"

From CDOT Wiki
Jump to: navigation, search
(Created page with "=Mixing Open Data, Open Source, Open Assets= This week we're starting a case study looking at practical ways to use and mix open data sets, open source, and open assets. Alo...")
 
(1. Feature Request)
Line 14: Line 14:
 
You are asked to implement a solution for the following Issue: https://github.com/humphd/bridge-troll/issues/6
 
You are asked to implement a solution for the following Issue: https://github.com/humphd/bridge-troll/issues/6
  
Please '''fork''' the https://github.com/humphd/bridge-troll repo and '''create a new branch''' named <code>issue-6</code.
+
Please '''fork''' the https://github.com/humphd/bridge-troll repo and '''create a new branch''' named <code>issue-6</code>.
  
 
Implement your fix on your <code>issue-6</code> branch, and then push to GitHub.
 
Implement your fix on your <code>issue-6</code> branch, and then push to GitHub.

Revision as of 13:52, 14 March 2018

Mixing Open Data, Open Source, Open Assets

This week we're starting a case study looking at practical ways to use and mix open data sets, open source, and open assets. Along the way we're also exploring modern approaches to collaborative, modern JavaScript development.

In this lab, you are asked to add a new feature to the project. The goals of the lab include:

  • Practice working on front-end JavaScript on GitHub
  • Gain experience using open source APIs and modules
  • Read and Write code written in modern JavaScript
  • Gain experience working with common collaborative tooling on GitHub

1. Feature Request

You are asked to implement a solution for the following Issue: https://github.com/humphd/bridge-troll/issues/6

Please fork the https://github.com/humphd/bridge-troll repo and create a new branch named issue-6.

Implement your fix on your issue-6 branch, and then push to GitHub.

2. Blog

Write a blog post about your experience adding the feature. Here are some things to pay attention to as you work:

  • Did you run into any problems? How did you overcome them?
  • What did you need to learn in order to complete the work?
  • Talk about the technologies you used. What did you think of them? Were they easy to use? What did you like/dislike about them.
  • What does your fix look like (screenshots)?
  • What approach did you take to solving this?

Please add a line for your blog and GitHub branch (with the commits for your fix) in the following table:

# Name Git URL to Branch for Fix (URL) Blog Post (URL)
1
2
3
4
5
6
7
8
9
10
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