Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.
If you're just looking for help, you'll probably attract the most attention if you post in GIS Stackexchange or GeoNet.
In general, we enforce a fork and pull model for new contributions to this repository. This model applies to both the members of the community at large and for our core contributing team.
If you're new to forking, you can find an excellent resource to get more familiar with the general steps here.
Also, this guide outlines the steps for submitting a pull request.
Feel free to file an issue if you get stuck, we're happy to help!
- Place code in folders according to programming language
- Use lowercase and dashes when creating new folder names
- Create a new folder for each new sample
- Add a readme file describing what the code achieves and how to run it
- Remove framework files and unnecessary files
- Try to keep screenshots under 1MB (~800px) whenever possible
- No
--force
pushing or modifying the Git history in any way - Dedicated feature branches should be used for ongoing work.
- Official GitHub Guides
- Contributing to Open Source projects
- Learning Git
- Twitter Infographic
- App: GitHub Desktop
- App: SourceTree