What to Do With 20 Million Users

I got some nice feedback on my recent blog entry about some key items that could be done for the postgresql community if someone would step up and fund them, but [http://www.khankennels.com/blog/index.php/archives/2006/08/10/25-ways-to-help-out-php/ Ligaya Turmelle’s recent post on how to help out PHP] was a good reminder that the onus on growing PostgreSQL isn’t just on the Andy’s of the world, but it is also on all of the PostgreSQL users out there. I don’t think we actually have 20 million users, but for the ones we have, here’s your TODO list on how you can help the PostgreSQL project out: # Get Active (Inside the Community) 1. Submit bug reports. If you don’t know if it is a bug, ask someone. 2. Contribute user comments to the online manual. 3. Join the irc channel and hang out. Get to know other postgresql users and help out when you can. 4. Join one of the mailing lists and help answer questions when you can. 5. Write your own case study about your company # Get Active (Outside the Community) 6. Pick your favorite online forum / community site and help find answers to any postgresql questions. 7. If you use software that doesn’t support PostgreSQL, ask the developers when they plan to add it. 8. Submit patches to that project to add PostgreSQL support if you can. 9. Ask your hosting providor to offer postgresql support if they don’t offer it now. 10. Switch to someone that does offer PostgreSQL support if they don’t. # Get Testin’ 11. PostgreSQL 8.2 is right around the corner, download and install it. Compile from source if you can. 12. Export your current database and import it into 8.2. If you encounter problems, send in a bug report. 13. Run some benchmarks on your current database, then run some benchmarks against 8.2, and share the results. 14. Test every software package you use that supports PostgreSQL against 8.2. # Get Writin’ 15. Pick your two favorite features in PostgreSQL and then write an article about them. If you don’t have a server to host them on, put them into techdocs. 16. Or if you’d rather, write up an article on something coming out in 8.2. There are a lot of features to choose from, and having more information available can only help new users. 17. While you’re at it, don’t forget to read through the manual. If you don’t feel wizbang enough to hack the sgml files, send an email to the docs list or just write a comment on the page about things that you think are confusing or examples that are just plain busted. 18. And if you know a second language, please help with translating articles or documentation so that everyone can get involved. # Get “Foundrying” 19. Propose and write a package and toss it up on the foundry. 20. Volunteer to take over a package that is no longer maintained 21. Check out the bug reports on your favorite package - pick one and fix it. 22. Then submit your patch to the lead developer for inclusion. (If you can’t fix it, just verifying that it is or isn’t a real problem is good too) 23. A lot of packages could use some documentation, write some up and submit it. 24. Translate your favorite foundry project into another language.