RDFLib Contributing Guide
Thank you for considering contributing to RDFLib. This project has no formal funding or full-time maintainers, and relies entirely on independent contributors to keep it alive and relevant.
Ways to contribute
Some ways in which you can contribute to RDFLib are:
- Address open issues:
- Fix
expected failure
tests:
- Add additional
expected failure
tests for open issues:
- Add tests for untested code:
- Review pull requests marked with the
label.
- Answer questions on Stack Overflow:
- Convert
unittestbased tests topytestbased tests: - Add, correct or improve docstrings:
- Update the RDFLib Wikipedia entry:
- Update the RDFLib Wikidata entry:
- Participate on Gitter/Matrix chat:
- Participate in GitHub discussions:
- Fix linting failures (see ruff settings in
pyproject.tomland# noqa:directives in the codebase).
Pull Requests
Contributions that involve changes to the RDFLib repository have to be made with pull requests and should follow the RDFLib developers guide.
For changes that add features or affect the public API of RDFLib, it is recommended to first open an issue to discuss the change before starting to work on it. That way you can get feedback on the design of the feature before spending time on it.
Code of Conduct
All contributions to the project should be consistent with the code of conduct adopted by RDFLib.