Contributing to GnuCash
The GnuCash Project is a volunteer-driven organization and depends on volunteers, such as you, to survive and grow.
A list of the different ways that you can help can be found here: http://gnucash.org/en/contribute.phtml And if that's not enough, look below for more ideas:
Many ideas here are taken from this slashdot comment.
Contents
Testing
Programmers make awful testers. Non programmers seem to be able to break programs in new and mysterious ways. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can't make the programmer see your bug, it won't get fixed! If you find a real reproducable bug, check with GnuCashBugzilla to make sure the developers know about it.
Feedback
Providing feedback on what features are used, and what aren't is important to developers who may spend a lot of time on a feature they think is important instead of a feature that actually is important. From another comment: What this thing needs is some normal human beings using it and saying "you know what, it's NOT acceptable that window A obscures window B and freezes while window B is waiting for input from me." It needs, I am sorry to say, Quicken or MS Money users, who say "It was really easy to do X, Y, and Z, but here, I can't even figure out if it's possible,"
WishList
Similarly, it is important to keep track of wishlists - both those of the official developers, and of users. Since this is a wiki, I (Andy Glew, a user) have taken the liberty of creating such a wishlist here. I hope that this is accepptable or that, if there is already such a wishlist, that you can point me to it.
Money
The GnuCash Project encourages financial contributions in three ways:
- Small donations can go to the GnuCash tip jar to pay for unavoidable expenses of the project, and for projects agreed upon by consensus.
- Sizeable donations go to specific developers to help fullfill feature requests.
- Thanking developers for past work can be done individually, but will not be done through the project.
Documentation! Documentation! Documentation!
Writing documents on how to do things (or why to do things, accounting is a black art to many). Help people out using the program. The article said that the programmers are spending a lot of their time answering questions instead of actually getting on and *doing* the job. Even simple things like "Tips and tricks" are a good start. If users can help other users, then the current programmers can spend more of their time getting new developers up to speed.
Advocacy
You usually get developers because they use software and have an itch to scratch. I'd guess that GnuCash's biggest problem is that programmers don't use the software. Running Tutorials, presentations at local LUGs can be invaluable for getting a larger userbase (and therefore hopefully a larger developer base)
Wiki
Write answers to FAQ's. Wiki'ing is very addictive and fun. And while you're at it, everyone learns! As you probably have noticed, you are looking at such a wiki right now. Simply click on the "Edit".
More
See HelpfulProjects for more ideas for small projects of value, ideal for limited contributors.
