doc: add issues and pull-requests templates

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making 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

.github/CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contribute to `scaleway-sdk-python`
+
+`scaleway-sdk-pythom` is Apache 2.0 licensed and accepts contributions via GitHub.
+This document will cover how to contribute to the project and report issues.
+
+## Topics
+
+- [Reporting Security Issues](#reporting-security-issues)
+- [Reporting Issues](#reporting-issues)
+- [Suggesting feature](#suggesting-feature)
+- [Contributing Code](#contributing-code)
+- [Community Guidelines](#community-guidelines)
+
+## Reporting security issues
+
+Please refer to our [security policy](../SECURITY.md).
+
+## Reporting issues
+
+A great way to contribute to the project is to send a detailed report when you encounter a bug.
+We always appreciate a well-written, thorough bug report, and will thank you for it!
+Before opening a new issue, we appreciate you reviewing open issues to see if there are any similar requests.
+If there is a match, thumbs up the issue with a 👍 and leave a comment if you have additional information.
+
+When reporting an issue, please include the `scaleway-sdk-python` version information
+
+## Suggesting a feature
+
+When requesting a feature, some of the questions we want to answer are:
+
+- What value does this feature bring to end users?
+- How urgent is the need (nice to have feature or need to have)?
+- Does this align with the goals of `scaleway-sdk-python`?
+
+## Contributing code
+
+Before contributing to the code, make sure you have read about the [continuous code deployment](docs/CONTINUOUS_CODE_DEPLOYMENT.md) process we are using on this repo.
+
+### Submit code
+
+To submit code:
+
+- Create a fork of the project
+- Create a topic branch from where you want to base your work (usually master)
+- Add tests to cover contributed code
+- Push your commit(s) to your topic branch on your fork
+- Open a pull request against `scaleway-sdk-python` `main` branch that follows [PR guidelines](#pull-request-guidelines)
+
+The [maintainers](MAINTAINERS.md) of `scaleway-sdk-python` use a "Let's Get This Merged" (LGTM) message in the pull request to note that the commits are ready to merge.
+After one or more maintainer states LGTM, we will merge.
+If you have questions or comments on your code, feel free to correct these in your branch through new commits.
+
+### Pull Request Guidelines
+
+The goal of the following guidelines is to have Pull Requests (PRs) that are fairly easy to review and comprehend, and code that is easy to maintain in the future.
+
+- **Pull Request title should respect [conventional commits](https://www.conventionalcommits.org/en/v1.0.0) specifications** and be clear on what is being changed.
+  The scope is the namespace on which the changes are made or `core` for changes which concern the whole SDK. Examples:
+    - A fix for the InstanceAPI.create_server method will be titled `fix(instance): ...`
+    - A change in authentication handling will be titled fix(core): ...
+    - A new instance feature will be title `feat(instance): ...`
+- **Keep it readable for human reviewers** and prefer a subset of functionality (code) with tests and documentation over delivering them separately
+- **Don't forget commenting code** to help reviewers understand and to keep [our Go Report Card](https://goreportcard.com/report/github.com/scaleway/scaleway-sdk-go) at A+
+- **Notify Work In Progress PRs** by prefixing the title with `[WIP]`
+- **Please, keep us updated.**
+  We will try our best to merge your PR, but please notice that PRs may be closed after 30 days of inactivity.
+
+Your pull request should be rebased against the `main` branch.
+
+Keep in mind only the **pull request title** will be used as commit message as we stash all commits on merge.
+
+## Community guidelines
+
+See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
+
+Thank you for reading through all of this, if you have any question feel free to [reach us](README.md#reach-us)!
+
+## Developer documentation
+
+### Code style
+
+Code formatting and linting are enforced with Ruff
+Our CI checks formatting automatically with Ruff, so please ensure your code passes the same checks locally before submitting.
+
+### Testing
+
+We use pytest for testing.
+All new features and bug fixes should include corresponding tests.
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,56 @@
+---
+name: 🐛 Bug Report
+about: Unexpected or broken behavior of SDK-python 🤔
+labels: bug
+---
+
+<!--- Please keep this note for the community --->
+
+### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
+* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment
+
+<!--- Thank you for keeping this note for the community --->
+
+## Command attempted
+
+<!-- Please provide the minimal Python code that reproduces the issue. -->
+
+```python
+from scaleway_core.client import Client
+from scaleway.instance.v1.types import BootType
+from scaleway.instance.v1.custom_api import InstanceUtilsV1API
+
+client = Client.from_config_file_and_env()
+instance_api = InstanceUtilsV1API(client)
+
+server = instance_api.create_server(
+    commercial_type="DEV1-S",
+    zone="fr-par-1",
+    name="test-server",
+    dynamic_ip_required=False,
+    volumes={},
+    protected=False,
+    boot_type=BootType.LOCAL,
+)
+```
+### Expected Behavior
+
+<!--- What should have happened? --->
+
+### Actual Behavior
+
+<!--- What actually happened? --->
+
+## More info
+
+SDK-Python version: <!-- e.g. 1.32.0 -->
+
+Python version: <!-- e.g. 3.10.0 -->
+
+OS version: <!-- e.g. Ubuntu 22.04 -->
+
+<!--- Add any other context, logs, screenshots, or system outputs about the problem --->
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Scaleway Community
+    url: https://slack.scaleway.com
+    about: GitHub issues in this repository are only intended for bug reports and feature requests. Other issues will be closed. Please ask questions on the Scaleway Community Slack (#sdk-python)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,33 @@
+---
+name: 🚀 Feature request
+about: I have a suggestion (and might want to implement it myself 🙂)!
+labels: enhancement
+---
+
+<!--- Please keep this note for the community --->
+
+### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
+* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment
+
+<!--- Thank you for keeping this note for the community --->
+
+## Description
+
+<!-- Describe the problem, limitation, or missing feature that you think SDK-Python should address. -->
+
+## Proposed Solution
+
+<!-- How do you imagine SDK-Python could expose this functionality? -->
+
+```python
+# Example of a possible API usage
+from scaleway.instance.v1.custom_api import InstanceUtilsV1API
+from scaleway_core.client import Client
+
+client = Client.from_config_file_and_env()
+instance_api = InstanceUtilsV1API(client)
+server = instance_api.new_feature(...)
+```

.github/pull_request_template.md

@@ -0,0 +1,18 @@
+### Community Note
+
+* Please vote on this pull request by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original pull request comment to help the community and maintainers prioritize this request.
+* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request
+
+<!--- Thank you for keeping this note for the community --->
+
+<!--- If your PR fully resolves and should automatically close the linked issue, use Closes. Otherwise, use Relates --->
+Relates OR Closes #0000
+
+Release note for [CHANGELOG](https://github.com/scaleway/scaleway-sdk-python/blob/master/CHANGELOG.md):
+<!--
+If the change is not user facing, just write "NONE" in the release-note block below.
+-->
+
+```release-note
+
+```

CHANGELOG.md

@@ -0,0 +1 @@
+# Changelog

SECURITY.md

@@ -0,0 +1,13 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+At Scaleway we take security seriously. If you have any issue regarding security,
+please notify us by sending an email to [email protected].
+
+Please DO NOT create a GitHub issue.
+
+We will follow up with you promptly with more information and a plan for remediation.
+We currently do not offer a paid security bounty program, but we would love to send some
+Scaleway swag your way along with our deepest gratitude for your assistance in making
+Scaleway a more secure Cloud ecosystem.