Contributing

There are dozens of ways to contribute to Weblate. We welcome any help, be it coding help, graphics design, documentation or sponsorship.

Code and development

Weblate is being developed on GitHub <https://github.com/WeblateOrg/weblate>. You are welcome to fork the code and open pull requests. Patches in any other form are welcome as well.

Coding standard

The code should follow PEP-8 coding guidelines.

It is good idea to check your contributions using pep8, pylint and pyflages. You can execute all checks by script ci/run-lint.

Testsuite

We do write testsuite for our code, so please add testcases for any new functionality and verify that it works. You can see current test results on Travis <https://travis-ci.org/WeblateOrg/weblate> and coverage on Codecov <https://codecov.io/github/WeblateOrg/weblate>.

To run testsuite locally use:

./manage.py test --settings weblate.settings_test

You can also specify individual tests to run:

./manage.py test --settings weblate.settings_test weblate.gitexport

See also

See Testing in Django for more information on running and writing tests for Django.

Reporting issues

Issue tracking

Our issue tracker is hosted at GitHub: <https://github.com/WeblateOrg/weblate/issues>

Feel welcome to report any issues or suggestions to improve Weblate there. In case you have found security issue in Weblate, please consult section below.

Security issues

In order to give the community time to respond and upgrade we strongly urge you report all security issues privately. We’re currently using HackerOne to handle security issues, so you are welcome to report issues directly at <https://hackerone.com/weblate>.

Alternatively you can report them to security@weblate.org, which ends up on HackerOne as well.

If you don’t want to use HackerOne for whatever reason, you can send the report by email to michal@cihar.com. You can choose to encrypt it using his PGP key 9C27B31342B7511D.

Note

We’re heavily depending on third party components for many things. In case you find vulnerability which is affecting those components in general, please report it directly to them.

See following sites for some of these:

Starting with our codebase

If you are looking for some bugs which should be good for starting with our codebase, you can find them labelled with newbie tag:

https://github.com/WeblateOrg/weblate/labels/newbie

Earning money by coding

We’re using Bountysource to fund our development, you can participate on this as well by implementing issues with bounties:

https://github.com/WeblateOrg/weblate/labels/bounty

Translating

Weblate is being translated using Weblate on <https://hosted.weblate.org/>, feel free to join us in effort to make Weblate available in as many world languages as possible.

Funding Weblate development

You can fund further Weblate development on Bountysource. Funds collected there are used to fund free hosting for free software projects and further development of Weblate. Please check the Bountysource page for details such as funding goals and rewards you can get for funding.

Backers who have funded Weblate

List of Weblate supporters from Bountysource:

  • Yashiro Ccs
  • Cheng-Chia Tseng