Merge branch 'release-1.1.0' into main

Author: henrikfroehling

.github/CODEOWNERS

@@ -0,0 +1 @@
+*       @henrikfroehling

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug, library
+assignees: henrikfroehling
+
+---
+
+**GitHub Issues are only used for bug reports and feature requests.**
+
+**If you have a support question, please ask in the official Gitter Chat:** https://gitter.im/Trakt-NET/Lobby
+
+**Please follow these guidelines when creating a new issue:**
+
+**--- Please use this template, and delete everything above this line before submitting your issue ---**
+
+**Describe the bug**
+- Use a **descriptive title** that identifies the issue to be addressed.
+- Specify a **detailed description** of the issue.
+- Specify the **version of Trakt.NET**, in which the bug occurs.
+- Specify the platform only, if the bug is related to a specific platform.
+- Describe the **expected and actual behavior**.
+- Specify any relevant **exception messages** and **stack traces**.
+- Describe the steps on how to reproduce the bug.
+- Subscribe for notifications for the created issue in case there are any follow up questions.

.github/ISSUE_TEMPLATE/Custom.md

@@ -0,0 +1,28 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'feature-request, library, target-branch: develop'
+assignees: henrikfroehling
+
+---
+
+**GitHub Issues are only used for bug reports and feature requests.**
+
+**If you have a support question, please ask in the official Gitter Chat:** https://gitter.im/Trakt-NET/Lobby
+
+**Please follow these guidelines when creating a new issue:**
+
+**--- Please use this template, and delete everything above this line before submitting your issue ---**
+
+**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 about the feature request here.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,7 +1,10 @@
 Trakt.NET is primarily authored by:
 
-* [Henrik Fröhling](https://github.com/henrikfroehling) [(henrik.froehling@gmail.com)](mailto:henrik.froehling@gmail.com)
+* [Henrik Fröhling](https://github.com/henrikfroehling) [(henrik.froehling@gmail.com)](mailto:henrik.froehling@gmail.com)
 
 Contributors include:
 
-* [Romans Pokrovskis](https://github.com/Amoenus) [(romans.pokrovskis@capita.co.uk)](mailto:romans.pokrovskis@capita.co.uk)
+* [Romans Pokrovskis](https://github.com/Amoenus)
+* [MCs88](https://github.com/MCs88)
+* [Arnaud Maichac](https://github.com/arnaudmaichac)
+* [skyfrk](https://github.com/skyfrk)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,46 +1,4 @@
-# Contributor Covenant Code of Conduct
+# 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, gender identity and expression, level of experience, 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 both within project spaces and in public spaces when an individual is representing the project or its community. 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 henrik.froehling@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+This project uses the [.NET Foundation Code of Conduct](https://dotnetfoundation.org/code-of-conduct) to define expected conduct in our community.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project maintainer at henrik.froehling@gmail.com.

AUTHORS.md

@@ -11,55 +11,40 @@ Contributing Guidelines
 
 ---
 
-### **Currently, there are the following limits on submitting pull requests**
-- Contributions must be discussed with the maintainer first by opening an issue, or they will likely be declined.
-- Only contributions against the [develop](https://github.com/henrikfroehling/Trakt.NET/tree/develop)-branch will be accepted. Authors submitting pull requests that target experimental feature branches or the [master](https://github.com/henrikfroehling/Trakt.NET/tree/master)-branch will likely be asked to target their pull request against the develop-branch.
-- Pull requests that do not merge easily with the tip of the develop-branch will be declined. The author will be asked to merge with the tip of the targeted branch and update the pull request.
-- Submissions must meet funtional expectations, including scenarios for which the maintainer does not yet have open source tests. This means you may be asked to fix and resubmit your pull request against a new open test case if it fails one of these tests.
-- Submissions must follow the rules stated in the [Coding Guidelines](https://github.com/henrikfroehling/Trakt.NET/blob/develop/coding_style.md).
-- Contributions must follow the [additional requirements](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#additional-requirements-for-pull-requests).
+### **Getting started**
+1. Create your own fork of the repository
+2. Do the changes in your fork
+   - Create a branch for the change with a descriptive name.
+3. If you like your change, send a pull request
+   - Be sure you have followed the [FAQ](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#faq)
+   - Be sure you have followed the [General Requirements](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#general-requirements)
 
 ---
 
-### **Additional requirements for pull requests**
-- Ensure [cross-platform compatibility](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#cross-platform-compatibility) for new features.
-- New features must have accompanying [unit tests](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#unit-tests) with "good" code coverage.
-- Changes to existing functionality needs to be checked that it does not break any existing [unit tests](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#unit-tests).
+### **Build Requirements**
+- at least Visual Studio 2017 with support for C# 7.2
 
 ---
 
-### **Coding conventions**
-- Use the coding style outlined in the [Coding Guidelines](https://github.com/henrikfroehling/Trakt.NET/blob/develop/coding_style.md).
-- Use plain code to validate arguments at public boundaries. Do not use contracts or magic helpers.
-```csharp
-if (argument == null)
-    throw new ArgumentNullException(nameof(argument), "optional message");
-```
-- Use `Debug.Assert()` for checks not needed in release builds. Always include a "message" string in your assert to identify failure conditions.
+### **FAQ**
+1. **Q: Which branch should I target?**
 
----
+   _A: By default you should target the branch `develop`. If you're working on an issue, usually the issue would have a label "target-branch", which states the branch to target for that specific issue._
+2. **Q: How do I trigger a CI-Build for my pull request?**
 
-### **Getting started**
-1. Create your own fork of the repository
-2. Do the changes in your fork
-   - Create a branch for the change with a descriptive name.
-3. If you like the change:
-   - Be sure you have followed the [Coding Guidelines](https://github.com/henrikfroehling/Trakt.NET/blob/develop/coding_style.md).
-   - Be sure you have followed the [additional requirements](https://github.com/henrikfroehling/Trakt.NET/blob/develop/CONTRIBUTING.md#additional-requirements-for-pull-requests).
-   - Send a pull request
+   _A: To trigger a CI-Build for you Pull Request branch, you should name your branch in the following pattern: `issue/{target-branch-name}/{your-branch-name}`, e.g. `issue/develop/your-branch-name`._
 
 ---
 
-### **Build requirements**
-- at least Visual Studio 2017 with support for C# 7.2
+### **General Requirements**
+- Do not make big surprise pull requests with a lot of changes and without an associating issue.
+  - First, please open an issue to open a discussion, whether your changes do make an actual improvement.
+- Pull requests that do not merge easily with the tip of the develop-branch will be declined. The author will be asked to merge with the tip of the targeted branch and update the pull request.
+- Submissions must follow the rules stated in the [Coding Guidelines](https://github.com/henrikfroehling/Trakt.NET/blob/develop/coding_style.md).
+- New features must have accompanying tests with "good" code coverage.
+- Changes to existing functionality needs to be checked that it does not break any existing unit tests.
 
 ---
 
 ### **Cross-platform compatibility**
 - [Trakt.NET](https://github.com/henrikfroehling/Trakt.NET) is built against .NET Standard 1.1
-
----
-
-### **Unit Tests**
-- all new tests need to be added to the project `Trakt.NET.Tests`
-  - the test framework is XUnit