Section 2.1 The Challenges of Global Community

Any global community will of necessity include participants with different native languages. Large projects usually evolve collaborative subgroups that work on documentation and localization for specific languages, but contributors to code and base documentation need a common language in which they can communicate. In many cases, the common language is English, in part because it is one of the most widely spoken languages today. However, the fact that the reserved keywords and base documentation for many programming languages are in English may also be a critical factor. In Eric S. Raymond’s How to Become a Hacker, Linus Torvalds, the original creator of the Linux kernel, is quoted as saying that it never occurred to him to comment the Linux kernel code in any language other than English, despite the fact that English is his third language.

The fact that our globe spins introduces some interesting challenges: collaborators in India and the USA, for example, will never be able to collaborate in real time during normal business hours – in fact, they’ll hardly be able to collaborate during normal waking hours. Most communities meet face-to-face only once or twice a year, if at all, and the face-to-face meetings usually involve only a small subset of the whole community. These challenges have forced the development of really good asynchronous online communication tools. However, having people in different timezones also has some advantages, making it easier to respond in a variety of threads, follow rapidly-developing security issues, and manage infrastructure 24×7.

Standing out in an ocean of nicknames and e-mail addresses, trusting people you have never met, and accepting criticism from strangers is very difficult. Control freaks, glory-grabbers, bullies, and fear-mongers exist in OSS communities and are poisonous to community-building. Creating and maintaining a fork of a major software project is a significant undertaking that is not usually done except as a last resort, because it divides community attention and requires duplication of resources; however, the simple fact that a fork is possible and the community is essential often provides an effective check on runaway egos.

Knowledge-level can be tied up in ego. When you are new to any community, you are a novice on the culture of that community even if you are an expert in some of the tools and languages used by that community. As you endeavor to become a new member of an open source community, it is good to remember that you are a novice to the culture. Some good advice is to read the contribution guide (if the project has one), read the community discussions such as in relevant discussion forums and in bug reports. If you first try to get a sense of how the community operates before you violate any implicit or explicit rules, you are much more likely to be welcomed in. For example, it could be frustrating to try to maintain code quality with volunteer contributors who are happy to contribute but who have not tried to understand the existing standards (such as formatting, documentation, or tests).