Merge pull request #97 from Esri/dev

Merge dev into master

Author: kgonzago

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+Contributing to the ERG Widget Repository
+=========================================
+
+Esri welcomes contributions from anyone and everyone. Please see our [guidelines for contributing](https://github.com/esri/contributing).
+
+- ***All development work is to be performed in a branch and when ready for release committed to master.***
+- ***Your code is required to adhere to coding rules using [JS Hint](http://www.jshint.com/) and [JSCS](http://jscs.info/). There is a .jshintrc file and .jscs file included in the root folder which enforces these styles.***
+
+Issues
+------
+Feel free to submit issues and enhancement requests.
+
+Contributing
+------------
+Please refer to each project's style guidelines and guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow.
+
+ 1. **Fork** the repo on GitHub
+ 2. **Clone** the project to your own machine
+ 3. **Commit** changes to your own branch
+ 4. **Push** your work back up to your fork
+ 5. Submit a **Pull request** so that we can review your changes
+
+NOTE: Be sure to merge the latest from "upstream" before making a pull request!
+
+Copyright and Licensing
+-----------------------
+Most Esri open source projects are licensed under the Apache 2.0 license.
+
+Esri does not require you to assign the copyright of your contributions, you retain the copyright. Esri does require that you make your contributions available under the Apache license in order to be included in the main repo.
+
+If appropriate, include the Apache 2.0 license summary at the top of each file along with the copyright info. If you are adding a new file that you wrote, include your name in the copyright notice in the license summary at the top of the file.
+
+Contributing code written by others
+-----------------------------------
+Please do not contribute code you did not write yourself, unless you are certain you have the legal ability to do so. Also ensure all code contributed can be licensed under the Apache License 2.0.
+
+Copyright 2017 by Esri
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.