How to contribute to rpm.org
Introduction
rpm.org welcomes many different methods of contribution. Here is a list of the most common contribution types and how to get involved.
Contributing Source Code
Our source code is maintained in a git repository. Clones of the repository can be made anonymously. If you have patches, or comments on the code, please discuss them on the rpm mailing lists with the rpm.org development team. If you want to hack on rpm but don't know where to start, here are some possible sources of inspiration:
- Fixing known bugs is always a good way to get started.
- Addressing known limitations and problems of RPM,
Those who have a proven track record of contributions will be granted write access.
Contributing Ideas
RPM is used as one of base tool in several large communities. Help us to identify problems of its daily usage.
Contributing Documentation
The RPM project is always looking for more and better documentation. Some documentation exists in the source code, while other documentation exists within this wiki. To contribute documentation to the source code, see the 'Contributing Sourcecode' section above. To contribute documentation to this wiki, request wiki edit access on rpm-maint@lists.rpm.org mailing list.
Contributing Help
There are various avenues to contribute user and developer help, such as testing and reporting bugs. Please see our communication page for more information.
