Gary Sherman posted a great article about the traditional gap between users and developers.

This occurs in all software, not just open source. Proprietary software companies spend a lot of time and effort translating their paying customers desires into development priorities, and often the true requirements get lost in translation. Developers and users often never get to meet directly or iteratively discuss new features.

One differentiator for open source is that the lines of communication are a lot more direct. We have the unique ability to narrow the divide. In order to take advantage of this opportunity, communication (Gary’s last and most important line), has to be wide open.

Developers need to pay attention to Gary’s guidance, and make sure to accept and encourage user involvement as much as possible. They’re your sanity check, making sure that the project is developing in the best way for all.

For users (like me) the only valid way to have input into a free and open project is to make a contribution. Nothing annoys me more than non-contributing users demanding new features. If the software is useful to you (you’re deriving benefit from it) then contribute.

This doesn’t mean writing code, and it need not be limited to documentation or support. You can evangelise for the project in case studies, articles, or presentations at conferences: the more users you can attract, the more likely the features you want will be added by someone else. You can pay a developer to add new features, or you can choose to use consultants with a history of open source contributions. You can help out with foundations like OSGeo that foster and raise the profile of open source geospatial projects, or by helping to organise a conference like FOSS4G 2007.

I guarantee that if you contribute to an open source geospatial project as a user, your voice will have weight. You will find developers far more willing to implement new features that are important to you. If you contribute frequently and your project is open enough to user involvement, you may even be asked to take a leadership role and participate in the project steering committee. In any case, all of your contributions lead to higher quality software, which in turn benefits you.

-J

P.S. OK, one thing annoys me more than non-contributing users: businesses that use open source software and give nothing back. If you’re leveraging open source software for competitive advantage, spin some of that back to the development community in code or $$$. Something as simple as contributing space, cola, and pizza for a code sprint can make a huge difference.