Open Source vs. Business

Some say that paid services belittle the efforts to facilitate free and open sharing of source code. Can profitable businesses and open source really coexist?

The mid-century saw the kernels of collaborative and open exchange of source code, eventually leading to the birth of the Internet in 1969. This paved the way for a culture of shared knowledge; decades later, the Open Source Initiative continues to argue for the practical benefits of openly shared source code. In 1998, the term "open source" was evangelized by a group of developers attending O'Reilly's Freeware Summit. Developers and leaders of some of the most influential free and open-source projects convened to discuss the confusion surrounding the sometimes synonymous terms open source, free software and freeware. It seemed early on that the public was having trouble understanding that businesses often stood behind open-source projects and that paid services were sometimes necessary. Despite this long history, the confusion surrounding the cohabitation of open source and business remains.

The Business of Open Source

The Business of Open Source

Open Source: Making Success Your Biggest Problem

Open Source: Step Back for Progress

Open Source vs. Business

As the Internet became mainstream in the 1990s, individuals found themselves surfing the Net from their workplace and homes. The Internet quickly became more than a vessel of shared knowledge, it became one of the most lucrative mediums of commercial profit since the television half a century before. Inversely, it also brought the boom of freeware sites, which allowed users to freely download everything from screen savers to office suites. Users eagerly snatched up all the free goodies the Internet offered, and soon people expected to find virtually any kind of software they might need for free. The term freeware continued to snake its way through the common lexicon. The open-source community and its projects gained popularity, but faced a sea of indignant users outraged at having to pay for support or documentation. Users failed to understand why they had to pay for services related to a freely downloaded piece of software, and failed to understand that open source doesn't refer to cost, but to openly, usually freely available source code. Once again, the game of semantics reared its ugly head as the battle between the connotations of free, open and business heated up.

Everyone loves free stuff, and the open-source community certainly advocates the free and open exchange of source code. The biggest issue is the expectation that everything is free. The public seems to have morphed the concept of open-source code with free downloads and extended that expectation to everything related to the project. Leaders of open-source projects are finding themselves constantly defending the necessity to generate resources to support their projects while keeping them truly open source and free of licensing fees. While indisputably vital, there comes a point when volunteer contributors can only take a project so far. A business model has to be applied to provide a firm foundation on which the open-source project can stand. Many open-source projects have turned toward a whole product approach, combining the open-source project with a business that supplies support, training, documentation, certification and a range of other professional services. This generates the revenue needed to keep the project viable, but it brings about a whole new set of issues.

More on Open Source

ABC: An Introduction to Open Source

Free Code for Sale: The New Business of Open Source

The Enterprise Committer: When Your Employee Develops Open-Source Code on the Company Payroll

Those who grasp that open source is about openly sharing source code so that others may build on it and benefit from others' efforts understand that supporting the business is inherently supporting the open-source project itself. In these businesses, developers are paid to maintain code and provide bug fixes, allowing the project to grow, remain strong and maintain stability. It also provides a road map—a planned course of action for growth—to focus and foster communication and collaboration in the community. Organizations benefit from the support, training and documentation paid employees generate, and without these businesses the professional services would not be possible. Again, volunteer contributors can only do so much, and asking members of the project community to take time off from their day jobs to provide free services is asking a lot. Who would, in turn, support them and pay their bills? They are professionals, after all, not pan handlers. An open-source project is certainly dependent on community, but that community needs a support source of its own. Someone—or an army of people—needs to keep the project going strong while they are pursuing their own goals and looking after their own responsibilities. The basis of community is fellowship—a group of people working together for a common interest. It would be a shame if the very people who claim to be supporters of open source were the same ones who cripple their community through greed.

Related:
1 2 Page 1
Page 1 of 2
Get the best of CIO ... delivered. Sign up for our FREE email newsletters!