Issue 1 (#16)

* added CONTRIBUTING.md and other boilerplate

* remove tegola-specific stuff

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,11 @@
+## Actual Behavior
+
+
+## Expected Behavior
+
+
+## Steps to reproduce the issue.
+
+
+## Data used
+

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,8 @@
+## Requested Behavior
+
+
+## Use Cases
+
+
+## Current work arounds to accomplish current behavior.
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,72 @@
+# go-spatial/proj Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing or otherwise unacceptable behavior may be
+reported by contacting the project team in the [#go-spatial](https://invite.slack.golangbridge.org/) channel. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+

CONTRIBUTING.md

@@ -0,0 +1,88 @@
+# Welcome
+
+Thank you for even thinking about contributing! We are excited to have you. This document is intended as a guide to help your through the contribution process. This guide assumes a you have a basic understanding of Git and Go.
+
+For sensitive security-related issue please start a conversation with a core contributor on the [#go-spatial](https://invite.slack.golangbridge.org/) channel in the [gophers slack](https://invite.slack.golangbridge.org/) organization.
+
+This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md).
+By participating, you are expected to uphold this code. Please report unacceptable behavior to the [#go-spatial](https://invite.slack.golangbridge.org/) channel in the [gophers slack](https://invite.slack.golangbridge.org/) organization or to one of the Core Contributors.
+
+## There are several places where you can contribute. 
+
+### Found a bug or something doesn’t feel right?
+
+Everything we do is done through [issues](https://github.com/go-spatial/proj/issues)(https://github.com/go-spatial/proj/issues). The first thing to do is to search the current issues to see if it is something that has been reported or requested already. If you are unable to find an issue that is similar or are unsure just file a new issue. If you find one that is similar, you can add a comment to add additional details, or if you have nothing new to add you can “+1” the issue.
+
+* If you are unable to find an issue that is similar or are unsure go ahead and file a new one. 
+* If it is a bug,  your can use the following [template](https://github.com/go-spatial/proj/issues/new?template=bug.md). 
+* If this is a rendering bug, please include the relevant data set and configuration file. 
+* If it is a feature request use the following [template](https://github.com/go-spatial/proj/issues/new?template=feature.md).
+* If this is a feature request, please include a description of what the feature is, and the use case for the feature.
+
+Once you have filed an issue, we will discuss it in the issue. If we need more information or you have further questions about that issue, this is the place to ask. This is the place where we will discuss the design of the fix or feature. Any pull request that adds a feature or fixes an issue should reference the issue number.
+
+Don’t be afraid to reach out if you have any questions.  You can reach us on the gophers Slack on the channel #proj or #go-spatial. You can get an invite into the gophers Slack via (https://invite.slack.golangbridge.org/)
+
+## Making a Contribution to the code base.
+
+For the Proj project our master branch is always the most recent stable version of the code base. The current release candidate will be in a branch name for the next version of the software. For example if the current release is v0.6.1 the next release will be v0.7.0, the release candidate branch will be called “v0.7.0”. Please, base all of your pull requests on the release candidate branch.
+
+### Discuss your design
+
+All contributions are welcome, but please let everyone know what you are working on. The way to do this is to first file an issue (or claim an existing issue). In this issue, please, discuss what your plan is to fix or add the feature. Also, all design discussions should happen on the issue. If design discussions happen in a channel, reconcile the decisions to the relevant issue(s). Once, your contribution is ready, create a pull request referencing the issue. Once, a pull request is created one or more of the Core Contributors will review the pull request and may request changes. Once the changes are approved, it will be merged into the current release candidate branch.
+
+Be sure to keep the pull request updated as merge conflicts may occur as other things get merged into the release branch before yours.
+
+Please, note that we may push your pull request to the next release candidate at which point you will have to resolve any conflicts that occur.
+
+### Not sure where to contribute?
+
+Want to contribute but not sure where? Not a problem, the best thing to do is look through the issues and find one that interests you. If the issue has the label `good first issue`, it means that one of the core contributors thinks this is a good issue to start with. But, this doesn’t mean that you have to start with these issues. Go through the issues and see if someone is already working on it. If no one is, state that you will be working on the issue to claim it. If you are unsure where to start on the issue, ask in the issue and one of the Core Contributors will help you out.
+
+## How to build from source
+
+Clone the `go-spatial/proj` repo to your `GOPATH`. The simplest way to do this is to use `go get -u github.com/go-spatial/proj`, navigate to the repository root then: 
+
+* Checkout the current release candidate branch, (i.e. v0.7.0)
+
+	(`git checkout v0.7.0`)
+
+* Create a new feature branch. 
+
+	(`git checkout -b issue-XXX-new_feature`)
+
+* Work on the fix, and run all the tests. We need to run tests with CGO enabled and disabled.
+
+	(`go test ./…`)
+
+* Commit your changes (`git commit -am ‘Add some feature #XXX\n\nExtened description.'`)
+
+### Contribute upstream:
+
+* On github, fork the repo to into your account.
+* Add a new remote pointing to your fork. 
+
+	(`git remote add fork  [email protected]:yourname/rep.git`)
+
+* Push to the branch 
+
+	(`git push fork issue-XXX-new_feature`)
+
+* Create a new Pull Request on GitHub against the Release Candidate branch.
+
+For more information about this work flow, please refer to this [great explanation by Katrina Owen](https://splice.com/blog/contributing-open-source-git-repositories-go/).
+
+## Conventions
+
+* All code should be formatted using:
+
+	(`gofmt -s ./…`).
+
+	- if you find that running `gofmt` produces changes across parts of the code base you're not working on, submit the formatting change in a separate Pull Request. This helps decouple engineering changes from formatting changes and focused the code review efforts. 
+
+* When declaring errors variables, follow the style in the `error_strings.go` file in the `merror` package.
+
+
+## Testing
+
+We try to provide both unit and system tests, and we try to provide a high code coverage percentage.

CONTRIBUTORS.md

@@ -0,0 +1,3 @@
+Thank you to all the people who have [contributed](https://github.com/go-spatial/proj/graphs/contributors) to this project.
+
+Thank you also to everyone who has submitted an [issue or feature](https://github.com/go-spatial/proj/issues?utf8=%E2%9C%93&q=is%3Aissue) request.