Enhance project's community profile

Add a CONTRIBUTING file together with a Code of Conduct and templates
for issues and pull requests.

Author: mattiasw

CODE_OF_CONDUCT.md

@@ -0,0 +1,78 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, nationality,
+personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+*   Using welcoming and inclusive language
+*   Being respectful of differing viewpoints and experiences
+*   Gracefully accepting constructive criticism
+*   Focusing on what is best for the community
+*   Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+*   The use of sexualized language or imagery and unwelcome sexual attention or
+    advances
+*   Trolling, insulting/derogatory comments, and personal or political attacks
+*   Public or private harassment
+*   Publishing others' private information, such as a physical or electronic
+    address, without explicit permission
+*   Other conduct which could reasonably be considered inappropriate in a
+    professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an
+incident. Further details of specific enforcement policies may be posted
+separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+<https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+<https://www.contributor-covenant.org/faq>

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+Contributing to ExifReader
+==========================
+
+If you want to contribute in any way, I'll be very happy to receive that help
+making this project better. There are several ways to contribute and all are
+welcome. You can send in suggestions for better documentation, new
+functionality, or a bug-fix (just create an issue). Or you can create a pull
+request for the thing you want changed or added.
+
+Please note that this project is released with a
+[Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this
+project you agree to abide by its terms.
+
+Creating an issue
+-----------------
+
+I will appreciate everything from pointing out spelling errors to a huge
+functionality suggestion. Just put in enough information for me to understand
+the issue. For reporting bugs specifically, please include the following if
+possible:
+
+-   A description of the issue and how to reproduce according to the issue
+    template.
+-   An example JPEG image where the problem can be seen. This is very valuable.
+
+Creating a pull request
+-----------------------
+
+If the pull request has code changes, they should follow the ESLint rules and be
+covered by unit tests. Running the linter and the tests is easy after
+`npm install` has been run:
+
+```bash
+npm run lint
+npm test
+```
+
+If you need help with writing tests, just ask. I can probably help in one way or
+another.
+
+The commit message should be descriptive and (if needed) have an explanatory
+body. This is one of all the guides out there on how to write good messages:
+[How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/)
+
+In short, here are some guidelines:
+
+-   Write the subject line in imperative mood: `Add IPTC support for records 1
+    and 7`, not `Added...`, `Fixing...`, etc.
+-   Try to not use more than 50 characters in the subject line with 72 as a hard
+    limit (otherwise it will get truncated).
+-   For non-trivial changes, add a body to explain what was changed and why.
+-   Wrap the lines of the body at 72 characters.

ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+### Description
+
+<!-- Describe what you're suggesting, the bug you've found, etc. -->
+
+<!-- If you found a bug, fill in the details below. Otherwise delete it. -->
+
+**How to reproduce**
+
+1.  <!-- First step -->
+2.  <!-- Second step -->
+3.  <!-- And so on -->
+
+**What I expected would happen:**
+
+<!-- The behavior you expected. -->
+
+**What really happened:**
+
+<!-- What you actually saw. -->

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,3 @@
+### Description
+
+<!-- Describe what the change does and why it's needed. If it's related to an issue, link to it. -->

README.md

@@ -124,7 +124,9 @@ directory.
 Tips
 ----
 
--   After parsing the tags, consider deleting the MakerNote tag if you know you will load a lot of files and storing the tags. It can be really large for some manufacturers. See the examples folder to see how you can do that.
+-   After parsing the tags, consider deleting the MakerNote tag if you know you
+    will load a lot of files and storing the tags. It can be really large for
+    some manufacturers. See the examples folder to see how you can do that.
 
 Testing
 -------
@@ -136,11 +138,23 @@ Testing is done with [Mocha](https://mochajs.org/) and
 npm test
 ```
 
-Issues
-------
+Known Issues
+------------
+
+-   The descriptions for UserComment, GPSProcessingMethod and GPSAreaInformation
+    are missing for other encodings than ASCII.
+
+Contributing
+------------
+
+See [CONTRIBUTE.md](CONTRIBUTE.md).
 
--   The descriptions for UserComment, GPSProcessingMethod and GPSAreaInformation are missing for other encodings than ASCII.
+Code of Conduct
+---------------
 
+This project is released with a
+[Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this
+project you agree to abide by its terms.
 
 License
 -------