-
Notifications
You must be signed in to change notification settings - Fork 57
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added security and contributing docs and markdown corrections (#214)
- Loading branch information
Showing
4 changed files
with
118 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
# Contributing to SDNS | ||
|
||
First and foremost, thank you for considering contributing to SDNS! It's people like you that make SDNS such a great tool. | ||
|
||
## Getting Started | ||
|
||
* Make sure you have a [GitHub account](https://github.com/signup/free). | ||
* Fork the repository on GitHub. | ||
* Decide if you want to work on an existing issue or if you want to propose a new feature or bug fix. | ||
|
||
## Making Changes | ||
|
||
1. Create a new branch in your fork from the main branch. Name your branch something descriptive. | ||
2. Make the changes in your fork. | ||
3. If you're adding a feature or fixing a bug, please add or modify existing tests if applicable. | ||
4. Run all tests to ensure your changes don't negatively impact existing code. | ||
5. Commit your changes to your branch. Keep commit messages clear and concise, stating what you did and why. | ||
|
||
## Submitting Changes | ||
|
||
1. Push your changes to your fork on GitHub. | ||
2. Open a pull request against the main branch of the original repository. | ||
3. Please ensure your pull request description clearly describes the problem and solution and relates to any issues it addresses. | ||
|
||
## Additional Resources | ||
|
||
* [Issue tracker](https://github.com/semihalev/sdns/issues) | ||
* [General GitHub documentation](https://docs.github.com/) | ||
* [GitHub pull request documentation](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
Only the following version is currently being supported with security updates: | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 1.3.x | :white\_check\_mark: | | ||
| < 1.3 | :x: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
We take security issues seriously. If you discover a security vulnerability in this project, please follow these steps: | ||
|
||
1. **Open an Issue**: Once you've made sure you're on the latest version and the vulnerability still exists, open an issue on our GitHub repository. Describe the vulnerability in detail, including the steps to reproduce if possible. | ||
2. **Discussion**: After you report the vulnerability, we'll engage in a discussion with you on the issue to understand it better and evaluate its impact. | ||
3. **Resolution**: We will address the security issue and release a new version with the necessary patches as soon as possible. | ||
|
||
Your efforts to responsibly disclose your findings are sincerely appreciated and will be acknowledged. |