We would love to have your help. Before you start working however, please read and follow this short guide.
Before you open an issue on GitHub, please discuss it on one of our mailing lists and wait for a confirmation from one of the comitters. If you have that permission, please be as precise as possible. Mention the version of Jitsi you are using, your operating system and explain how the problem can be reproduced.
Please note that issues that are reported against a version older than the current stable release will be closed without further investigation.
Please go to our translation website, which is a Pootle instance that allows for easy online translation. Many languages are already there and wait for completion.
If your preferred language is not yet created, please drop us an e-mail. Be aware though that completing a new language will be quite some effort, so be sure you actually want to take up on that work and translate more than a few words.
Please do not create any pull requests for the resources_XX.properties files, they will be overwritten with what comes from Pootle. The only exception is if you find mistakes in the language file for English.
For some more information, e.g. how to translate offline visit the How To Translate Jitsi on our website.
Found a bug and know how to fix it? Great! Please read on.
While Jitsi is released under the LGPL, the copyright holder and principal creator is Blue Jimp. To ensure that we can continue making Jitsi available under an open source license and still pay our bills, we need you to sign our contributor license agreement. If you cannot accept the terms laid out in the agreement, unfortunately, we cannot accept your contribution.
- Please read and follow the code conventions, especially the limit on 80 characters per line.
- Do not reformat existing code.
- Perform one logical change per pull request.
- Maintain a clean list of commits, squash them if necessary.
- Rebase your topic branch on top of the master branch before creating the pull request.