You'd like to get involved in the moneyGuru project but you're not quite sure where to start or whether your skills are needed or where to start? There is plenty of things to do, for developers and non-developers alike (and every significant contribution, development-related or not, is worthy of being counted and compensated as Fairware). So, if you'd like to get involved in any way with the moneyGuru project, don't hesitate to contact me.

Tasks for non-developers

Documentation! There's never enough of it. You think that the docs could be improved? Don't hesitate to start working on it. You'd like to re-write it in your own language? That would be cool too.

Localization. I speak French and English, so I can manage those two localizations. However, external contributions are needed for other languages. Your language is not supported yet? You're welcome to add it to moneyGuru. moneyGuru already supports your language? It's possible that it has "rotten" a little bit. When new features are added, I can't localize the strings of that new features to all languages, so they appear in english. You're welcome to step in and "refresh" an existing localization.

Thorough bug reporting. Are you experiencing a bug which would require you a lot of time to hunt down? This is also worth Fairware compensations, even if "all you do" is bug reports.

Screencasts and other pretty things. I suck at marketing and my spoken english sounds like crap. Anyone willing to do stuff like screencasts showing off moneyGuru doing its stuff, or other markety kind of thing is welcome.

Tasks for developers

Although moneyGuru is written in Python, Objective-C and a little bit of C, you don't need to know all languages or even to be an expert in any of these languages to make meaningful contributions to moneyGuru. Here are a couple of examples:

Developer documentation. I know this code too well to correctly document it anymore. To me, this code is clear, but I know that to a newcomer, it's not. As a newcomer, you are ideally placed to write developer documentation (It's already started, it's in the "devdocs" folder). Moreover, writing such docs will help you understand the code better, I guess. Any initiative to write/improve devdocs are gladly welcomed.

Debian packaging. The current way I do debian packaging is a hack. If you're knowledgable about how debian works and would like to help me set up an apt server and all that stuff, it would be great! Also, if you're knowledgable about other types of packaging (rpms, etc) and would like to add support for it, that would be welcome too.

Windows packaging. For now, I use a closed source solution for packaging into MSI files. If you're knowledgable about thins kind of stuff and you know of an open source solution (and ideally, a way to keep the auto-update mechanism in place), come on board!

Anything else, really. Got idea? Don't hesitate to add a ticket, or don't hesitate to let me know if you'd like to work on an existing ticket.

In any case, don't hesitate to contact me.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins