Table of Contents
The Kurento project accepts contributions from third parties in all kinds of forms:
Improvements to the documentation
Improvements to the testability of the code itself
Kurento team members will probably ask for further explanations, tests or validations of any code contributed to the project before it gets incorporated into its codebase. You must be ready to address these concerns before having your code approved for inclusion.
Please mind the following contribution guidelines:
Ensure the bug was not already reported by searching in our Issue Tracker.
If you’re unable to find an open issue addressing the problem, open a new one. Include a title and clear description, as much relevant information as possible, and a code sample or an executable test case that can be used to demonstrate the unexpected behavior.
For more detailed information on submitting a bug report and creating an issue, visit our reporting guidelines.
Open a new GitHub Pull Request with the patch.
Ensure the PR description clearly describes the problem and its solution. Include the relevant Issue number, if applicable.
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Kurento will generally not be accepted.
Before contributing a piece of work, we strongly suggest that you first write about your intentions in the Kurento Public Mailing List, so we can talk about the need and value of your changes.
Specify the contents of your contribution:
What problem is it trying to solve?
What are the consequences of the changes?
Specify the licensing restrictions of the code you contribute.
By having some work contributed for incorporation in the Kurento project, you will be implicitly accepting Kurento to own the code copyright, so that the Open Source nature of the project can be guaranteed.
Remember that the Kurento project has no obligations in relation to accepting contributions from third parties.