Update for v0.8.1

CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+## 0.8.1 2024-06-07
+
+- Update ArcGIS Maps SDK for JavaScript version 4.26
+- add "reactive" functionality to dynamically change attributes
+- add new `ui` attribute
+- add new `minmaxzoom` (map view) and `minmaxalt` (scene view) attributes
+- add new events for `mapLoaded` and `mapLoadError`
+
+## 0.6.2 2023-03-03
+
+- Update demos to latest version
+- Update ArcGIS Maps SDK for JavaScript version 4.26
+- Update dependencies
+
+## 0.2.1 2019-12-15
+
+- Initial release, introduces `esri-map-view` and `esri-scene-view`

CODE_OF_CONDUCT.md

@@ -1,23 +1,21 @@
 # Code of Conduct
 
-v1.0.0, February 2019
-
-> Adapted from Esri's [Conference and Community Spaces Code of Conduct](https://www.esri.com/en-us/about/events/code-of-conduct)
+November, 2023
 
 ## 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.
+We believe open-source can make the world a better place. In adopting this Code of Conduct, we 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 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.
 
 ## Expectations
 
 Behavior we encourage:
 
-- Share your ideas, but also listen to others
-- Be professional, kind, and considerate in technical discussions and disagreements
-- Respect personal boundaries and preferences
-- Respect all project contributors and maintainers
+- Share your ideas, but also listen to others.
+- Be professional, kind, and considerate in technical discussions and disagreements.
+- 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:
 
@@ -32,12 +30,9 @@ Inappropriate/unacceptable behavior is anything hurtful that interferes with oth
 - Offensive email, voicemail messages, or social media postings
 - Personal threats
 
-## Reporting
-
-Repository maintainers reserve the right to remove offensive content. To report inappropriate behavior, you can also contact [[email protected]](mailto:[email protected]).
-
 ## 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 participation in any of our repositories and open-source projects.
+- Being blocked from participation in any of our social media channels.

CONTRIBUTING.md

@@ -1,21 +1,29 @@
 # Contributing
 
-Esri welcomes contributions from anyone and everyone. Please see our [guidelines for contributing](https://github.com/esri/contributing).
+This project welcomes contributions from anyone and everyone. We follow the "fork-and-pull" git workflow:
 
-### Before filing an issue
+ 1. **Fork** this repo on GitHub.
+ 2. **Clone** the project to your own machine.
+ 3. **Checkout a branch** to put your new work on its own branch.
+ 4. **Commit** changes to your branch with a clear and concise message.
+ 5. **Push** your work back up to your fork.
+ 6. Submit a **Pull request** so that we can review your changes.
 
-If something isn't working the way you expected, please take a look at [previously logged issues](https://github.com/Esri/arcgis-rest-js/issues) first.  Have you found a new bug?  Want to request a new feature?  We'd [love](https://github.com/Esri/arcgis-rest-js/issues/new) to hear from you.
+NOTE: Be sure you have the most recent and up to date code. Pull and merge the latest from "upstream" before making a pull request.
 
-If you're looking for help you can also post issues on [GIS Stackexchange](http://gis.stackexchange.com/questions/ask?tags=esri-oss).
+## Before filing an issue
+
+If something isn't working the way you expected, please take a look at [previously logged issues](https://github.com/jf990/esri-map-component/issues) first.  Have you found a new bug?  Want to request a new feature?  We'd [love to hear from you](https://github.com/jf990/esri-map-component/issues/new).
 
 **Please include the following information in your issue:**
-* Browser (or Node.js) version.
-* a snippet of code.
-* any _exact_ error messages or console logs related to the issue.
+
 * an explanation of:
   * what you saw.
   * what you expected to see.
+* a snippet of code.
+* any _exact_ error messages or console logs related to the issue.
+* browser (or Node.js) version.
 
 ### I want to contribute, what should I work on?
 
-Any open issues are fair game. Feature requests are welcome. Even just telling us what you want to see would be extremely helpful!
+Any open issues are fair game. Feature requests are welcome. Even just telling us what you want to see would be considered.