Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 16 additions & 7 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,20 @@
# Code of Conduct

v1.0.0, February 2019
v1.1.0, September 2025

> Adapted from Esri's [Conference and Community Spaces Code of Conduct](https://www.esri.com/en-us/about/events/code-of-conduct)

## Purpose

At Esri, we believe geography can make the world a better place. In adopting this Community Code of Conduct, we as Esri employees are committed to fostering a welcoming environment for collaboration, creativity, and the free exchange of ideas for developing, maintaining, and using open source GIS software. We aim to empower all participants to actively engage and help build a friendly and safe Esri open source developer community.
At Esri, we believe software can make the world a better place. In adopting this Community Code of Conduct, we as Esri
employees are committed to fostering a welcoming environment for collaboration, creativity, and the free exchange of
ideas for developing, maintaining, and using open source software. We aim to empower all participants to actively engage
and help build a friendly and safe Esri open source developer community.

Whether publicly or privately, and whether in-person or online, we expect all members of this community to interact both professionally and without harassment toward others, regardless of race, color, creed, gender, gender identity, religion, marital status, domestic partner status, genetic information, age, national origin or ancestry, military or veteran status, sexual orientation, or either physical or mental disability.
Whether publicly or privately, and whether in-person or online, we expect all members of this community to interact both
professionally and without harassment toward others, regardless of race, color, creed, gender, gender identity,
religion, marital status, domestic partner status, genetic information, age, national origin or ancestry, military or
veteran status, sexual orientation, or either physical or mental disability.

## Expectations

Expand All @@ -19,7 +25,8 @@ Behavior we encourage:
- Respect personal boundaries and preferences
- Respect all project contributors and maintainers

Inappropriate/unacceptable behavior is anything hurtful that interferes with other people’s experience and participation in our community. This includes:
Inappropriate/unacceptable behavior is anything hurtful that interferes with other people’s experience and participation
in our community. This includes:

- Harassment, aggression, and intimidation
- Slurs
Expand All @@ -34,10 +41,12 @@ Inappropriate/unacceptable behavior is anything hurtful that interferes with oth

## Reporting

Repository maintainers reserve the right to remove offensive content. To report inappropriate behavior, you can also contact [events@esri.com](mailto:events@esri.com).
Repository maintainers reserve the right to remove offensive content. To report inappropriate behavior, you can also
contact [events@esri.com](mailto:events@esri.com).

## Consequences

Violations of this Code of Conduct may result in:
* Disqualification from Esri Events and Conferences
* Being blocked from Esri's [GitHub Organization](https://help.github.com/articles/blocking-a-user-from-your-organization/)
- Disqualification from Esri Events and Conferences
- Being blocked from Esri's
[GitHub Organization](https://help.github.com/articles/blocking-a-user-from-your-organization/)
3 changes: 2 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
Esri welcomes contributions from anyone and everyone. Please see our [guidelines for contributing](https://github.com/esri/contributing).
Esri welcomes contributions from anyone and everyone. Please see our
[guidelines for contributing](https://github.com/esri/contributing).
15 changes: 10 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
Contributing to Esri Open Source Projects
=========================================

Esri welcomes contributions to our [open source projects on Github](http://esri.github.io/). When contributing, please follow the [Esri Community Code of Conduct](CODE_OF_CONDUCT.md).
Esri welcomes contributions to our [open source projects on Github](http://esri.github.io/). When contributing, please
follow the [Esri Community Code of Conduct](CODE_OF_CONDUCT.md).

Issues
------
Expand All @@ -13,7 +14,8 @@ Please use [Esri Support](https://developers.arcgis.com/support/) to report ArcG
Contributing
------------

Please refer to each project's style and contribution guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow.
Please refer to each project's style and contribution 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
Expand All @@ -28,9 +30,12 @@ Copyright and Licensing

Most Esri open source projects are licensed under the [Apache 2.0 license](http://www.apache.org/licenses/LICENSE-2.0).

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 2.0 license in order for it be included in the main repo.
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 2.0 license in order for it 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.
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.

## License Summary

Expand All @@ -52,4 +57,4 @@ See the License for the specific language governing permissions and
limitations under the License.
```

## [FAQ](https://github.com/Esri/contributing/issues?q=label%3Afaq+sort%3Aupdated-desc+is%3Aclosed)
## [FAQ](https://github.com/Esri/contributing/issues?q=label%3Afaq+sort%3Aupdated-desc+is%3Aclosed)
9 changes: 6 additions & 3 deletions README_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@

> An extremely brief elevator pitch type description of your project.

A more freeform, long winded, less terse way to describe your very good project and all the useful things it does and maybe where it does them or how or anything else folks should know _right up front_.
A more freeform, long winded, less terse way to describe your very good project
and all the useful things it does and maybe where it does them or how or
anything else folks should know _right up front_.

![animation](https://raw.githubusercontent.com/jgravois/lrm-esri/master//animation.gif)

Expand All @@ -22,7 +24,8 @@ npm install && npm test

### Contributing

Esri welcomes contributions from anyone and everyone. Please see our [guidelines for contributing](https://github.com/Esri/contributing/blob/master/CONTRIBUTING.md).
Esri welcomes contributions from anyone and everyone. Please see our
[guidelines for contributing](https://github.com/Esri/contributing/blob/master/CONTRIBUTING.md).

### License

Expand All @@ -40,4 +43,4 @@ 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.

A copy of the license is available in the repository's [LICENSE](./LICENSE) file.
A copy of the license is available in the repository's [LICENSE](./LICENSE) file.