docs(stdlib/contrib): add docs on how to contribute third party packages (#2775)

Author: nathanielc

CONTRIBUTING.md

@@ -72,6 +72,12 @@ This is done by running `go generate` in the following way.
 $ go generate ./stdlib
 ```
 
+### Contributing Flux Packages
+
+If you have some Flux code that you think the wider community would benifit from please consider contributing it to the Flux repo.
+We have layed out specific guildines in the contrib [README](https://github.com/influxdata/flux/blob/master/stdlib/contrib/README.md).
+uu
+
 ## Pull request guidelines
 
 ### Effective Go

docs/new_flux_ideas_and_guide.md

@@ -1,13 +1,4 @@
 # Getting Started Querying with Flux and InfluxDB
-**NOTE BEFORE YOU GET STARTED:** Forget much of what you know about Flux. This is a new version with some very 
-important differences. As you work through this guide, please keep notes on your thoughts for each section 
-as you encounter it. This ends in a test and you are expected to create a secret Gist with your thoughts and 
-the answers to the questions. You can close with a summary of your feelings after going through the whole thing 
-but please note your thoughts as you go along. It's very likely that you'll think something is crazy or off 
-initially, but maybe think it's ok when you look back later to write your summary. We're interested in 
-seeing this progression of your learning and thought process.
-
-You're allowed to ask questions in the private channel set up for this usability test in Slack. #flux-usability-yourname
 
 Welcome to the getting started guide for Flux. Flux is a functional scripting and query language that looks 
 very similar to Javascript in some parts, but with shortcut syntax for common queries. Its goal is to make 

stdlib/README.md

@@ -42,3 +42,8 @@ All `*_test.flux` files are encoded into `flux_test_gen.go` the non test `.flux`
 > NOTE: The `flux_test_gen.go` file is not a Go test file as we want to include the Flux test code into the normal build.
 This enables downstream projects that import Flux to run the test suite define in the standard library against their implementation.
 
+
+## Third Party Contributions
+
+We collect third part contributions into the `contrib` package.
+See the [README](https://github.com/influxdata/flux/blob/master/stdlib/contrib/README.md) for details on how to contribute a third party package to Flux.

stdlib/contrib/README.md

@@ -0,0 +1,27 @@
+# Contribute Third Party Flux Packages
+
+This directory contains a collections of third party contributions to Flux.
+This is a simple and light weight process for sharing Flux code with the wider community while no other official means of sharing Flux packages exists.
+
+## Adding a New Package
+
+To add a new package first create a new directory using your github account name.
+Then create another directory for the name of your package.
+
+For example if I (@nathanielc) wanted to add a Flux package about reading text based ledger files in Flux I would create a directory named `nathanielc/ledger` under the `contrib` directory.
+I would then place all the Go code, Flux code and corresponding test cases into that directory.
+
+Please see the [CONTRIBUTING](https://github.com/influxdata/flux/blob/master/CONTRIBUTING.md) guide for more details on how to make contributions to the Flux repo.
+
+## Package Ownership
+
+Packages in the `contrib` directory are owned and maintained by their author not the InfluxData team.
+As such the author will be requested for review on all changes to the package.
+
+
+## Future Plans
+
+In the future we may create a more official repository of Flux packages that does not require committing the code to the Flux code repository.
+When that happens we intend to promote the packages from the `contrib` directory into their own Flux package in that repository in what ever form that takes.
+Until then we will collect third party packages into the `contrib` directory.
+