Thank you for your interest in contributing to the Syncfusion Toolkit for Blazor! In this document, we'll outline what you need to know about contributing and how to get started.
First and foremost: if you are thinking about contributing a bigger change or feature, please open an issue or talk to a core team member first! By doing this, we can coordinate and see if the change you are going to work on is something that aligns with our current priorities and is something we can commit to reviewing and merging within a reasonable time. We would want to prevent you from investing a lot of your valuable time in something that might not be in line with what we want for the toolkit.
Please see our Code of Conduct.
Currently, we are in the beginning phases of building up the Syncfusion Toolkit for Blazor. Yet, we are still very excited for you to join us during this exciting time!
Have a look at our Development Guide to learn about setting up your development environment.
If you're looking for something to work on, please browse our backlog. Any issue that is not already assigned is up for grabs.
Please adhere to the coding standards outlined by the .NET Foundation. Additionally, review and follow the guidelines specified in our pull request template when submitting changes.
Please refer to our pull request template.
Please check the "Allow edits from maintainers" checkbox on your pull request. This allows us to make minor fixes and resolve conflicts for you quickly.
To propose a change or new feature, open an issue using the feature request template. You may also use the spec template if you have an idea of what the API should look like. Be sure to also browse current issues that may be related.
All pull requests need to be reviewed and tested by at least two members of the Blazor Toolkit team. We do our best to review pull requests in a timely manner, but please be patient! Two reviewers will be assigned and will start the review process as soon as possible. If there are any changes requested, the contributor should make them at their earliest convenience or let the reviewers know that they are unable to make further contributions. If the pull request requires only minor changes, then someone else may pick it up and finish it. We will do our best to make sure that all credit is retained for contributors.
All PRs should target the main branch.