@article {385, title = {Differentiating Community from Customers in an F/LOSS Business}, journal = {Open Source Business Resource}, year = {2010}, month = {10/2010}, publisher = {Talent First Network}, type = {Articles}, address = {Ottawa}, abstract = {When software companies using free/libre open source software (F/LOSS) in their product and service offerings attempt to manage the customer pipeline and develop a community, problems may arise. Project communities and customer pipelines are not the same thing, although some participants belong to both groups. This creates confusion in the business and tension with the community. F/LOSS communities have been on the rise for the past two decades. Companies began to form around F/LOSS projects in the early 1990s, with some creating their own F/LOSS projects and some wrapping themselves around existing projects. This has created tension between company managers who are trying to earn profits from software that is "available for free," and from developers in communities that do not necessarily want to create software for someone else{\textquoteright}s corporate gain. This happens regardless of whether the company created the F/LOSS-licensed project itself, or participates in external communities around other projects, or both. This article demonstrates that separating the concepts of community and customer, and of project and product, allows a business to manage clearly both challenges of developing an engaged community and maximizing profits.}, issn = {1913-6102}, url = {http://timreview.ca/article/385}, author = {Matthew Aslett and Stephen Walli} }