added AUTHORS CONTRIBUTORS and CONTRIBUTING.md

Author: pa-m

AUTHORS

@@ -0,0 +1,11 @@
+# This is the official list of sklearn authors for copyright purposes.
+# This file is distinct from the CONTRIBUTORS files.
+# See the latter for an explanation.
+
+# Names should be added to this file as
+#	Name or Organization <email address>
+# The email address is not required for organizations.
+
+# Please keep the list sorted.
+
+Pascal Masschelier <[email protected]>

CONTRIBUTING.md

@@ -0,0 +1,106 @@
+# Contribution Guidelines
+#### Introduction
+
+The sklearn project provides a partial port of the scikit-learn libraries for the Go programming language, and we would like you to join us in improving sklearn's quality and scope.
+This document is for anyone who is contributing or interested in contributing.
+Questions about sklearn or the use of its libraries can be directed to [golang-sklearn](https://groups.google.com/forum/#!forum/golang-sklearn).
+
+#### Table of Contents
+
+[Project Scope](#project-scope)
+
+[Contributing](#Contributing)
+  * [Working Together](#working-together)
+  * [Reporting Bugs](#reporting-bugs)
+  * [Suggesting Enhancements](#suggesting-enhancements)
+  * [Your First Code Contribution](#your-first-code-contribution)
+  * [Code Contribution](#code-contribution)
+  * [Code Review](#code-review)
+  * [What Can I Do to Help?](#what-can-i-do-to-help)
+  * [Style](#style)
+
+## Project Scope
+
+The purpose of the sklearn project is to provide a partial port of the scikit-learn libraries for the Go programming language.
+The libraries should aim to provide building blocks for disciplinary work and advanced algorithms.
+Code should be implemented in pure Go.
+Calls to C, Fortran, or other languages may be justified with performance considerations, but should be opt-in for users.
+Calls to assembly should be opt-out, if included.
+Code should favor readability and explicitness over cleverness.
+This makes code easy to review and verify, not only at submission, but also for users who want to understand how the algorithms work.
+Where possible, the source of algorithms should be referenced in the comments.
+
+## Contributing
+
+### Working Together
+
+When contributing or otherwise participating, please:
+
+- Be friendly and welcoming
+- Be patient
+- Be thoughtful
+- Be respectful
+- Be charitable
+- Avoid destructive behavior
+
+Excerpted from the [Go conduct document](https://golang.org/conduct).
+
+### Reporting Bugs
+
+When you encounter a bug, please open an issue.
+Start the issue title with the repository/sub-repository name, like `metrics: issue name`.
+Be specific about the environment you encountered the bug in.
+If you are able to write a test that reproduces the bug, please include it in the issue.
+As a rule we keep all tests OK.
+
+### Suggesting Enhancements
+
+If the scope of the enhancement is small, open PR.
+If it is large, such as suggesting a new repository, sub-repository, or interface refactoring, then please start a discussion on [the golang-sklearn list](https://groups.google.com/forum/#!forum/golang-sklearn).
+
+### Your First Code Contribution
+
+If you are a new contributor, thank you!  Before your first merge, you will need to be added to the [CONTRIBUTORS](https://github.com/pa-m/sklearn/blob/master/CONTRIBUTORS) and [AUTHORS](https://github.com/pa-m/sklearn/blob/master/AUTHORS) file.
+Open a pull request adding yourself to them.
+All sklearn code follows the MIT license in the [license document](https://github.com/pa-m/sklearn/blob/master/LICENSE).
+We prefer that code contributions do not come with additional licensing.
+For exceptions, added code must also follow a MIT license.
+
+### Code Contribution
+
+If it is possible to split a large pull request into two or more smaller pull requests, please try to do so.
+Pull requests should include tests for any new code before merging.
+It is ok to start a pull request on partially implemented code to get feedback, and see if your approach to a problem is sound.
+You don't need to have tests, or even have code that compiles to open a pull request, although both will be needed before merge.
+When tests use magic numbers, please include a comment explaining the source of the number.
+Benchmarks are optional for new features, but if you are submitting a pull request justified by performance improvement, you will need benchmarks to measure the impact of your change, and the pull request should include a report from [benchcmp](https://godoc.org/golang.org/x/tools/cmd/benchcmp) or, preferably, [benchstat](https://github.com/rsc/benchstat).
+
+### Code Review
+
+If you are a contributor, please be welcoming to new contributors.  [Here](http://sarah.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/) is a good guide.
+
+There are several terms code reviews may use that you should become familiar with.
+
+  * ` LGTM ` — looks good to me
+  * ` SGTM ` — sounds good to me
+  * ` s/foo/bar/ ` — please replace ` foo ` with ` bar `; this is [sed syntax](http://en.wikipedia.org/wiki/Sed#Usage)
+  * ` s/foo/bar/g ` — please replace ` foo ` with ` bar ` throughout your entire change
+
+We follow the convention of requiring at least 1 reviewer to say LGTM before a merge.
+When code is tricky or controversial, submitters and reviewers can request additional review from others and more LGTMs before merge.
+You can ask for more review by saying PTAL in a comment in a pull request.
+You can follow a PTAL with one or more @someone to get the attention of particular people.
+Also note that you do not have to be the pull request submitter to request additional review.
+
+### What Can I Do to Help?
+
+If you are looking for some way to help the sklearn project, there are good places to start, depending on what you are comfortable with.
+You can [search](https://github.com/pa-m/sklearn/issues) for open issues in need of resolution.
+You can improve documentation, or improve examples.
+You can add and improve tests.
+You can improve performance, either by improving accuracy, speed, or both.
+You can suggest and implement new features that you think belong in sklearn.
+
+### Style
+
+We use [Go style](https://github.com/golang/go/wiki/CodeReviewComments).

CONTRIBUTORS

@@ -0,0 +1,21 @@
+# This is the official list of people who can contribute
+# (and typically have contributed) code to the sklearn
+# repository.
+#
+# The AUTHORS file lists the copyright holders; this file
+# lists people.  For example, Google employees would be listed here
+# but not in AUTHORS, because Google would hold the copyright.
+#
+# When adding J Random Contributor's name to this file,
+# either J's name or J's organization's name should be
+# added to the AUTHORS file.
+#
+# Names should be added to this file like so:
+#     Name <email address if known>
+#
+# Please keep the list sorted. 
+# (ex:  git shortlog -e -s -n|cut -d$'\t' -f 2-|grep -iv masschelier|sort)
+
+
+Graham Clark <[email protected]>
+Sebastien Binet <[email protected]>

README.md

@@ -38,7 +38,7 @@ All of this is
 - unit tested but coverage should reach 90%
 - underdocumented but python sklearn documentation should be sufficient
 
-Many thanks to gonum and scikit-learn contributors
+Many thanks to gonum and scikit-learn authors and contributors
 
 PRs are welcome