-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
28 additions
and
0 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,28 @@ | ||
# How Can I Contribute? | ||
|
||
## Reporting Bugs | ||
|
||
If you find a bug, please check the [issues](../../issues) to see if it’s already been reported. If not, create a new issue and provide: | ||
- A descriptive title. | ||
- Steps to reproduce. | ||
- Expected vs. actual behavior. | ||
|
||
## Suggesting Enhancements | ||
|
||
To suggest improvements or new technologies: | ||
- Open an issue with: | ||
- The technology name. | ||
- Category (What quadrant it belongs in). | ||
- Proposed stage (Adopt, Trial, Assess, Hold). | ||
- Why it’s important for our radar. | ||
|
||
## Submitting Code | ||
|
||
For code contributions: | ||
1. Fork the repo on GitHub | ||
2. Clone the project to your own machine | ||
3. Commit changes to your own branch | ||
4. Push your work back up to your fork | ||
5. Submit a pull request (PR) so your changes can be reviewed | ||
|
||
Be sure to merge with the latest code from "upstream" before making a pull request! |