|
| 1 | +# Contributing to Mathy |
| 2 | + |
| 3 | +Thank you for considering contributing to **Mathy**! We welcome all contributions to make this project better. Here's how you can help: |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## Getting Started |
| 8 | + |
| 9 | +1. **Fork the Repository**: |
| 10 | + |
| 11 | + - Click the "Fork" button on the top-right corner of the repository page. |
| 12 | + |
| 13 | +2. **Clone Your Fork**: |
| 14 | + |
| 15 | + ```bash |
| 16 | + git clone https://github.com/WebDevCaptain-Lab/oss-npm-package-workshop.git |
| 17 | + cd oss-npm-package-workshop |
| 18 | + ``` |
| 19 | + |
| 20 | +3. **Install Dependencies**: |
| 21 | + |
| 22 | + ```bash |
| 23 | + npm install |
| 24 | + ``` |
| 25 | + |
| 26 | +4. **Run Tests**: |
| 27 | + ```bash |
| 28 | + npm test |
| 29 | + ``` |
| 30 | + |
| 31 | +--- |
| 32 | + |
| 33 | +## How to Contribute |
| 34 | + |
| 35 | +### Reporting Issues |
| 36 | + |
| 37 | + Found a bug or have a suggestion? Open an issue and use the appropriate template. |
| 38 | + |
| 39 | +### Feature Requests |
| 40 | + |
| 41 | + Check the [Roadmap](./ROADMAP.md) to see if your feature aligns with future plans. If not, create an issue to discuss. |
| 42 | + |
| 43 | +### Submitting Pull Requests |
| 44 | + |
| 45 | +- Create a new branch for your work: |
| 46 | + `git checkout -b my-feature` |
| 47 | + |
| 48 | +- Make your changes. Write clear and concise code, and add comments if necessary. |
| 49 | + |
| 50 | +- Ensure tests pass: |
| 51 | + `npm test` |
| 52 | + |
| 53 | +- Push your branch and open a pull request: |
| 54 | + `git push origin my-feature` |
| 55 | + |
| 56 | +- Follow the Pull Request Template to include all required details. |
| 57 | + |
| 58 | +- Code Style |
| 59 | + Prettier and ESLint are used to enforce code style. Run: |
| 60 | + |
| 61 | + - `npm run lint` |
| 62 | + - `npm run format` |
| 63 | + |
| 64 | +- Join the Discussion |
| 65 | + Feel free to ask questions or seek guidance by opening a discussion or issue. Happy coding! |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +### **2. CODE_OF_CONDUCT.md** |
| 70 | + |
| 71 | +Defines behavior expectations for contributors. |
| 72 | + |
| 73 | +```markdown |
| 74 | +# Contributor Code of Conduct |
| 75 | + |
| 76 | +## Our Pledge |
| 77 | + |
| 78 | +We as contributors and maintainers pledge to make participation in this project a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. |
| 79 | + |
| 80 | +## Our Standards |
| 81 | + |
| 82 | +Examples of behavior that contributes to a positive environment: |
| 83 | + |
| 84 | +- Being respectful of differing viewpoints. |
| 85 | +- Providing constructive feedback. |
| 86 | +- Showing empathy toward others. |
| 87 | + |
| 88 | +Examples of unacceptable behavior: |
| 89 | + |
| 90 | +- Use of sexualized language or unwelcome advances. |
| 91 | +- Insulting or derogatory comments. |
| 92 | +- Public or private harassment. |
| 93 | + |
| 94 | +## Enforcement |
| 95 | + |
| 96 | +Instances of unacceptable behavior can be reported by contacting the project team at **[ [email protected]](mailto: [email protected])**. All complaints will be reviewed and addressed confidentially. |
| 97 | + |
| 98 | +## Acknowledgments |
| 99 | + |
| 100 | +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org). |
| 101 | +``` |
0 commit comments