Honor OVH templates

Signed-off-by: Xavier Lucas <xavier.lucas@corp.ovh.com>

CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing to SVFS
+
+This project accepts contributions. In order to contribute, you should
+pay attention to a few things:
+
+1. your code must follow the coding style rules
+2. your code must be unit-tested
+3. your code must be documented
+4. your work must be signed (see below)
+5. you may contribute through GitHub Pull Requests
+
+# Submitting Modifications
+
+The contributions should be submitted through Github Pull Requests
+and follow the DCO which is defined below.
+
+# Licensing for new files
+
+SVFS is licensed under a BSD license. Anything
+contributed to SVFS must be released under this license.
+
+When introducing a new file into the project, please make sure it has a
+copyright header making clear under which license it's being released.
+
+# Developer Certificate of Origin (DCO)
+
+To improve tracking of contributions to this project we will use a
+process modeled on the modified DCO 1.1 and use a "sign-off" procedure
+on patches that are being emailed around or contributed in any other
+way.
+
+The sign-off is a simple line at the end of the explanation for the
+patch, which certifies that you wrote it or otherwise have the right
+to pass it on as an open-source patch.  The rules are pretty simple:
+if you can certify the below:
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I have
+    the right to submit it under the open source license indicated in
+    the file; or
+
+(b) The contribution is based upon previous work that, to the best of
+    my knowledge, is covered under an appropriate open source License
+    and I have the right under that license to submit that work with
+    modifications, whether created in whole or in part by me, under
+    the same open source license (unless I am permitted to submit
+    under a different license), as indicated in the file; or
+
+(c) The contribution was provided directly to me by some other person
+    who certified (a), (b) or (c) and I have not modified it.
+
+(d) The contribution is made free of any other party's intellectual
+    property claims or rights.
+
+(e) I understand and agree that this project and the contribution are
+    public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+
+
+then you just add a line saying
+
+    Signed-off-by: Random J Developer <random@developer.org>
+
+using your real name (sorry, no pseudonyms or anonymous contributions.)

LICENSE

@@ -1,23 +1,25 @@
-Copyright (c) 2016 OVH SAS
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-Except as contained in this notice, the name of OVH and or its trademarks
-shall not be used in advertising or otherwise to promote the sale, use or other
-dealings in this Software without prior written authorization from OVH.
+Copyright (c) 2016, OVH SAS.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+  * Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+  * Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in the
+    documentation and/or other materials provided with the distribution.
+  * Neither the name of OVH SAS nor the
+    names of its contributors may be used to endorse or promote products
+    derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY OVH SAS AND CONTRIBUTORS ``AS IS'' AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL OVH SAS AND CONTRIBUTORS BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.x

README.md

@@ -92,5 +92,9 @@ happen when copying non-segmented large files server-side. Default is 5 minutes.
 
 Take a look at the [docs](docs) for further discussions about SVFS approach.
 
+## Hacking
+
+Make sure to use the latest version of go and follow [contribution guidelines](CONTRIBUTING.md) of SVFS.
+
 ## License
 This work is under the BSD license, see the [LICENSE](LICENSE) file for details.