Add contributing and code of conduct documents. (#50)

* Add contributing document.
Add code of conduct document.
Add Contributing and Code of Conduct sections to README.md file.

* Modify CODE_OF_CONDUCT.md.
Modify CONTRIBUTING.md.

CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,136 @@
+# Contributing
+
+## Contributing to Fruit-Detection
+
+The following is a set of guidelines for contributing to Fruit-Detection project.
+These are mostly guidelines, not rules. Use your best judgment, and feel free to
+propose changes to this document in a pull request.
+
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [CODE OF CONDUCT](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+
+## How to Contribute
+
+
+### Reporting Bugs
+
+#### Before Submitting a Bug Report
+
+1. Determine the repository which should receive the problem.
+2. Search the repository's issues to see if the same or similar problem has
+   been opened. If it has and the issue is still open, then add a comment to
+   the existing issue. Otherwise, create a new issue.
+
+#### How to Submit a Good Bug Report
+
+Create an issue on the repository that is related to your bug, explain the
+problem, and include additional details to help maintainers reproduce the
+problem. Refer to the `Short, Self Contained, Correct (Compilable), Example
+[Guide](http://sscce.org/) as well as the following tips:
+
+* **Use a clear and descriptive title** for the issue to identify the problem.
+* **Describe the exact steps which reproduce the problem** in as many details as possible. When listing steps, don't just say what you did, but explain how you did it.
+* **Provide specific examples to demonstrate the steps.** Include links to files or projects, or copy/pasteable snippets, which you use in those examples.
+* **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
+* **Explain which behavior you expected to see instead and why**.
+* **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem.
+* **If the problem wasn't triggered by a specific action**, describe what you were doing before the problem happened and share more information using the guidelines below.
+
+Provide more context by answering these questions:
+
+* **Did the problem start happening recently** (e.g. after updating to a new version) or was this always a problem?
+* If the problem started happening recently, **can you reproduce the problem in an older version?** What's the most recent version in which the problem doesn't happen?
+* **Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
+
+Include details about your configuration and environment:
+
+* **Which version of Fruit-Detection are you using?**?
+* **What's the name and version of the OS you're using**?
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion,
+including completely new features and minor improvements to existing
+functionality. Following these guidelines helps maintainers and the
+community understand your suggestion and find related suggestions.
+
+Before creating enhancement suggestions, please check [`before-submitting-a-bug-report`](#before-submitting-a-bug-report) as you
+might find out that you don't need to create one. When you are creating an
+enhancement suggestion, please include as many details as possible.
+When filling in the issue form for an enhancement suggestion, include the
+steps that you imagine you would take if the feature you're requesting
+existed.
+
+#### Before Submitting An Enhancement Suggestion
+
+* **Check if you're using the latest software version**. A more recent version may contain your desired feature.
+* **Determine which repository the enhancement should be suggested in**
+* **Perform a** [cursory search](https://github.com/ekumenlabs/fruit_detection/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+
+#### How Do I Submit A (Good) Enhancement Suggestion
+
+Enhancement suggestions are tracked as [GitHub
+issues](https://help.github.com/en/github/managing-your-work-on-github/about-issues).
+After you've determined which repository your enhancement suggestion is related to, create an issue on that repository and provide the following information:
+
+* **Use a clear and descriptive title** for the issue to identify the suggestion.
+* **Provide a step-by-step description of the suggested enhancement** in as many details as possible.
+* **Provide specific examples to demonstrate the steps**. Include copy/pasteable snippets which you use in those examples, as [Markdown code blocks](https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks).
+* **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
+* **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem.
+* **Explain why this enhancement would be useful** to most users and isn't something that can or should be implemented as a separate application.
+* **Specify which version of Fruit-Detection you're using.**
+* **Specify the name and version of the OS you're using.**
+
+### Contributing Code
+
+We follow a development process designed to reduce errors, encourage
+collaboration, and make high quality code. Review the following to
+get acquainted with this development process.
+
+#. **Read the** [reporting_bugs](#reporting-bugs) **and** [suggesting_enhancements](#suggesting-enhancements) **sections first.**
+
+#. **Fork the Fruit-Detection package** you want to contribute to. This will create
+   your own personal copy of the package. All of your development should
+   take place in your fork.
+   - An important thing to do is create a remote pointing to the [upstream remote repository](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork). This way, you can always check for modifications on the original repository and **always** keep your fork repository up to date.
+
+#. **Work out of a new branch**, one that is not
+   a release / main branch. This is a good habit to get in, and will make
+   your life easier.
+
+#. **Write your code.** To remember:
+   - Look at the existing code and try to maintain the existing style and pattern as much as possible
+   - **Always** keep your branch updated with the original repository
+
+#### Process
+
+All Fruit-Detection team members actively:
+
+* **Watch** all Fruit-Detection-related repositories to receive email notifications of new issues / pull requests
+* Provide **feedback** to issues as soon as possible
+* **Review** pull requests as soon as possible
+
+  * Team members can review pull requests already under review or approved
+  * Team members can provide some feedback without doing a full review
+
+Pull requests can be merged when:
+
+* They have at least 1 approval from a member of the core team
+* There are no unresolved comments
+* CI is passing
+* [Developer Certificate of Origin](https://developercertificate.org/)(DCO) check is passing
+
+  * DCO is a declaration of ownership, basically saying that you created the contribution and that it is suitable to be covered under an open source license (not proprietary).
+  * All you have to do is end your commit message with Signed-off-by: Your Full Name <[email protected]>
+  * If your user.name and user.email configurations are set up in git, then you can simply run git commit -s to have your signature automatically appended.
+
+Merging strategy:
+
+* For internal contributions, give the original author some time to hit the merge button themselves / check directly with them if it’s ok to merge.
+* Default to “squash and merge”
+  * Review the pull request title and reword if necessary since this will be part of the commit message.
+  * Make sure the commit message concisely captures the core ideas of the pull request and contains all authors' signatures.

README.md

@@ -248,6 +248,14 @@ ros2 bag play my_rosbag
 docker compose -f docker/docker-compose.yml --profile detection_test build
 ```
 
+# Contributing
+
+Issues or PRs are always welcome! Please refer to [CONTRIBUTING](CONTRIBUTING.md) document.
+
+# Code of Conduct
+
+The free software code of conduct fosters an inclusive, respectful community for contributors by promoting collaboration and mutual respect. For more details, refer to the full document [Code of Conduct](CODE_OF_CONDUCT.md).
+
 # FAQs
 
 1. How do I clean up all the docker resources?