CrimeVis

Info201 Final project repository

Link to the app

Link to the dataset

Git Collaboration

• Always make your commit messages meaningful and not ambiguous or vague.
• Comment your code it helps when people review before merges.
• Always work on a separate branch before changing any code. Avoid working on master. git branch is a good way to check to see if you're on another branch before working (If it's a small change just use master but be sure to check in when you do and make sure no errors pop up).
• git pull often just because changes are likely to occur quickly and address conflicts.
• If you see that your pull request has merge conflicts address them don't leave it alone.
• Message in the chats (either slack or fb messenger) if you make any additions or send PR's.
• Add any new .R files you create into the scripts directory just to keep things organized.

Extra Dependencies

• install.packages("leaflet")
• install.packages("shinythemes")

Issues

• When you take on new issues make sure to assign yourself before starting that way nobody else is working on it mistakenly assuming that nobody is on it.
• When creating new issues be sure to put labels and a decent enough description on it that way the person working on it knows what to do.

Pull Requests

• Same with commit messages, keep your pull request descriptions clear and not ambiguous or vague.
• After pushing your branch up to GitHub make pull requests from there (should typically pop up near the top with a message someone along the lines "new branch added" and a pull request button will typically be there)

Other Resources:

GitHub Desktop is a really handy way of seeing what commits you are making, changing branches, and all the things that you don't really want to type in terminal so if you want to download that then go for it!

Questions

Either create an issue so that we can respond or just message anyone, I'm sure all of us will be able to come up with something.