Add basic documentation

[TomWFox]

• Adds SPM, cocoapods, Carthage installation instructions
• Adds contributing doc
• Changes copyright notice in license
• Improve readme design

[ShawnBaek]

@Tom-Fox1 Thank you for contributing. Who is maintain parse-swift repo? We need to update the contributing guide.

[dplewis]

There are no maintainer for this repo.

New maintainers are welcome

[cbaker6]

@TomWFox I think we can add some of the usage/testing from #12 (comment), particularly the playgrounds part.

The project can be imported via SPM, Cocoapods, Carthage (I've never use this before, but the tests pass) by linking to the repo link directly

[cbaker6]

For the Contributing guide, we can add, brew install swiftlint

[TomWFox]

@cbaker6 @pranjalsatija I think this is good to go now.

The details in the contributing doc are very basic right now but at some point I'll add info about setting up a Parse Server locally to test etc.

Btw I haven't actually tried the SPM or Carthage install but I think they should both work.

[pranjalsatija]

LGTM, other than the one nit!

Before we merge, I'm going to try and install this via SPM or CocoaPods and make sure it works. I'll be able to do that later tonight.

[cbaker6]

@TomWFox lgtm!

I'm not sure if you should add the SwiftLint line I mentioned directly in the doc. If people don't install it locally, they may write a bunch of code that has SwiftLint errors that won't be detected until they make a PR for travis to catch. Installing it locally allows them to see errors and warnings on the fly

[pranjalsatija]

@TomWFox just confirming that I was able to install ParseSwift, then build and launch a blank iOS single view app template using SPM and CocoaPods with no issues.

[TomWFox]

@cbaker6 good point, added

[TomWFox]

@pranjalsatija thanks for checking, only Carthage that is untested now (by us anyway).

[pranjalsatija]

I just tested that out too (just to be safe), it worked.

[TomWFox]

Great!