This is a bit corporate (just ignore) but I think there are some good things in it, plus it is a model for a project that has multiple github projects.
One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
The best way to get your bug fixed is to be as detailed as you can be about the problem.
Providing a minimal project with steps to reproduce the problem is ideal.
Here are questions you can answer before you file a bug to make sure you're not missing any important information.
Make sure you can build the code. Familiarize yourself with the project workflow and our coding conventions. If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests.
We only accept PRs to the dev branch.
Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. Here's a list of blog posts that are worth reading before doing a pull request:
This is a bit corporate (just ignore) but I think there are some good things in it, plus it is a model for a project that has multiple github projects.
From https://github.com/IdentityServer/IdentityServer3.EntityFramework/blob/master/CONTRIBUTING.md
How to contribute
One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
General feedback and discussions?
Please start a discussion on the core repo issue tracker.
Bugs and feature requests?
Please log a new issue in the appropriate GitHub repo:
Other discussions
https://gitter.im/IdentityServer/IdentityServer3
Filing issues
The best way to get your bug fixed is to be as detailed as you can be about the problem. Providing a minimal project with steps to reproduce the problem is ideal. Here are questions you can answer before you file a bug to make sure you're not missing any important information.
GitHub supports markdown, so when filing bugs make sure you check the formatting before clicking submit.
Contributing code and content
You will need to sign a Contributor License Agreement before submitting your pull request.
Make sure you can build the code. Familiarize yourself with the project workflow and our coding conventions. If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests.
We only accept PRs to the dev branch.
Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. Here's a list of blog posts that are worth reading before doing a pull request:
Here's a few things you should always do when making changes to the code base:
Commit/Pull Request Format
Tests