Language Selection

English French German Italian Portuguese Spanish

Will the real open source community please stand up?

Filed under
OSS

I recently had an e-mail conversation with an IT pro that knocked me for a loop. Responding to a presentation I did on open source, he said, "It's a great topic, but I would have liked to see a member of the open source community participating."

Whoa! I didn't know that I wasn't a member of the open source community! So I wrote back, saying that I certainly consider myself part of the community. He responded by saying that in his opinion the open source community was confined to those individuals who are open source developers.

That definition sure does limit the size, scope and inclusiveness of the open source community, and I'm wondering if it's a definition shared by many IT professionals.

This exchange got me to thinking about the term "community." It's thrown around a lot. You often hear statements beginning with, "The community believes in …" or "The community won't respect …," without any real identification of who makes up the community.

Over the past few weeks, I have been polling people on what they mean by the term "community."

What's been fascinating is the ambiguity of the responses. Some people identify the community as my correspondent did, including only open source coders. Others include people who contribute other project artifacts, like bug reports, documentation and so on.

Many people have a very inclusive definition that encompasses developers, artifact contributors and the entire user base. It is this latter definition that I find most congenial. In fact, I think a broad definition of community is crucial to the ultimate success of open source.

One of the real strengths of open source is that -- unlike commercial software -- its users have myriad resources to turn to. Open source is no monolithic, take it or leave it, world. It's hard to overstate the power of this aspect of open source. Something about open source brings out mutual effort, which makes using it much, much easier.

So what's wrong in defining the open source community as only a group of developers?

Full Story.

More in Tux Machines

CORD becomes a Linux Foundation project

Central Office Re-architected as a Data Center (CORD), an open source integrated solutions platform for service providers leveraging merchant silicon, white boxes, and open source platforms such as Open Network Operating System (ONOS), OpenStack, Docker, and the cloud operating system XOS, is now part of the Linux Foundation as a new independent project. The Linux foundation is already home to many open source networking projects, including OpenDaylight and ONOS, so CORD is a natural fit for the non-profit foundation. Read more

Google beefs Linux up kernel defenses in Android

Future versions of Android will be more resilient to exploits thanks to developers' efforts to integrate the latest Linux kernel defenses into the operating system. Android's security model relies heavily on the Linux kernel that sits at its core. As such, Android developers have always been interested in adding new security features that are intended to prevent potentially malicious code from reaching the kernel, which is the most privileged area of the operating system. Read more

Fork YOU! Sure, take the code. Then what?

There's an old adage in the open source world – if you don't like it, fork it. This advice, often given in a flippant manner, makes it seem like forking a piece of software is not a big deal. Indeed, forking a small project you find on GitHub is not a big deal. There's even a handy button to make it easy to fork it. Unlike many things in programming though, that interaction model, that simplicity of forking, does not scale. There is no button next to Debian that says Fork it! Thinking that all you need to do to make a project yours is to fork it is a fundamental misunderstanding of what large free/open source projects are – at their hearts, they are communities. One does not simply walk into Debian and fork it. One can, on the other hand, walk out of a project, bring all the other core developers along, and essentially leave the original an empty husk. This is what happened when LibreOffice forked away from the once-mighty OpenOffice; it's what happened when MariaDB split from MySQL; and it's what happened more recently when the core developers behind ownCloud left the company and forked the code to start their own project, Nextcloud. They also, thankfully, dropped the silly lowercase first letter thing. Nextcloud consists of the core developers who built ownCloud, but who were not, and, judging by the very public way this happened, had not been, in control of the direction of the product for some time. Read more

Proprietary and Microsoft Software