Open source
Start contributing
A clear path from finding a project to submitting work that maintainers can review. Contributing to OSSGrid itself and contributing to a project indexed on OSSGrid are different paths; both are covered below.
- Step 1
Discover
Choose OSSGrid itself, or browse GSoC and LFX for a project that matches your interests and skills. Read the selected repository’s README and its own contribution guidance before starting.
- Step 2
Choose an issue
Search open issues for documentation, bugs, or good first issue labels. Labels are suggestions, not a promise of easy work. Check that the issue is still relevant and coordinate with its maintainers before starting.
- Step 3
Fork and clone
Use Fork on the repository’s GitHub page, then copy your fork’s clone URL from Code. Run git clone with that URL and enter the project directory. Follow its README to install dependencies. For OSSGrid, run npm ci and npm run dev, then open localhost:3000.
- Step 4
Make changes
Create a branch with git switch -c fix/short-description. Make one focused change, follow the existing code style, and run the project’s checks. Review git diff, stage the relevant files with git add, and use git commit with a message explaining the change.
- Step 5
Submit a pull request
Push your branch to your fork with git push -u origin fix/short-description. Open a pull request to the upstream project’s default branch (main for OSSGrid). Link the issue, explain the result, include test results and UI screenshots, and respond to review feedback.
- Step 6
Get recognized
Accepted or otherwise maintainer-verified contributions to OSSGrid qualify for its contributors directory. If your work is missing, share a link to the accepted contribution with OSSGrid’s maintainers. Contributions to external repositories are recognized by those projects and do not qualify you for the OSSGrid directory.
Good places to begin
The beginner-friendly issue list may be empty; browse other open issues or ask maintainers for a suitable task. For OSSGrid bugs, use the repository’s bug report template. For improvements, explain the user problem and expected behavior in a focused issue or pull request.