This community encourages feedback and contributions. Thank you for your interest in making the Q# Community better! There are several ways you can get involved.
Adding a new repository to the community
Are you someone who has a project they want to contribute to the Q# community organization? There are a few main benefits to doing so:
- Make it easier for new contributors to find your project 🎉
- Crowd source maintaining and developing with others familiar with Q#
Steps to add a new project
- Send an email introducing you and your project to firstname.lastname@example.org (with a link to the current repo if possible) for the organization maintainers to review.
- Then at least two maintainers will review the project to make sure it is a good fit. We strive to get feedback on this in a timely manner.
- If the project is a good fit, next is to start a new repo or transfer the ownership of the previous repo to the organization. Any original contributors will be made admin on the repo under the org and if the licence is OSI approved, it can maintain all original licensing.
- 🎊Party!🎉 Now if you like you can write a blog post about your project and we can host/cross-post it to our site here so people can read first hand from you about your project! Also consider publishing your work to Nuget or Myget!
Licencing repositories in the community organization
Each repository when contributed to the organization can decide what OSI approved licence it uses. This is an open source community and the best way to help others learn and continue to build amazing projects is to keep making projects open source. The community generally suggests MIT licence, as most open source .NET projects do the same.
Reporting issues and suggesting new features
If something about one of the community projects is not working properly, please file an issue of the corresponding repository. If you have ideas for new features of the community throw them up on the Gitter and maintainers can then create projects on this repo to track progress and discussions. Remember that all community interactions must abide by the Code of Conduct.
Finding issues you can help with
Looking for something to work on?
good first issue on all community repos are a good place to start.
You can also check the
help wanted tags to find other issues to help with.
If you’re interested in working on a fix, leave a comment to let everyone know and to help avoid duplicated effort from others.
Contributions we accept
We welcome your contributions to Q# community projects especially to fix bugs and to make improvements. Some general guidelines:
- DO follow the Q# style guide, and keep code changes as small as possible.
- DO include corresponding tests whenever possible.
- DO check for additional occurrences of the same problem in other parts of the codebase before submitting your PR.
- DO link the issue you are addressing in the pull request.
- DO write a good description for your pull request. More detail is better. Describe why the change is being made and why you have chosen a particular solution. Describe any manual testing you performed to validate your change.
- DO NOT merge multiple changes into one PR unless they have the same root cause.
Making changes to the code
The Q# language has a style guide, please use this for Q# code projects. For projects that involve other languages, please use consistent styling.
Testing and Packaging
Your change should include tests to verify new functionality wherever possible.
Coming Soon: instructions on how to setup Azure DevOps pipelines for Q# projects
After submitting a pull request, members of the Q# Community team will review your code. We will assign the request to an appropriate reviewer. Any member of the community may participate in the review, but at least one member of the Q# Community team will ultimately approve the request.