Contributing and security

You’re welcome here

Rafik grows through people helping one another. Whether you build software, coach, study sport, translate, test, write or simply notice something that could be clearer, your perspective is welcome. You do not need to arrive with a big feature or know the whole codebase.

Small contributions count: improve a sentence, check an Arabic translation, report a confusing step, try a workflow with safe sample data or suggest a useful next improvement. The Rafik repository is the place to explore the code and join in.

A friendly first step

Before changing code, take a look at the project’s contribution guide, requirements and relevant architecture decisions. If you are getting the project running, follow getting started. Start with a focused change and explain what you tried and what you observed.

Not sure where to begin? A clear note about what you wanted to do, what happened and how to reproduce it gives the team a helpful starting point. Use synthetic data for examples.

Code, docs and translations

Keep permission checks and transactions on the server, use forward migrations and regenerate transport types from their source. When behavior or known limits change, update the maintained documentation too. Rafik supports English and Arabic, so please keep translated pages and interface text in step. For this public site, pair English and Arabic routes and translation keys.

Checks and sharing your work

Run the tests and type/build checks relevant to your change. In your pull request, describe what people will be able to do, which checks you ran and any limits you found. Keep changes focused so others can review and build on them. Never commit secrets, production records or test credentials, and preserve the licenses and source notes for any assets you add.

A note about security reports

We appreciate people who help keep Rafik safe. Please follow the project’s security guidance. If private vulnerability reporting is enabled, use GitHub Security → Advisories → Report a vulnerability. Otherwise, publicly ask the maintainers for a private reporting channel without posting exploit details. Please do not send sensitive evidence through the general contact form. Response times are not guaranteed.

Glad you’re here

Thanks for sharing your time and ideas. Your contribution can make Rafik a little easier, clearer or more useful for the next coach, athlete or institution that uses it.

Source and scope

Reviewed against the maintained local university branch on 17 October 2026. CONTRIBUTING.md.