There are a few ways that you can help out the wxPython project. If any of these sound like something you can do, or you would like to make a donation, please mail me.
- Library code and patches: Have you developed some classes using wxPython that might be useful to others? Or how about changes to existing code to fix bugs or enhance features? Send them my way and I'll include it in wxPython if I like it. Be sure to take a look at the wxPython Coding Guidelines first.
- Modules: The same goes for additional extension modules. Maybe I'm taking too long to get to adding your favorite feature of wxWidgets to wxPython. Maybe you or somebody else has written some C++ classes using wxWidgets that you'd like to see have wxPython support... It's now easier than ever to add new modules to wxPython. Simply check out wxWidgets CVS, add your code in a subdirectory of .../wxPython/contrib and you're done! (Well, maybe you should build it and test it a couple times too.)
- Financial: If none of the above options are up your alley, please consider making a contribution to the project. Just about everything I get goes to hardware, software, network services, etc. You can contribute using a credit card or e-check at PayPal:
Other payment options can be found here.
Any CEO's out there that want to sponsor wxPython? Just pretend it's a little-league team and you'll have another tax write-off! <grin>
Seriously though, my dream is to find a way to work full-time on developing, supporting and writing about wxPython and still be able to pay the mortgage and put food on the table. Unless I happen to find a 1980 certificate for 10,000 shares of Microsoft buried in the basement I expect I'll have to come up with a creative arrangement with one or more business entities to make this happen...