chore(contrib): include a contribution guide

CONTRIBUTING.md

@@ -0,0 +1,152 @@
+# Contributing
+
+At its core, this project is a Terraform provider, and so an understanding of
+what Terraform is and how it works would help anyone looking to contribute to
+this provider.
+
+For those new to Terraform, the following might be good starting places.
+
+-   [How Terraform Works][how_terraform_works]
+-   [Plugin Types - Providers][how_terraform_works]
+
+For those who are already familiar with Terraform, there are still plenty of
+good resources on the [Extending Terraform][extending_terraform] page that are
+worth looking at, but those might be a topic by topic basis, depending on the
+need.
+
+## DTK Who?
+
+The Developer Toolkit Team is a small team dedicated to open source, and
+integrating our APIs into the [Go Client][client_go], which we then leverage in
+a few projects, including this one.  You can read more about the team
+[here][dtk].
+
+## Future facing APIs
+
+New Relic has several APIs, and its worth understanding at a high level what
+this means for the provider.  Also note, that each of the APIs for a given
+product are the results of many teams, each owning their implementation,
+documentation, and feature set, etc.
+
+However, at a high level there is a concerted effort within New Relic to try
+and move away from the REST APIs, and towards a newer GraphQL based API that we
+call Nerdgraph.  This migration is likely to take years, and the specific
+details about what exactly this means are fuzzy at best.
+
+What is mostly clear at this point, is that each team will continue to own
+their migration, implementation, and feature set in terms of what they choose
+to put into the GraphQL API.
+
+### REST v2 APIs
+
+Most of the documentation for the REST APIs are available at the [API
+Explorer][api_explorer].  There you can see the call structures and responses,
+and what methods are available.
+
+### GraphQL API
+
+To play and experiment with GraphQL, you can use the [graphiql][graphiql]
+interface to perform queries and mutations.  Note that these are using the API,
+so its possible to make changes on your account.  Caution is advised when using
+"mutations".
+
+As mentioned above, New Relic teams will be working to migrate their APIs to
+Nerdgraph, but the specifics about what that means are left to each of those
+teams.  For example, during a migration, one team might choose to drop one
+feature and replace it with another.  This is something of an opportunity to
+change the API and product behavior, and some teams may seize that opportunity
+more than others.
+
+New fields, and new endpoints are available every week in GraphQL, and so the
+API surface area continues grow and scale.
+
+## API Clients
+
+There are a couple of different API clients that are used in this project, but
+the bulk of the work is being done in the [New Relic Go Client][client_go].
+
+There is also a Go Agent that is in use for testing, so that we have a mock
+application to use during integration tests, and there is also an Insights
+client, that is likely on its way out of this project, so I won't go into
+detail here.
+
+## Development Process
+
+### main.tf
+
+When working to implement a feature or test a change, its helpful to have an
+HCL file that is isolated from any real projection/staging environment.  When
+using environment variables to [configure the provider][provider-config-guide],
+the following is all that is needed to get a working provider for most
+situations.
+
+```hcl
+provider "newrelic" {}
+```
+
+Then you can begin to include a resource or data source that you want to test,
+and experiment with changing attributes while running plan/apply to see the
+results of how Terraform will behave.
+
+### Changes to the provider
+
+The simplest case is when the API calls you want to make are already in the [Go
+Client][client_go] and the only changes you need to make are in the provider
+code.  In that case, simply building the provider binary with the correct name
+and running the plan will get you there.
+
+```shell
+go build -o terraform-provider-newrelic && terraform init -upgrade && TF_LOG=INFO terraform plan
+```
+
+### Developing with the [Go Client][client_go]
+
+When changes are required to the [Go Client][client_go] project, it might be
+useful to test changes in the client while developing the provider.  In this
+case, you can tell Go to use your local copy of the [Go Client][client_go] when
+building.
+
+```shell
+go mod edit -replace github.com/newrelic/newrelic-client-go=/Users/zleslie/go/src/github.com/newrelic/newrelic-client-go
+```
+
+This modifies the `go.mod` file to reference a local path on disk rather than
+fetching the code from the remote `github.com/newrelic/newrelic-client-go`.
+With this in place, you can then see how the two projects will behave when
+there are changes in each that are needed for a particular feature.
+
+Once complete, you can PR the change in the client repository, and then `git
+checkout go.mod` in the provider to go back to a released version of client.
+You'll want to make sure the version number in the provider lines up with the
+client version you want to be using as well.
+
+### Commit messages
+
+To keep a style and make allow us to automate the generating of a change log,
+we require that that commit messages adhere to a standard.
+
+TL;DR here is that the commit message must match this regular expression.
+
+    (chore|docs|feat|fix|refactor|tests?)(\([^\)]+\))?: .*
+
+For more information on commit messages, we mostly follow [this standard][conventional_commits].
+
+[api_explorer]: https://rpm.newrelic.com/api/explore/
+
+[client_go]: https://github.com/newrelic/newrelic-client-go/
+
+[dtk]: https://github.com/newrelic/developer-toolkit
+
+[extending_terraform]: https://www.terraform.io/docs/extend/index.html
+
+[graphiql]: https://api.newrelic.com/graphiql
+
+[how_terraform_works]: https://www.terraform.io/docs/extend/how-terraform-works.html
+
+[provider-config-guide]: https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/guides/provider_configuration#configuration-via-environment-variables
+
+[provider_design_principles]: https://www.terraform.io/docs/extend/hashicorp-provider-design-principles.html
+
+[terraform_providers]: https://www.terraform.io/docs/extend/plugin-types.html#providers
+
+[conventional_commits]: https://www.conventionalcommits.org/en/v1.0.0/

LESSONS.md

@@ -0,0 +1,7 @@
+2020-08-18 08:49:56
+
+# Lessons Learned
+
+-   TypeSet vs TypeList
+-   Structure files vs single file per resource/data source
+-   Single API per resource/datasource

README.md

@@ -33,6 +33,9 @@ If you wish to work on the provider, you'll first need [Go](http://www.golang.or
 machine (version 1.13+ is _required_). You'll also need to correctly setup a
 [GOPATH](http://golang.org/doc/code.html#GOPATH), as well as adding `$GOPATH/bin` to your `$PATH`.
 
+Please see our [CONTRIBUTING][contributing] guide for more detail on the APIs
+in use by this provider.
+
 #### Building
 
 Clone repository to: `$GOPATH/src/github.com/newrelic/terraform-provider-newrelic`
@@ -67,3 +70,5 @@ $ make testacc
 ```
 
 [provider_docs]: https://www.terraform.io/docs/providers/newrelic/index.html
+
+[contributing]: https://github.com/newrelic/terraform-provider-newrelic/blob/master/CONTRIBUTING.md