Merge pull request #30 from IGNF/develop

Merge develop into master for a 2.2.0

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve this project
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+### Bug 
+
+#### Describe the bug
+A clear and concise description of what the bug is.
+
+#### Type of use (choose between):
+- [ ] `installation` 
+- [ ] `SQL requests in DB` 
+- [ ] `requests from Road2`
+- [ ] `documentation` 
+
+#### To Reproduce
+Steps to reproduce the behavior:
+
+#### Expected behavior
+A clear and concise description of what you expected to happen.
+
+#### Environment (please complete the following information):
+ - OS: [e.g. Debian]
+ - OS Version: [e.g. 11]
+ - Python version: [e.g. 3.10]
+ - PGRouting procedures commit: [sha]
+
+#### Data:
+Data generated with : [eg. r2gg, other]
+System used : [eg. official docker image of pgrouting-procedures, other]
+
+#### Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+### Feature 
+
+Please, make one issue per asked feature. 
+
+#### Is your feature request related to a problem? Please describe.
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+#### Describe the solution you'd like
+A clear and concise description of what you want to happen.
+
+#### Describe alternatives you've considered
+A clear and concise description of any alternative solutions or features you've considered.
+
+#### Additional context
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,20 @@
+### Need 
+
+Please, make one PR per feature or fix, and describe the reason of it. 
+
+What is appreciated is to link this PR to an existing issue created with a template of this project. 
+
+### Tasks 
+
+- [ ] Code the feature on a new branch created from develop (see next paragraph)
+- [ ] Run tests 
+  - [ ] Inside the docker provided by the project 
+  - [ ] Manually if necessary
+- [ ] Update the documentation 
+  - [ ] changelog.md
+  - [ ] documentation directory 
+- [ ] If possible, rebase your branch from develop
+
+### Code 
+
+Please, describe what has been done to achieve this feature or fix. 

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+
+# 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 by being friendly, patient and careful in used words 
+* Being welcoming, respectful of differing opinions, viewpoints, and experiences in your speech and actions
+* Attempting collaboration before conflict
+* 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
+* Alerting community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential
+
+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, pull requests, discussions 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 community spaces are issues, pull request and discussions of 
+the Github project. 
+Examples of representing our community include using an official e-mail 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
+report.road2@ign.fr or by a report on the Github project. 
+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**: If possible, a private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. This warning could be public otherwise. 
+A public apology may be requested. 
+When written, impacts may be reported and moderated. 
+
+### 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](https://www.contributor-covenant.org/),
+version [2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+Elements were taken from the Django Code of Conduct and the Citizen Code of Conduct. 
+
+