Github

The Github repository for this site is at

Data

This site’s data are stored as three separate json files in data. The three files are accounts.json, contexts.json, and notes.json.

Solve all the issues marked for the milestone named hackathon.

What is NatureNet? NatureNet is a citizen science project with a crowd-sourced design. The goal to increase motivation for participation and to identify creative ways in which people can contribute to sustainable bio-diversity at the Aspen Center for Environmental Studies (ACES).
Who are involved in this project? Three universities: University of North Carolina Charlotte (UNCC), University of Maryland Collge Park (UMD), and University of Colorado Boulder (CU). Tom Yeh, the professor teaching this course, is the Principal Investigator (PI) of CU’s team. Jackie Cameron is a PhD student on the project. She is around today and can answer your question about the project.
Is the site going to be used at one point? Quite possibly. Rather than working on another fake site, we thought it would be more fun and meaningful to hack on a site for something real.

Who works on what? The work must be fairly distributed among the team members. The site’s functionality is broken down into small, individual script files in routes/ and template files in views/ to make it easy for concurrent development and to minimize conflicts.
How can I indicate that I’ve fixed an issue? Each time you’ve fixed an issue, make a commit. Suppose you’ve just fixed issue 1 and are ready to commit to your branch, write fixed issue #1 in the commit message.
```
  $ git commit -a -m 'fixed #1'
```
Github is clever and can automatically resolve #1 to issue 1. The fact that you’ve resolved #1 will be reflected in the commit history, like this:
Should the site go live? Yes. The team leader should publish the site to Heroku following this instruction. You only need to do the Set up step and the Deploy the app step. Ask for help if you are stuck.

2.5 hours

Work together with the same team from the previous week.

Use the same two-level fork-pull procedure you’ve done a few times so far.

Fork. The team leader creates a fork (i.e., team’s fork).
Fork. Each team member creates a fork of this team’s fork.
Work. The team distributes works fairly to individual members to do.
Pull. Once done, each team member makes a pull request to the leader.
Pull. The leader merges all the pull requests and then make a single pull request to the course’s repository (i.e., https://github.com/ucdd2-sp15/nn-express).

Use the following template in the pull request message:


# Team members
Who?
Who?
Who?
Who?

# Score
?/50

# URL
What Heroku URL to access this site? (e.g., https://frozen-tor-4197.herokuapp.com/)