Phosh is inherently shaped by it’s contributors and their ideas. There are multiple ways you can contribute and all kinds of contributions are welcome, if unsure where to start or if you get stuck, join us on matrix so we can help out and also improve the documentation.

Here’s some possible ways to contribute:

Source code#

In order to contribute source code changes you open a merge requests in the projects repository . Contributions are usually checked via Continuous Integration which will provide you with some initial feedback.

Translations#

Having Phosh properly translated into different languages lowers the entry barrier for many. Translations are kept as po files within the projects repository. For some projects changes happen via the translation facilities at l10n.gnome.org:

• phosh
• phosh-mobile-settings
• phosh-tour
• squeekboard

For others please provide translations via merge requests in their respective repositories.

Testing#

Testing Phosh components before the release allows us to spot bugs before they reach distributions and more users. Thus any testing prior to a release is very welcome. This can either be a check that a recently closed bug is actually fixed or testing the projects main branch during a release cycle. This is especially useful during each releases feature freeze.

If you’re using a Debian based distribution testing doesn’t require any compilation as you can use our nightly packages.

Also testing open merge request is useful as it ensures the claimed functionality is actually present and nothing else regresses.

Testing is also a good way to ensure your use cases keep working.

Code Review#

Reviewing merge requests helps us to merge changes faster while improving quality at the same time.

Artwork#

Sounds, icons, wallpapers, avatars for Matrix rooms, styles and banners for web pages are some examples where artwork contributions can improve the overall experience and where contributions are welcome.

Bug Reports#

Actionable, descriptive bug reports help us to improve Phosh. Besides filing new issues a good way to contribute is to look at existing bugs, check if they still apply and provide more information like describing the circumstances under which a bug is reproducible (and under which it is not).

Documentation#

Both usage information as well as developer information are happy about e.g. e.g. additional tutorials. If you have additional ideas, get in touch or check the open issues in the webpages repositories.

Financial Support#

Supporting us financially helps us to keep the project alive and move it forward.