Code = Conversation

How do I become a better user of Free/Libre/Open Source Software? Here’s my list:

• When looking for Open Source or Free software to use, remember to first look for good projects, then for good products. With FLOSS I have the option of becoming a contributor – even if it seems unlikely I will right now, I may become one sometime in the future. I know this because my requirements for the software will most likely change as I get comfortable with it – and when this happens, I’ll be glad that I chose a project that will support me as I get to explore it’s details, or support the people I hire so they can improve on the product on my behalf.
• Consider the license! If I in some way intend to add value to the product in order to sell it, go for products with a BSD-like license. Otherwise stick to licenses that force other people’s (and my own!) contributions to stay free for all and anyone to scrutinize and improve. The GNU General Public License is the most used one in this regard.
• Get a feeling of the type and amount of activity. Look for mailing lists, web bulletin boards, bug trackers and newsgroups, and try to lurk around for a while to get an impression. In a FLOSS project it’s evolution of the code that matters most. Not the code itself, not the people working on it, not marketing or managerial matters. See if the project has good code, people, marketing and management – but if one of these seem to hurt the project’s prospects, find out how the project lead(s) solve the problem so that the project can continue thriving. Also take into consideration the type of project you’re looking for. Are you trying to solve an open problem (the kind which never is “done”), then you should expect the activity to be bustling. With projects trying to solve closed problems, you shouldn’t be too disparaged by low amounts of chatter on the forums.
• Look for inclusive but code-centric leadership. What do the contributors do to attract talented people? How is the tone and atmosphere in the different fora? How much of the discussion is solution-, system-, feature-, wishlist- or people-oriented? Is the project open and welcoming to novices and new contributors? How often do discussions reach a satisfactory conclusion?

A project should at presumably make use of the following infrastructure and characteristics in order to support good communication:

• One or more open forums (with searchable archives) where you can join the discussion, ask for support etc.
• A standard way of retrieving the latest bleeding edge version from a revision control system (e.g. SVN or CVS) so you can check for yourself what’s going on in the project.
• A bug- and issue tracker that is in active use.
• A website describing the product, with documentation, download links and other collaborations tools (a wiki for example).
• Responsive project participants, and a good and friendly tone wherever the software is being dicussed.

If the project seems promising but lacks some of the infrastructure, then try to find out if the contributors are working on aquiring the missing tools.