First off, thank you for considering contributing to this project! Whether it's fixing a bug, improving documentation, or building a new feature, we appreciate your effort. Below is a set of guidelines that will help you make your contributions smoothly and ensure that we can review and integrate them as efficiently as possible.
- Using it in your product or project and providing feedback.
- Use cases, feature requests: Roadmap influence
- Community Support, bug fixes, forum posts: Help to be helped
- Documentation: Everyone needs good docs, Code is a moving targed.
- Testing (Perf, load, security, unit tests, ...)
If you find any bugs or have any feature requests, please open an issue. When reporting issues, try to include as much detail as possible:
- Steps to reproduce the problem.
- The expected behavior.
- What actually happened.
- If it's a bug, include relevant logs, error messages, or screenshots.
- Your environment (e.g., OS, software versions).
If you don't have write access, you'll need to fork the repository first. Here’s the process:
- Go to the main project repository: PAiC-SMSC
- Clone the repository.
- Use the fork-and-clone-smsc-repos.sh script to fork the all the repositories.
To become a contributor with write access to the code, you will need to have demonstrated an understanding of the codebase and testsuite by participating in the design discussions and submitting patches for bugs/enchancements before we will grant developer access.