From "community" to "commercial" FLOSS: The case of moodle

This is the post-print version of the final published article that is available from the link below. Copyright © 2010 ACM, Inc.This paper documents the evolution of Moodle, an advanced Content Management System, and its transition from a purely volunteer-based project to one driven by commercial interests and stakeholders. The study of its evolution provides evidence of the sustainability of its process: increasing amounts of provided effort by developers correspond to similarly increasing produced outputs to the Moodle system. It is also evident how this OSS system, apart from achieving the transition to a successful multisite, collaborative and community-based OSS project, depends more on its community than its commercial partners

Engaging without over-powering: A case study of a FLOSS project

This is the post-print version of the published chapter. The original publication is available at the link below. Copyright @ 2010 IFIP International Federation for Information Processing.The role of Open Source Software (OSS) in the e-learning business has become more and more fundamental in the last 10 years, as long as corporate and government organizations have developed their educational and training programs based on OSS out-of-the-box tools. This paper qualitatively documents the decision of the largest UK e-learning provider, the Open University, to adopt the Moodle e-learning system, and how it has been successfully deployed in its site after a multi-million investment. A further quantitative study also provides evidence of how a commercial stakeholder has been engaged with, and produced outputs for, the Moodle community. Lessons learned from this experience by the stakeholders include the crucial factors of contributing to the OSS community, and adapting to an evolving technology. It also becomes evident how commercial partners helped this OSS system to achieve the transition from an “average” OSS system to a successful multi-site, collaborative and community-based OSS project

The Mirroring Hypothesis: Theory, Evidence and Exceptions

The mirroring hypothesis predicts that the organizational patterns of a development project (e.g. communication links, geographic collocation, team and firm co-membership) will correspond to the technical patterns of dependency in the system under development. Scholars in a range of disciplines have argued that mirroring is either necessary or a highly desirable feature of development projects, but evidence pertaining to the hypothesis is widely scattered across fields, research sites, and methodologies. In this paper, we formally define the mirroring hypothesis and review 102 empirical studies spanning three levels of organization: within a single firm, across firms, and in open community-based development projects. The hypothesis was supported in 69% of the cases. Support for the hypothesis was strongest in the within-firm sample, less strong in the across-firm sample, and relatively weak in the open collaborative sample. Based on a detailed analysis of the cases in which the mirroring hypothesis was not supported, we introduce the concept of actionable transparency as a means of achieving coordination without mirroring. We present examples from practice and describe the more complex organizational patterns that emerge when actionable transparency allows designers to 'break the mirror.'Modularity, innovation, product and process development, organization design, design structure, organizational structure, organizational ties

Formulating an open source business model requires community segmentation and targeted marketing

From a commercial open source company's point of view, open source is ideally the ultimate in “grass roots" marketing where people learn by word-of-mouth about the project and where they volunteer their time and effort, resulting in a vibrant community that benefits the company in many ways. This enables an open source company to enjoy major advantages that do not normally accrue to proprietary software companies e.g. they do not need to spend resources on traditional marketing activities and furthermore, having this community support can help ensure the longevity of the project and company. While this ideal may apply to a handful of open source projects, where they achieve a large critical mass of a community which lends itself to a natural form of monetization, for the vast majority of open source companies, it is not the case of “build it and they will come”. Instead, most open source companies need to understand who comprises their community so they can formulate a viable business model. In particular, they need to understand that communities are comprised of heterogeneous types of people, each of which have their own interests, motivation, needs and ability to be monetized. Open source companies need to identify the subgroups in their community, decide which ones to deliberately focus on, and choose the best way to leverage them. This is indispensable for determining how best to monetize the interest in their software, ideally without ruffling the community spirit that differentiates their software from proprietary offerings. And this is where “old fashioned” marketing can help. This means understanding your user base and what makes them tick, determining their needs, and formulating products and services that people are willing to pay for. The sooner an open source company understands that it needs to practice traditional marketing techniques such as segmentation and target marketing, the faster they will hit on the business model formula that enables their company to succeed. These techniques need to be adapted for the open source world, which requires the blending of traditional marketing techniques and community relations. The risk of treating one's community in an undifferentiated manner and applying a generic, formulaic business model is that a company will fail to generate significant revenue as well as alienate a community that could abandon them. As a community is perhaps the most distinctive asset of an open source company, losing its community is tantamount to death. If the community is not properly nurtured and leveraged, an open source company's potential will not be realized. This paper aims at describing, through case study research, a generic approach for how commercial open source companies can segment their community to aid in their formulation of a business model and marketing plans to reach their potential. It is for anyone who works in an open source company or project who is trying to determine a viable business model. The paper is structured in three parts: the first part outlines the research question and methodology. The second part proposes a way that an open source company can segment its community. The final part analyzes the Funambol experience, describing how the company segmented its community and created open source programs to nurture and leverage it.

Managing the boundary of an 'open' project

In the past ten years, the boundaries between public and open science and commercial research efforts have become more porous. Scholars have thus more critically examined ways in which these two institutional regimes intersect. Large open source software projects have also attracted commercial collaborators and now struggle to develop code in an open public environment that still protects their communal boundaries. This research applies a dynamic social network approach to understand how one community-managed software project, Debian, developed a membership process. We examine the project's face-to-face social network over a five-year period (1997-2001) to see how changes in the social structure affected the evolution of membership mechanisms and the determination of gatekeepers. While the amount and importance of a contributor's work increased the probability that a contributor would become a gatekeeper, those more central in the social network were more likely to become gatekeepers and influence the membership process. A greater understanding of the mechanisms open projects use to manage their boundaries has critical implications for research and knowledge-producing communities operating in pluralistic, open and distributed environments.open source software; social networks; organizational design; institutional design;

Decoding the "Free/Open Source(F/OSS) Software Puzzle" a survey of theoretical and empirical contributions

F/OSS software has been described by many as a puzzle. In the past five years, it has stimulated the curiosity of scholars in a variety of fields, including economics, law, psychology, anthropology and computer science, so that the number of contributions on the subject has increased exponentially. The purpose of this paper is to provide a sufficiently comprehensive account of these contributions in order to draw some general conclusions on the state of our understanding of the phenomenon and identify directions for future research. The exercise suggests that what is puzzling about F/OSS is not so much the fact that people freely contribute to a good they make available to all, but rather the complexity of its institutional structure and its ability to organizationally evolve over time.F/OSS software, Innovation, Incentives, Governance, Intellectual Property Rights