So you want to help. Thats great, Flyspray needs your help.


If you want to translate Flyspray into your language or improve existing translations, check out the manuals translation page.

Report bugs

If you’ve found a problem with Flyspray, we want to hear about it. If it’s a very minor thing, it would be better if you quickly let us know on the mailing list. Also use the mailing list for comments about the homepage, or the development cycle, or… anything loosely Flyspray related. If it’s something more major, we would appreciate it if you would file a bug report.

Help us code

If you know PHP, you are welcome to modify Flyspray to suit your needs. If you want to share your modifications, please fork the Flyspray Github repo and issue a pull request. Be prepared to discuss your patch when we ask you about it. When designing your PHP code, follow the current coding style.

And make sure to add yourself to Development Team!

Write documentation

Although we strive to make Flyspray easy to use, it’s always helpful to have documentation available. Unfortunately we don’t always have time to write both the Flyspray code and the user manual, and we prefer to concentrate on the code. All is not lost, as anyone can checkout and edit the User Manual.

We would like users of this page to write in English. No other languages for now, thank you.

Talk to us

Tell us what we’re doing right or wrong! It is very motivating when people take an interest in the project. And make sure to add yourself to Real world users.

Although using Flyspray is free, developing it does cost money. Please consider donating a few dollars via Paypal to help fund development.