@article {Subramaniam:2009:DOS:1480545.1480824,
	title = {Determinants of open source software project success: A longitudinal study},
	journal = {Decis. Support Syst.},
	volume = {46},
	year = {2009},
	month = {January},
	pages = {576{\textendash}585},
	publisher = {Elsevier Science Publishers B. V.},
	address = {Amsterdam, The Netherlands, The Netherlands},
	abstract = {In this paper, we investigate open source software (OSS) success using longitudinal data on OSS projects. We find that restrictive OSS licenses have an adverse impact on OSS success. On further analysis, restrictive OSS license is found to be negatively associated with developer interest, but is positively associated with the interest of non-developer users and project administrators. We also show that developer and non-developer interest in the OSS project and the project activity levels in any time period significantly affect the project success measures in subsequent time period. The implications of our findings for OSS research and practice are discussed. },
	keywords = {contributors, developers, licenses, longitudinal study, Open source project, OSS, project success, restrictive, Software project success},
	issn = {0167-9236},
	doi = {10.1016/j.dss.2008.10.005},
	url = {http://portal.acm.org/citation.cfm?id=1480545.1480824},
	author = {Subramaniam, Chandrasekar and Sen, Ravi and Nelson, Matthew L.}
}
@article {1082,
	title = {Returns from social capital in open source software networks},
	journal = {Journal of Evolutionary Economics},
	volume = {19},
	year = {2009},
	note = {"The data we use in this analysis come from the SourceForge.net Research Data (Department of Computer Science and Engineering, University of Notre Dame)." "Particularly, our dataset is a sub-sample of 2,962 valid observations over twelve months of projects aimed at developing games{\textquoteright} software. To get this sample, we look at the monthly dumps of data and select all projects that belong to the category of GNU Public License (GPL) [6]. "
dependent variable: performance (number of downloads); independent variable: social network ("Here we measure ties among projects through the individuals{\textquoteright} member and contributor roles at projects on the network over time.)},
	month = {4/2009},
	pages = {277 - 295},
	abstract = {Open Source Software projects base their operation on a collaborative structure for knowledge exchange in the form of provision or reception of information, expertise, and feedback on the creation of source code. Here, we address the direction of these knowledge flows among projects throughout social networks and their impact on project success. We identify the roles of membership or contribution that individuals play within projects. We found that connections through contributors who bring their knowledge to the project, improve project success, and that connection through members, who transfer their knowledge towards other projects, enhance project success. Finally, we found that ties through shared membership and contributions hamper project success. The analysis of knowledge flows and their impact on project success imply a translation of returns from investment in social capital, where investment takes the shape of knowledge flows and the returns mean the projects{\textquoteright} diffusion over the network.},
	keywords = {contributors, developers, games, gpl, project success, roles, social capital, social network analysis, social networks, sourceforge, srda, teams},
	issn = {1432-1386},
	doi = {10.1007/s00191-008-0125-5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mendez-DuronGarcia.pdf},
	author = {M{\'e}ndez-Dur{\'o}n, Rebeca and Garc{\'\i}a, Clara E.}
}
@article {1084,
	title = {Dynamics of innovation in an "open source" collaboration environment: lurking, laboring, and launching FLOSS projects on SourceForge},
	journal = {Industrial and Corporate Change},
	volume = {17},
	year = {2008},
	note = {"For the purposes of this study, we are able to draw upon micro-level data pertaining to the activities undertaken during the period between the beginning of September 2000 and December 2002 by the entire cohort of 222,835 individuals who had registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
"The statistical analysis in this article is based upon an edited dataset (referred to here as the SFnetDataset) covering the SourceForge cohort of 222,835 individuals who registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
They appear to be using their own dataset which is from 2000-2001 even though this paper is from 2008},
	month = {07/2008},
	pages = {647 - 710},
	abstract = {A systems analysis perspective is adopted to examine the critical properties of the Free/Libre/Open Source Software (FLOSS) mode of innovation, as reflected on the SourceForge platform (SF.net). This approach re-scales March{\textquoteright}s (1991) framework and applies it to characterize the {\textquotedblleft}innovation system{\textquotedblright} of a {\textquotedblleft}distributed organization{\textquotedblright} of interacting agents in a virtual collaboration environment, rather than to innovation within a firm. March (1991) views the process of innovation at the organizational level as the coupling of sub-processes of exploration and exploitation. Correspondingly, the innovation system of the virtual collaboration environment represented by SF.net is an emergent property of two {\textquotedblleft}coupled{\textquotedblright} processes: one involves the interactions among agents searching the locale for information and knowledge resources to use in designing novel software products (i.e., exploration), and the other involves the mobilization of individuals{\textquoteright} capabilities for application in the software development projects that become established on the platform (i.e., exploitation). The micro-dynamics of this system are studied empirically by constructing transition probability matrices representing the movements of 222,835 SF.net users among seven different activity states, which range from {\textquotedblleft}lurking{\textquotedblright} (not contributing or contributing to projects without becoming a member) to {\textquotedblleft}laboring{\textquotedblright} (joining one or more projects as members), and to {\textquotedblleft}launching{\textquotedblright} (founding one or more projects) within each successive 6-month interval. The estimated probabilities are found to form first-order Markov chains describing ergodic processes. This makes it possible the computation of the equilibrium distribution of agents among the states, thereby suppressing transient effects and revealing persisting patterns of project joining and project launching. The latter show the FLOSS innovation process on SF.net to be highly dissipative: a very large proportion of the registered {\textquotedblleft}developers{\textquotedblright} fail to become even minimally active on the platform. There is nevertheless an active core of mobile project joiners, and a (still smaller) core of project founders who persist in creating new projects. The structure of these groups{\textquoteright} interactions (as displayed within the 3-year period examined) is investigated in detail, and it is shown that it would be sufficient to sustain both the exploration and exploitation phases of the platform{\textquoteright}s global dynamics.},
	keywords = {contributors, core, developers, roles, SFnetDataset, sourceforge, users, virtual communities, virtual organization, virtual organizations},
	issn = {1464-3650},
	doi = {10.1093/icc/dtn026},
	author = {David, P. A. and Rullani, F.}
}
@conference {Alonso:2008:EIV:1370750.1370780,
	title = {Expertise identification and visualization from CVS},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {125{\textendash}128},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As software evolves over time, the identification of expertise becomes an important problem. Component ownership and team awareness of such ownership are signals of solid project. Ownership and ownership awareness are also issues in open-source software (OSS) projects. Indeed, the membership in OSS projects is dynamic with team members arriving and leaving. In large open source projects, specialists who know the system very well are considered experts. How can one identify the experts in a project by mining a particular repository like the source code? Have they gotten help from other people?

We provide an approach using classification of the source code tree as a path to derive the expertise of the committers. Because committers may get help from other people, we also retrieve their contributors. We also provide a visualization that helps to further explore the repository via committers and categories. We present a prototype implementation that describes our research using the Apache HTTP Web server project as a case study.},
	keywords = {apache, classification, committers, components, contributors, expertise, expertise identification, repository, scm, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370780},
	url = {http://doi.acm.org/10.1145/1370750.1370780},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p125-alonso.pdf},
	author = {Alonso, Omar and Premkumar T. Devanbu and Gertz, Michael}
}
@article {Giuri2008305,
	title = {Explaining leadership in virtual teams: The case of open source software},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {Empirical Issues in Open Source Software},
	pages = {305 - 315},
	abstract = {This paper contributes to the open source software (OSS) literature by investigating the likelihood that a participant becomes a project leader. Project leaders are key actors in a virtual community and are crucial to the success of the OSS model. Knowledge of the forces that lead to the emergence of project managers among the multitude of participants is still limited. We aim to fill this gap in the literature by analyzing the association between the roles played by an individual who is registered with a project, and a set of individual-level and project-level characteristics. In line with the theory of occupational choice elaborated by (Lazear, E.P., 2002. Entrepreneurship. NBER Working Paper No. 9109, Cambridge, Mass; Lazear, E.P., 2004. Balanced skills and entrepreneurship, American Economic Review 94, pp. 208-211), we find that OSS project leaders possess diversified skill sets which are needed to select the inputs provided by various participants, motivate contributors, and coordinate their efforts. Specialists, like pure developers, are endowed with more focused skill sets. Moreover, we find that the degree of modularity of the development process is positively associated with the presence of project leaders. That result is consistent with the modern theory of modular production (Baldwin, C.Y., Clark, K.B., 1997. Managing in an age of modularity. Harvard Business Review September-October. pp. 84-93; Mateos-Garcia, J., Steinmueller, W.E., 2003. The Open Source Way of Working: A New Paradigm for the Division of Labour in Software Development? SPRU - Science and Technology Policy Studies. Open Source Movement Research INK Working Paper, No. 1; Aoki, M., 2004. An organizational architecture of T-form: Silicon Valley clustering and its institutional coherence. Industrial and Corporate Change 13, pp. 967-981).},
	keywords = {contributors, Human capital, leadership, roles, sourceforge, team},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.002},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SRW10C-1/2/5ce36096ba3947338962268b54a5a7a9},
	author = {Paola Giuri and Francesco Rullani and Salvatore Torrisi}
}
@article {springerlink:10.1007/s10368-007-0086-4,
	title = {Open source software: Motivation and restrictive licensing},
	journal = {International Economics and Economic Policy},
	volume = {4},
	year = {2007},
	note = {"We employ a unique data set consisting of 71 open source projects hosted at the SourceForge web site. The 71 projects in the sample were chosen (in January 2000)"
"This sample was observed over an 18-month period from January 2002 through the middle of 2003, with data collected at 2-month intervals."
"We are grateful to NERA for providing us with the data."
"Although we only have data on a relatively small sample of the projects hosted SourceForge, the sample is unique because of data on lines of code as well as data on different versions of the program. The latter is a potentially important control variable, since a change in version may necessitate additional lines of code.
Our data set contains information on the size of the open source projects in the form of source lines of code (SLOC). Using SLOC as a performance measure is not always ideal; nevertheless, this performance measure is employed in the profession and the literature.15 For our purposes, SLOC is in fact an ideal measure, because we want to measure the effort that is put into the project, rather than whether a project succeeds."
},
	pages = {209-225},
	publisher = {Springer Berlin / Heidelberg},
	abstract = {Open source software (OSS) is an economic paradox. Development of open source software is often done by unpaid volunteers and the source code is typically freely available. Surveys suggest that status, signaling, and intrinsic motivations play an important role in inducing developers to invest effort. Contribution to an OSS project is rewarded by adding one{\textquoteright}s name to the list of contributors which is publicly observable. Such incentives imply that programmers may have little incentive to contribute beyond the threshold level required for being listed as a contributor. Using a unique data set we empirically examine this hypothesis. We find that the output per contributor in open source projects is much higher when licenses are less restrictive and more commercially oriented. These results indeed suggest a status, signaling, or intrinsic motivation for participation in OSS projects with restrictive licenses.},
	keywords = {contributions, contributors, developers, incentives, license analysis, licenses, lines of code, loc, MOTIVATION, restrictive, scm, size, status, version history},
	issn = {1612-4804},
	url = {http://dx.doi.org/10.1007/s10368-007-0086-4},
	author = {Fershtman, Chaim and Gandal, Neil}
}
@article {90,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06},
	year = {2006},
	abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, "how does one empirically distinguish the core?" Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. 

We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.},
	keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James}
}
@conference {German:2006:SCP:1137983.1138022,
	title = {A study of the contributors of PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {163{\textendash}164},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This report describes some characteristics of the development team of PostgreSQL that were uncovered by analyzing the history of its software artifacts as recorded by the project{\textquoteright}s CVS repository.},
	keywords = {contributions, contributors, cvs, developers, mining challenge, mining software repositories, msr challenge, patches, postgresql, revision history, roles, software evolution, source code, team},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138022},
	url = {http://doi.acm.org/10.1145/1137983.1138022},
	attachments = {https://flosshub.org/sites/flosshub.org/files/163AStudyOf.pdf},
	author = {Daniel M. German}
}
@conference {1090,
	title = {A Topological Analysis of the Open Souce Software Development Community},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2006},
	note = {"We extracted data from a 2003 data dump obtained from SourceForge. "
roles},
	pages = {1-10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {The fast growth of OSS has increased the interest in studying the composition of the OSS community and its collaboration mechanisms. Moreover, the success of a project may be related to the underlying social structure of the OSS development community. In this paper, we perform a quantitative analysis of Open Source Software developers by studying the entire development community at SourceForge [26]. Statistics and social network properties are explored to find collaborations and the effects of different members in the OSS development community. Small world phenomenon and scale free behaviors are found in the SourceForge development network. These topological properties may potentially explain the success and efficiency of OSS development practices. We also infer from our analysis that weakly associated but contributing co-developers and active users may be an important factor in OSS development.},
	keywords = {contributors, developers, roles, social network analysis, social networks, sourceforge, srda, users},
	doi = {10.1109/HICSS.2005.57},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.132.6830\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/xuGao.pdf},
	author = {Jin Xu and Gao, Yongqin and Christley, S. and Madey, G.}
}
@article {1079,
	title = {Are All Open Source Projects Created Equal? Understanding the Sustainability of Open Source Software Development Model},
	journal = {AMCIS 2005 Proceedings},
	number = {435},
	year = {2005},
	note = {uses first 300 most active projects on Sourceforge: {\textquoteright}Our data sample consists of 300 open source software development projects hosted in the Sourceforge.Net. They are the first 300 active projects ranked by Sourceforge.Net....Our dependent variable in the model to measure the success of the projects is the number of downloads. It is an essential variable to show how successful the project is. Generally, more number of downloads means a more successful project. Independent variables include: development status, project lifespan, number of developers, number of messages in the forums, number of mailing list, number of bug report, number of patch report, number of CVS report, number of file releases and also number of news release."},
	abstract = {A very intriguing question in Open Source software (OSS) development is: why there are only a few open source projects succeed, while the majority of projects never do. In this research, we examine the factors that may influence the performance of OSS projects. We particularly focus on the OSS{\textquoteright}s core developers{\textquoteright} role in the project{\textquoteright}s success. Extant research has yet to distinguish core developers and non-core developers from the community at large. The different roles of the core developers and non-core developers in OSS projects{\textquoteright} success still remain unclear. Our research contributes to the literature by separating the core developers from the development forces in general and empirically examining the core developers{\textquoteright} importance. Drawing the evidences from our extensive dataset of 300 open source projects, we demonstrated that core developers{\textquoteright} leadership and project advocation are crucial in determining the fate of the OSS projects. Our research could provide better understanding of OSS sustainability. It could also give practical advice to the OSS community on how to make the project successful.},
	keywords = {contributors, core, developers, downloads, metadata, project success, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LongYuan.pdf},
	author = {Long, J. and Yuan, M.J.}
}
@conference {731,
	title = {Evolution of Volunteer Participation in Libre Software Projects: Evidence from Debian},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	note = {"For each release we have retrieved the corresponding sources.gz file (see below) from the Debian archive. From it we have extracted information about the packages and their maintainers...."
},
	pages = {100-107},
	abstract = {Most libre software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: volunteer contributions are inherently difficult to predict, plan and manage, especially in the case of large projects. In this paper we analyze the evolution in time of the human resources of one of the largest and most complex libre software projects composed primarily of volunteers, the Debian project. Debian currently has around 1300 volunteers working on several tasks: much activity is focused on packaging software applications and libraries, but there is also major work related to the maintenance of the infrastructure needed to sustain the development. We have performed a quantitative investigation of data from almost seven years, studying how volunteer involvement has affected the software...},
	keywords = {contributors, debian, maintainers, PopCon, popularity, Volunteers},
	url = {http://pascal.case.unibz.it/handle/2038/857},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles_barahona_michlmayr-evolution_participation.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Martin Michlmayr}
}
@article {DBLP:journals/tse/Dinh-TrongB05,
	title = {The FreeBSD Project: A Replication Case Study of Open Source Development},
	journal = {IEEE Trans. Software Eng.},
	volume = {31},
	number = {6},
	year = {2005},
	note = {" we obtained the necessary data from the [FreeBsd] CVS repository, the bug report database, and the e-mail archive. The CVS repository contains all of the code and related documentation that is committed to the project from 1993 until the present. The bug report database contains information describing all reported problems, as well as the status (such as fixed, under test, or open) of each problem. Each bug report is called a PR and assigned a reference number. The e-mail archive contains every e-mail message exchanged between the developers since 1994."

d/l: research.cs.queensu.ca/~ahmed/home/teaching/.../F06/.../free-bsd.pdf},
	pages = {481-494},
	abstract = {Case studies can help to validate claims that open source software development produces higher quality software at lower cost than traditional commercial development. One problem inherent in case studies is external validity{\textemdash}we do not know whether or not results from one case study apply to another development project. We gain or lose confidence in case study results when similar case studies are conducted on other projects. This case study of the FreeBSD project, a long-lived open source project, provides further understanding of open source development. The paper details a method for mining repositories and querying project participants to retrieve key process information. The FreeBSD development process is fairly well-defined with proscribed methods for determining developer responsibilities, dealing with enhancements and defects, and managing releases. Compared to the Apache project, FreeBSD uses 1) a smaller set of core developers{\textemdash}developers who control the code base{\textemdash}that implement a smaller percentage of the system, 2) a larger set of top developers to implement 80 percent of the system, and 3) a more well-defined testing process. FreeBSD and Apache have a similar ratio of core developers to people involved in adapting and debugging the system and people who report problems. Both systems have similar defect densities and the developers are also users in both systems.},
	keywords = {apache, bug reports, contributors, core, cvs, defect density, developers, email, email archive, freebsd, mailing list, scm, source code, users},
	doi = {10.1109/TSE.2005.73},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DinhTrungBieman.pdf},
	author = {Trung T. Dinh-Trong and James M. Bieman}
}
@conference {Stewart:2005:PAI:1042438.1043100,
	title = {A Preliminary Analysis of the Influences of Licensing and Organizational Sponsorship on Success in Open Source Projects},
	booktitle = {Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 07},
	series = {HICSS {\textquoteright}05},
	year = {2005},
	note = {"Publicly available data on open source projects registered on the Freshmeat website (www.freshmeat.net) was used to test the hypotheses. Data was collected from each project{\textquoteright}s Freshmeat website at the start and end of an eight month period (March - December 2002)."
"We first selected three project categories from which to draw our sample. These were utilities, software development, and games."
"Within these categories we further differentiated between new projects, which had been registered on the site within the two weeks prior to our first data collection point and older projects that had been registered more than two weeks prior to our initial data collection."
},
	month = {2005},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {This paper develops and tests a model of the impact of	licensing restrictiveness	and	organizational sponsorship on the popularity and vitality of open source software (OSS) development projects. Using data gathered from Freshmeat.net and OSS project home pages the main conclusions derived from the analysis are that organizational sponsorship has a positive effect on project popularity by easing user concerns about cost and quality and that license restrictiveness may have a negative effect on popularity by reducing the perceived utility of open source software. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.},
	keywords = {contributors, developers, freshmeat, license analysis, licensing, metadata, popularity, restrictive, users},
	isbn = {0-7695-2268-8-7},
	doi = {http://dx.doi.org/10.1109/HICSS.2005.38},
	url = {http://dx.doi.org/10.1109/HICSS.2005.38},
	author = {Stewart, Katherine J. and Ammeter, Anthony P. and Maruping, Likoebe M.}
}
@article {capiluppi:23,
	title = {Improving comprehension and cooperation through code structure},
	journal = {IEE Seminar Digests},
	volume = {2004},
	number = {908},
	year = {2004},
	note = {"In this study we measured source code size in three different forms (LOCs, SLOCs, and Kbs of code)."

"Pilot Project: The ARLA System"
},
	pages = {23-28},
	publisher = {IEE},
	abstract = {Defining a relationship between a software system{\textquoteright}s architecture and the process{\textquoteright} efforts is one of the most fascinating questions of software engineering. Apparently, when a system{\textquoteright}s architecture is complex, the process to improve and evolve it will be more difficult. We try to tackle this question from a different point of view: given an open source system, in all the phases of its evolution, we focus on both the aspects of software developers, and the obtained software product. More we observe one of the possible architectures of this system, based on the tree structure derived from source components. First conclusions show that some patterns of tree evolution are recognizable: some branches may appear more promising than other, and are extensively evolved, while other remains in the same status for all the life cycle. More, when the tree structure reaches some status, the process of joining as a core developer seems to forestall. },
	keywords = {arla, code structure, contributors, developers, open source system, scm, software development, software engineering, software process, software product, software system architecture, source code, source components, tree evolution, tree structure},
	doi = {10.1049/ic:20040260},
	url = {http://link.aip.org/link/abstract/IEESEM/v2004/i908/p23/s1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/capiluppi2004.pdf},
	author = {A. Capiluppi}
}
@conference {Ye:2003:TUM:776816.776867,
	title = {Toward an understanding of the motivation Open Source Software developers},
	booktitle = {Proceedings of the 25th International Conference on Software Engineering},
	series = {ICSE {\textquoteright}03},
	year = {2003},
	note = {"Analyzing the emails sent to the mailing fist is one way of understanding the structure of the community."
"Table 2 displays the number of code contributions made by members to the GIMP system and the defined roles of those contributing members. We counted the number of contributions made by each person by analyzing the change log of the system."},
	pages = {419{\textendash}429},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {An Open Source Software (OSS) project is unlikely to be successful unless there is an accompanied community that provides the platform for developers and users to collaborate. Members of such communities are volunteers whose motivation to participate and contribute is of essential importance to the success of OSS projects. In this paper, we aim to create an understanding of what motivates people to participate in OSS communities. We theorize that learning is one of the motivational forces. Our theory is grounded in the learning theory of Legitimate Peripheral Participation, and is supported by analyzing the social structure of OSS communities and the co-evolution between OSS systems and communities. We also discuss practical implications of our theory for creating and maintaining sustainable OSS communities as well as for software engineering research and education.},
	keywords = {change log, COMMUNITY, contributions, contributors, developers, email, email archives, evolution, gimp, log files, mailing list, roles, source code},
	isbn = {0-7695-1877-X},
	url = {http://portal.acm.org/citation.cfm?id=776816.776867},
	attachments = {https://flosshub.org/sites/flosshub.org/files/YeKishida.pdf},
	author = {Ye, Yunwen and Kishida, Kouichi}
}
@article {flosswp40,
	title = {Cave or Community? An Empirical Examination of 100 Mature Open Source Projects},
	journal = {First Monday},
	volume = {7},
	number = {6},
	year = {2002},
	note = {The author conducts an empirical study of the top 100 mature projects on SourceForge.net to develop an understanding of the F/OSS community. The author sought empirical evidence that would help us understand which is more common- the cave (i.e., lone producer) or the community in F/OSS development. Some key findings include: first, most F/OSS programs are developed by individuals, rather than communities. Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project is unrelated to the age of the project.},
	month = {06/2002},
	abstract = {Starting with Eric Raymond{\textquoteright}s groundbreaking work, "The Cathedral and the Bazaar", open-source software (OSS) has commonly been regarded as work produced by a community of developers. Yet, given the nature of software programs, one also hears of developers with no lives that work very hard to achieve great product results. In this paper, I sought empirical evidence that would help us understand which is more common - the cave (i.e., lone producer) or the community. Based on a study of the top 100 mature products on Sourceforge, I find a few surprising things. First, most OSS programs are developed by individuals, rather than communities. The median number of developers in the 100 projects I looked at was 4 and the mode was 1 - numbers much lower than previous numbers reported for highly successful projects! Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project was positively correlated to the age of the project. Fifth, the larger the project, the smaller the percent of project administrators.},
	keywords = {age, contributors, developers, project success, registration, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/krishnamurthy.pdf},
	author = {Sandeep Krishnamurthy}
}
@proceedings {140,
	title = {An exploratory study of ideology and trust in open source development groups},
	year = {2001},
	note = {"To do this, we scanned information in the public domain to develop a preliminary understanding of the context. We then identified 48 OS projects using www.sourceforge.net, an on-line open source meeting place that provides information on open source efforts and hosts code repositories. Projects were selected to represent a variety of types of software, licenses, and group sizes. We contacted administrators or project leaders and asked them to complete open-ended questionnaires regarding their experience and views on open source development."},
	abstract = {Open source (OS) software development has been the subject of heightened interest among organizational scholars because of the novel social coordination practices that signal a departure from traditional proprietary software development. We propose that trust among group members in open source development groups (OSDGs) plays a key role in facilitating their success. Trust is important in this context because of the risk of opportunistic behavior by other members who volunteers may not have met and may never expect to meet, as well as a lack of explicit market contracts or common organizational affiliation. The open source community is differentiated by a coherent ideology that emphasizes a distinct set of interrelated norms, beliefs, and values. These serve to create incentives for open source practices that eschew conventional transactional norms in favor of a gift culture and a focus on reputations. In this study, we primarily examine the role of the shared ideology in enabling the development of affective and cognitive trust in OSDGs. We further examine how this trust leads to desired outcomes - group efficacy and effectiveness. The study is based on exploratory interviews, examination of archival records and a preliminary survey to understand the specific conditions of open source efforts on which this work-in-progress report is based. This is being followed-up by empirical testing of our research model through a survey of a broad variety of OSDGs. This study would contribute to a clarification of the role of trust in enabling software groups to work effectively and help to understand the bases of trust in ideology-permeated groups.},
	keywords = {contributors, groups, ideology, license analysis, licenses, metadata, open source, sourceforge, Survey, team, team size, teams, trust, types},
	doi = {10.1.1.104.638},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.104.638\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewartGosain2001.pdf},
	author = {Katherine Stewart and Gosain, S.}
}
