Add issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,24 @@
+---
+name: Report a bug
+about: Create a report about something that is not working properly
+labels: bug
+---
+
+### Describe the bug
+A clear and concise description of what the bug is.
+
+### To reproduce
+<!--
+We ❤ code! Ideally, please point us to a minimalistic repro project hosted in a GitHub repository.
+For a repro project, create a new project and apply the minimum required code to result in the issue you're observing.
+-->
+
+### Exceptions (if any)
+<!-- 
+Include the exception you get when facing this issue.
+-->
+
+### Further technical details
+- ASP.NET Core version.
+- Include the output of `dotnet --info`.
+- The IDE (VS / VS Code/ VS4Mac) you're running on, and its version.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Sponsor the project
+    url: https://github.com/sponsors/kevinchalet
+    about: In recognition of their support, sponsors can get private support and depending on the selected tier, an access to security announcements and patches
+  - name: Ask a question (community support)
+    url: https://stackoverflow.com/questions/ask?tags=openiddict
+    about: Ask a question that will be answered by the OpenIddict community

.github/ISSUE_TEMPLATE/enhancement.md

@@ -0,0 +1,15 @@
+---
+name: Suggest an enhancement
+about: "Suggest an idea for this project. Note: priority will be given to suggestions made by sponsors"
+labels: enhancement
+---
+
+### Is your feature request related to a problem?
+A clear and concise description of what the problem is.
+Example: I am trying to do [...] but [...].
+
+### Describe the solution you'd like
+A clear and concise description of what you want to happen. Include any alternative solutions you've considered.
+
+### Additional context
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,5 @@
+---
+name: Ask a question or request support (sponsors-only)
+about: "Important: only sponsors can ask a question on GitHub. If you're not a sponsor, please post your question on StackOverflow"
+labels: question
+---

README.md

@@ -73,18 +73,22 @@ with an ECDSA certificate/key will always result in a `PlatformNotSupportedExcep
 - **[Creating your own OpenID Connect server with ASOS](https://kevinchalet.com/2016/07/13/creating-your-own-openid-connect-server-with-asos-introduction/)** by [Kévin Chalet](https://github.com/kevinchalet)
 - **[Using OpenIddict to easily add token authentication to your .NET web apps](http://overengineer.net/Using-OpenIddict-to-easily-add-token-authentication-to-your-.NET-web-apps)** by [Josh Comley](https://github.com/joshcomley)
 
+## Security policy
+
+Security issues and bugs should be reported privately by emailing contact@kevinchalet.com.
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+
 ## Support
 
-**Need help or wanna share your thoughts?** Don't hesitate to join us on Gitter or ask your question on StackOverflow:
+If you need support, please make sure you [sponsor the project](https://github.com/sponsors/kevinchalet) before creating a GitHub ticket.
+If you're not a sponsor, you can post your questions on Gitter or StackOverflow:
 
 - **Gitter: [https://gitter.im/openiddict/openiddict-core](https://gitter.im/openiddict/openiddict-core)**
 - **StackOverflow: [https://stackoverflow.com/questions/tagged/openiddict](https://stackoverflow.com/questions/tagged/openiddict)**
 
 ## Nightly builds
 
-If you want to try out the latest features and bug fixes, there is a MyGet feed with nightly builds
-of OpenIddict.
-
+If you want to try out the latest features and bug fixes, there is a MyGet feed with nightly builds of OpenIddict.
 To reference the OpenIddict MyGet feed, **create a `NuGet.config` file** (at the root of your solution):
 
 ```xml

SECURITY.md

@@ -0,0 +1,6 @@
+# Security policy
+
+Security issues and bugs should be reported privately by emailing contact@kevinchalet.com.
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+
+Please do not open GitHub issues for anything you think might have a security implication.