By Dave Whitinger, Linux Today.
Evidence shows that the
majority of the public views the Linux community as one solid
entity, with a singular vision, a common goal, and similar
tasks.
They couldn’t be further from the truth. What they fail to
realize is that the Linux community is just like any other large
organization, sub-divided into groups that achieve common goals.
Each group has different goals, different visions, and have
different hopes for end-results.
While the most popular end-result of Linux may be the widespread
acceptance of Linux, on the server and the desktop, we must realize
that many people have differing goals.
- There are those who want to see Open Source Software become the
next generation of software development. - There are those who want to see more competition in the
operating system market, and dis-allow any one company or
individual from controlling the industry. - Some merely want to be able to use an operating system that
works, regardless of the flavor. Linux is an obvious choice. - For some, the reward is the actual process of writing the code.
They enjoy working on the internals of an operating system. - Some may want a purpose in life, and the Linux community
welcomes them with open arms.
These reasons are why Linux exists, continues to exist, and will
continue to exist forever more.
Assuming that every
member of the community is responsible for writing code is
incredibly small-minded. With these differing goals we are trying
to achieve, does it not make sense that we each play different
roles within the community?
Those who enjoy programming, write free software. Those who are
authors at heart write documentation. And so on and so on, until
all of the needs of the Linux community are fulfilled.
Let us examine in closer detail some of the roles in the Linux
community:
- User = They use the software.
- Documentation authors = These people have an understanding of
the software and are talented in recording information in an easy
to understand format. They document the software for a variety of
audiences. - Support = They monitor mailing lists, usenet, and IRC,
answering questions and helping others. - Q.A. = They use and test software. They join mailing lists and
submit detailed bug reports to the developers. - Marketing and Sales: They promote the use of Linux wherever
possible. They may contribute by:- Submitting wishlist items to developers.
- Starting and managing local User Groups.
- Convincing organizations to use Linux.
- Monitoring the mainstream press for Linux mentions and helping
authors write more informed articles about Linux. - Maintaining web pages that advocate Linux in one way or
another. - Monitoring and discussing the political ramifications of
certain moves by the Linux community.
- Developer = He writes code. He understands and enjoys
programming, so he contributes code to the community.
The evolution of these roles is a fairly interesting process to
watch. Everyone enters the Linux community equally – as a user.
They then may opt to move to other areas, such as support,
marketing, and perhaps even developing.
The point of this
article is to attempt to explain the dynamics of the Linux
community, and to help the public understand that the Linux
community is not one huge and static force, but rather a liquid and
flexible series of sub-communities.
We each have our own role. A developer will have a different
function (and hence, different priorities) than a Documentation
writer.
The next time you feel that a fellow member of the community is
getting side tracked with something that appears to be un-related
to Linux, or a waste of time, step back and consider the
possibility that he is fulfilling a role that you are not. When
seeing the situation through his eyes, you may understand the
action he is taking.