January 2014 Download this article as a PDFAbstract

Leveraging open source practices provides value to businesses when entrepreneurs and managers understand how to collaborate effectively in an open source ecosystem. However, the complex mix of different actors and varying barriers to effective collaboration in the ecosystem pose a substantial challenge. How can a business create and capture value if it depends on effective collaboration among these different groups? In this article, we review the published research on open source collaboration and reveal insights that will be beneficial to entrepreneurs and managers. We organize the published research into four streams based upon the following actor groups: i) governance actors, ii) competitors, iii) complementors, and iv) the core community. Then, through induction and synthesis, we identify barriers to collaboration, first by ecosystem and then by actor group. Finally, we offer six recommendations for identifying and overcoming barriers to collaboration in an open source ecosystem.


Collaboration is the act of working with another individual or grouping to create something. It involves working jointly and openly with others. When collaborators bring their own diverse skills and experience – and new perspectives – the potential for innovation is great. However, collaboration is far from easy, and the diversity that brings benefits to the experience can also present barriers to collaboration. In an open source ecosystem, where collaboration is essential and the diversity of contributors is often high, these barriers can be substantial.

Open source collaboration is the act of working with different group of actors on a project to produce and create open source software (Nan and Kumar, 2013). For companies that wish to leverage open source software as part of their business models, effective collaboration is essential. However, the open environment introduces business- and people-related issues that can restrict or prevent open collaboration among the different groups of actors. Entrepreneurs and managers are faced with questions such as: How open should an actor be with sensitive or confidential business information, and with whom can it safely be shared? How can we collaborate openly with a competitor? How do we collaborate with actors from around the world, where cultural differences may affect our interactions? These business- and people- related issues inherent in an open source ecosystem create barriers to effective collaboration if entrepreneurs and managers fail to understand and overcome the barriers.

In this article, we examine the barriers to effective collaboration in an open source ecosystem, and we ask whether the different groups of actors in such an ecosystem face the same or different barriers. To successfully collaborate in an open source ecosystem, entrepreneurs and managers must understand: i) the degree of similarity or dissimilarity between barriers to collaboration in such an ecosystem and ii) how the barriers relate to the different groups of actors.

In the existing literature, previous research has focused on specific actors in open source ecosystems, such as: foundations, communities, governments, complementors, competitors, leaders, developers, adapters, users, and expert users. However, there is a lack of research from the broader perspective of the collaboration barriers that may arise within and between these various groups of actors. To achieve business success through leveraging an open source ecosystem, entrepreneurs and managers need to:

  1. Identify and understand barriers to collaboration common to all groups of actors in an open source ecosystem
  2. Identify and understand barriers to collaboration unique to specific groups of actors in an open source ecosystem
  3. Overcome all these barriers for overall effective collaboration in an open source ecosystem

In this article, we make five contributions. First, we identify barriers to collaboration common to all groups of actors in an open source ecosystem. Second, we categorize actors in an open source ecosystem into four different groups. Third, we identify open source collaboration barriers unique to the different groups. Fourth, we assemble the research articles relevant to the topic of collaboration in open source ecosystems into four streams based upon our four different groups of actors. Finally, we provide recommendations to entrepreneurs and managers to identify and overcome barriers to collaboration from a different group of actor perspective.

The article is organized into four sections. The first section summarizes the results of our literature review concerning open source collaboration. The second section provides a definition of open source collaboration as it relates to open source business and an open source ecosystem. This section also identifies open source collaboration barriers common in the ecosystem and unique to the four different groups of actors. The third section provides recommendations for entrepreneurs and managers to overcome collaboration barriers in an open source ecosystem. A final section concludes the article.

Literature Review

Table 1 summarizes the 15 papers we reviewed following a search of literature relating to open source collaboration. Based on patterns we observed, we organized the literature into four streams based on the relevance to four groups of actors in an open source ecosystem: i) governance actors, ii) competitors, iii) complementors, and iv) the core community. Organizing the literature in this way revealed insights into the common barriers in an open source ecosystem and the barriers that are unique to each group of actor.


Table 1. A summary of of open source collaboration literature relevant to open source ecosystems

<Open Table 1 as a PDF>


1. Governance actors

Five of the articles we reviewed in Table 1 relate collaboration with governance actors. Lack of governance can be an overall barrier (Muegge, 2011), but one of the main barriers is the disparate interests or divergent interests between actors in the ecosystem (O’Mahony and Bechky, 2008). Other relevant barriers include the lack of vision and standards relating to the joint efforts in the ecosystem (Kshetri and Schiopu, 2007; Skerrett, 2009). A lack of openness and transparency (Smith and Milinkovich, 2007) can also be a barrier that restricts collaboration in an open source ecosystem. Governance actors manage different interests, solidify and converge interests, and overall reduce business differences between actors in an open source ecosystem (O’Mahony and Bechky, 2008). Openness and transparency (Skerrett, 2009) are also required for access to shared resources and gaining commitment from the actors (Smith and Milinkovich, 2007). Collaboration with governance actors is a process of compromise to establish an ecosystem structure that enables business activities (O’Mahony and Bechky, 2008). A vision and standards are required for international collaboration (Kshetri and Schiopu, 2008); they enable the actors in an open source ecosystem to create value and collaborate.

2. Competitors

Three articles summarized in Table 1 relate to open source collaboration with competitors. Barriers to overcome when collaborating with competitors include a lack of trust, the need to identify shared objectives, and the need to share access to resources in contrast to a closed approach where a company looks to assimilate key resources into its business (Shamsuzzoha et al., 2013). Other barriers include concerns related to releasing confidential information (Lindman and Rajala, 2012); removing restrictions that prevent open collaboration with competitors (Schreaders et al., 2011); and the need to attract and build a larger community of competitors that may be leveraged (Schreuders et al., 2011).

3. Complementors

Two articles summarized in Table 1 relate to collaboration with complementors. Barriers include intellectual property in the form of a right that prevents use and collaboration as well as an inability to share confidential information, lack of trust, moving from closed to open, vendor dominance, and trust (Skerrett, 2011) and lack of transparency (Muegge, 2013).

4. Core Community

Eight articles summarized in Table 1 relate to collaboration with the core community (i.e., users, adopters, contributors, leaders, developers and expert users). Barriers to overcome when collaborating with the core community include:

  • a lack of leadership; leaders are not appointed but evolve out of the community, and there may be cultural differences in leadership (Sarker et al., 2009). Collaboration with the core community requires identification of a leader or leaders of the project to ensure productivity and balance the needs of the actors in the core community
  • the size and format of the community, which affects collaboration as well as the degree of centralization or decentralization (Nan and Kumar, 2013). Going beyond boundaries can be a barrier to productivity (Colazo, 2010)
  • the individual needs of expert users, which may not align with the needs of the community (Hemetsberger and Reinhardt, 2009)
  • the mix of developer attributes, such as the amount of skill or a lack of skill. In addition, a developer's role and responsibilities, which tend to be undefined in an open source ecosystem, (Evans and Wolf, 2005) also create barriers to effective collaboration.

Open Source Barriers to Collaboration

Open source business shifts “the focus from the production value to the use value of the software artifact and emphasizes services and meta-services surrounding the artifact” (Feller et al., 2006). The open source ecosystem includes a number of different actors involved in the artifact and the services to provide a complete solution to customers. The ecosystem has little organization and order. The ecosystem may further include a platform where actors interact to create products or offer services. The platform offers value to the actors in the ecosystem but the platform also brings together many different technology, people and business relates issues (Kilamo et al., 2012). The actors are motivated by common interests or business models (Manikas and Hansen, 2013). Common interests include a motivation to join the ecosystem where there is overlap in business and the actors work collectively towards a common task, asset, or resource. A business model is also a motivation where the business model in part relies on a non-differentiating common task, asset, or resource.

As we identified earlier, the collection of actors includes four main groups: i) governance actors, ii) competitors, iii) complementors, and iv) the core community. Governance actors are important and manage the boundaries of collaboration (O’Mahony and Bechky, 2008), which are essential to the operation of an open source ecosystem. The type of governance actor varies with the open source ecosystem and may include a foundation (O’Mahony and Bechky, 2008; Skerrett, 2009; Smith and Milinkovich, 2007), a federal government (Kshetri and Schiopu, 2007), or the community (O’Mahony and Bechky, 2008). The core community comprises the actors in the open source ecosystem that work on the open source project to develop and test the product (Kilamo et al., 2012). Actors in the core community include: leaders (Sarker et al., 2009), developers (Nan and Kumar, 2013; Colazo, 2010), users (Muegge, 2013), adopters (Skerrett, 2011; Muegge, 2011) and expert users (Hemetsberger and Reinhardt, 2009). Leaders provide overall leadership to the development portion of the community. Developers work on the open source project creating and testing the software. Users are important for providing requirements. Adopters are key to using the open source project. Expert users provide insight into the project for both present and future needs.

Governance actors resolve differences in the community to ensure the health of the ecosystem (Smith and Milinkovich, 2007). Resolving differences involves collaboration with all other groups. Competitors create and share value while collaborating with the core community, complementors, and other competitors. Complementors help build a larger community that can be leveraged to create and share value (Skerrett, 2011); they collaborate with the core community as well as competitors and other complementors. The core community includes actors such as leaders, developers, and expert users and the associated collaboration barriers are different within the core community.

Table 2 is a summary of collaboration barriers from the literature pertaining to these four main groups, including the different types of actors within each group. The barriers in this table were identified through a close reading of the articles in the literature review. For example, the barrier relating to lack of project representation, which applies to governance actors, is derived from O’Mahony and Bechky (2008): "Though project members were not eager to impose a 'command and control structure onto the community', this desire for 'republics' led the projects to adapt a governance structure that established project representation and preserved pluralistic control.” Similarly, the governance-actor barrier relating to challenges in defining the scope of collaboration is derived from Skerrett (2009): "Determining the scope of collaboration is often the most challenging aspect of starting an open source project. The key challenge is to understand which areas of technology are core and which are non-core to the business value of that organization." Another example is the inequality barrier faced by complementors, which was derived from (Skerrett, 2011): "For single–vendor-dominated communities, copyright assignment was required to allow the receiving vendor the ability to create revenue streams by implementing a dual license for the project code. MySQL is the most common example of this strategy. Unfortunately, this approach creates a revenue stream that is unique to one company. In turn, this inequality creates a barrier to involvement by other companies."

These examples show how the collaboration barriers listed in Table 2 were identified from the literature. Table 3 is a synthesis of the barriers from Table 2 to reveal which barriers are common across the groups and which barriers are unique to each group.

There are four barriers to collaboration that are common to all groups in an open source ecosystem: i) intellectual property, ii) moving from closed to open, iii) openness, and iv) a lack of transparency. The literature shows that trust is important to most groups in the ecosystem with the exception of the governance actors. A particular challenge for competitors and the core community is the diverse mix of people, and the potential for undefined roles and responsibilities. A particular challenge for complementors and the core community is inequality in the ecosystem. The governance actors and the core community tend to have a broad range of different barriers to collaboration.


Table 2. Open source ecosystem actors, sub-groups, and collaboration barriers

<Open Table 2 as a PDF>


Table 3. Barriers to collaboration in an open source ecosystem, by actor group

<Open Table 3 as a PDF>


Recommendations for Entrepreneurs and Managers

We offer six recommendations for entrepreneurs and managers seeking to overcome collaboration barriers for successful collaboration in an open source ecosystem.

1. Identify the common and unique barriers to collaboration in your open source ecosystem

The barriers to collaboration in an open source ecosystem include barriers common to all groups of actors in the ecosystem and barriers unique to specific groups of actors. Entrepreneurs and managers need to seek out, understand, and pay attention to these very different barriers for successful collaboration in an open source ecosystem. The specific nature of a given barrier will depend on the unique circumstances of your ecosystem, but Table 3 can help you systematically identify the types of common and unique barriers to collaboration.

2. Strike a balance between open and closed

Intellectual property that is not differentiating to a business should be released into the open. This requires early and ongoing identification of assets and information that may be open to the ecosystem and other assets and information that should be kept confidential. This includes patents, copyrights, designs and potential inventions. Trademarks and know-how become more valuable and strategic to open source business.

Move quickly and make informed business decisions in the open environment of the ecosystem and be open and transparent with competitors based upon your business decisions when collaborating with any group of actors in an open source ecosystem.

3. Seek representation and effective governance

Understand the collaboration barriers that relate to representation, pluralistic control, economic balance, disparate and divergent interests, ability to cooperate, vision, and standards. Then, ensure your business has a fair share of representation and become proactive with pluralistic control. Identify different interests early and compromise when collaborating with other groups of actors. Setting a clear vision and standards will assist you with effective collaboration with the governance group of actors.

4. Collaborate effectively with the core community

Understand the barriers with the core community that relate to equality, leadership, team structures, cultural differences, and new member integration. Be fair and equitable with the core community. Attempt to identify the leader, or assist developing a leader in the community. Ensure you have an appropriate team structures to assist collaboration with the core community and pay attention to cultural differences associated with a global community, and assist with integrating new members into the community.

5. Compete and collaborate with competitors

Understand the collaboration barriers with competitors that relate to objectives, roles, responsibilities, and shared values. In advance of engaging competitors in the open source ecosystem, ensure you have clear objectives and defined roles, responsibilities, and values. Make a point of understanding your competitor’s objectives, roles, responsibilities, and values. Ensure or negotiate an appropriate understanding of joint roles, responsibilities, and values for collaborating in the open source ecosystem.

6. Recognize the challenges of diversity

Be aware of the diversity in the competitor and core community groups; it can be beneficial, but it also introduces collaboration challenges. Diversity includes different levels of knowledge or education and different levels of skills. There may be actors from many different parts of the world, which creates the potential for cultural barriers to collaboration.


There are many barriers to collaboration in an open source ecosystem. Some of these barriers are common to all actors in the ecosystem, but others are unique to specific groups of actors in the ecosystem. Barriers common to all groups are: intellectual property, business- and people-related issues when moving from a closed system to an open system, understanding where and how to be open in business with other actors in the ecosystem including competitors, and a potential lack of transparency that can impact success. Effective collaboration requires an open approach to all groups in the ecosystem based upon informed business decisions and an understanding of the barriers in an open source ecosystem. Effective collaboration requires that entrepreneurs and managers identify and understand the collaboration barriers both common and unique to each of the four groups of actors in the ecosystem and then overcome these barriers.

Share this article:

Cite this article:

Rate This Content: 
No votes have been cast yet. Have your say!

Keywords: business ecosystem, collaboration, collaboration barriers, communities, competitors, complementors, core community, governance, open source


the article under publication is quite comprehensive .It might have involved lot of efforts and hardwork .Kudos to all of you .Keep it up

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.