@proceedings {1915,
	title = {Classifying code comments in Java open-source software systems},
	year = {2017},
	note = {"we conducted an in-depth analysis of the
comments in the source code files of six major OSS systems
in Java"},
	month = {05/2017},
	pages = {227-237},
	abstract = {Code comments are a key software component
containing information about the underlying implementation.
Several studies have shown that code comments enhance the
readability of the code. Nevertheless, not all the comments have
the same goal and target audience. In this paper, we investigate
how six diverse Java OSS projects use code comments, with the
aim of understanding their purpose. Through our analysis, we
produce a taxonomy of source code comments; subsequently, we
investigate how often each category occur by manually classifying
more than 2,000 code comments from the aforementioned
projects. In addition, we conduct an initial evaluation on how
to automatically classify code comments at line level into our
taxonomy using machine learning; initial results are promising
and suggest that an accurate classification is within reach.},
	keywords = {java, Survey},
	author = {Luca Pascarella and Bacchelli, Alberto}
}
@proceedings {1907,
	title = {Do Software Developers Understand Open Source Licenses?},
	year = {2017},
	note = {Data: We report on the results of a survey that asked
developers about 42 different cases of the use of code under
different open source licenses. To make the survey tractable
for developers to answer, we focused on three popular open
source licenses (GNU GPL 3.0, GNU LGPL 3.0 and MPL
2.0)

Findings: The survey results indicate that most of the 375 respondents
to our survey struggle with understanding the interaction of
open source licenses in both simple and complex software
development cases},
	month = {05/2017},
	pages = {1-11},
	abstract = {{\textemdash}Software provided under open source licenses is
widely used, from forming high-profile stand-alone applications
(e.g., Mozilla Firefox) to being embedded in commercial offerings
(e.g., network routers). Despite the high frequency of use of open
source licenses, there has been little work about whether software
developers understand the open source licenses they use. To our
knowledge, only one survey has been conducted, which focused
on which licenses developers choose and when they encounter
problems with licensing open source software. To help fill the
gap of whether or not developers understand the open source
licenses they use, we conducted a survey that posed development
scenarios involving three popular open source licenses (GNU GPL
3.0, GNU LGPL 3.0 and MPL 2.0) both alone and in combination.
The 375 respondents to the survey, who were largely developers,
gave answers consistent with those of a legal expert{\textquoteright}s opinion in
62\% of 42 cases. Although developers clearly understood cases
involving one license, they struggled when multiple licenses were
involved. An analysis of the quantitative and qualitative results of
the study indicate a need for tool support to help guide developers
in understanding this critical information attached to software
components.},
	keywords = {license, Survey},
	doi = {10.1109/ICPC.2017.7},
	author = {Almeida, Daniel A. and Murphy, Gail C. and Wilson, Greg and Hoye, Mike}
}
@article {1920,
	title = {Process Aspects and Social Dynamics of Contemporary Code Review: Insights from Open Source Development and Industrial Practice at Microsoft},
	journal = {IEEE Transactions on Software Engineering},
	volume = {43},
	year = {2017},
	note = {" We sent the survey
to code review participants from 36 popular OSS projects
and received 287 responses"},
	month = {1/2017},
	pages = {56 - 75},
	abstract = {Many open source and commercial developers practice contemporary code review, a lightweight, informal, tool-based code
review process. To better understand this process and its benefits, we gathered information about code review practices via surveys of
open source software developers and developers from Microsoft. The results of our analysis suggest that developers spend
approximately 10-15 percent of their time in code reviews, with the amount of effort increasing with experience. Developers consider
code review important, stating that in addition to finding defects, code reviews offer other benefits, including knowledge sharing,
community building, and maintaining code quality. The quality of the code submitted for review helps reviewers form impressions about
their teammates, which can influence future collaborations. We found a large amount of similarity between the Microsoft and OSS
respondents. One interesting difference is that while OSS respondents view code review as an important method of impression
formation, Microsoft respondents found knowledge dissemination to be more important. Finally, we found little difference between
distributed and co-located Microsoft teams. Our findings identify the following key areas that warrant focused research: 1) exploring the
non-technical benefits of code reviews, 2) helping developers in articulating review comments, and 3) assisting reviewers{\textquoteright} program
comprehension during code reviews.},
	keywords = {code review, commercial projects, peer impressions, Survey},
	issn = {1939-3520},
	doi = {10.1109/TSE.2016.2576451},
	url = {https://amiangshu.com/papers/CodeReview-TSE-2016.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CodeReview-TSE-2016.pdf},
	author = {Bosu, Amiangshu and Carver, Jeffrey C. and Christian Bird and Orbeck, Jonathan and Chockley, Christopher}
}
@proceedings {1917,
	title = {Understanding the Impressions, Motivations, and Barriers of One Time Code Contributors to FLOSS Projects: A Survey},
	year = {2017},
	month = {05/2017},
	pages = {187-197},
	abstract = {Successful Free/Libre Open Source Software
(FLOSS) projects must attract and retain high-quality talent.
Researchers have invested considerable effort in the study of
core and peripheral FLOSS developers. To this point, one critical
subset of developers that have not been studied are One-Time
code Contributors (OTC) {\textendash} those that have had exactly one patch
accepted. To understand why OTCs have not contributed another
patch and provide guidance to FLOSS projects on retaining
OTCs, this study seeks to understand the impressions, motivations,
and barriers experienced by OTCs. We conducted an online
survey of OTCs from 23 popular FLOSS projects. Based on the
184 responses received, we observed that OTCs generally have
positive impressions of their FLOSS project and are driven by a
variety of motivations. Most OTCs primarily made contributions
to fix bugs that impeded their work and did not plan on becoming
long term contributors. Furthermore, OTCs encounter a number
of barriers that prevent them from continuing to contribute to the
project. Based on our findings, there are some concrete actions
FLOSS projects can take to increase the chances of converting
OTCs into long-term contributors.},
	keywords = {newcomers, One Time Contributors, Qualitative Research, Survey},
	author = {Amanda Lee and Carver, Jeffrey C. and Bosu, Amiangshu}
}
@inbook {1739,
	title = {Surveying the Adoption of FLOSS by Public Administration Local Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {114-123},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Background. The introduction of Open Source Software technologies in the Public Administration plays a key role in the spread of Open Source Software. The state of the art in the adoption of Open Source Software solutions in the Public Administration is not very well known even in areas like Lombardy, which is Italy{\textquoteright}s largest and most developed region.
Goal. The goal of the investigation documented in this paper is to obtain a clear picture about the introduction of Open Source Software technologies in the Public Administration, the obstacles to their adoption, and the willingness of stakeholders to proceed with their introduction.
Method. We carried out a qualitative and quantitative survey that was submitted to a representative part of the Public Administrations in Lombardy.
Results. The analysis of the qualitative and quantitative information shows that several Public Administrations are already using Open Source Software technologies, though not in all application areas. The savings are one frequently cited incentive to the adoption of Open Source Software. However, one obstacle is the fact that a comprehensive law on software in the Public Administration has not yet been approved.
Conclusions. Our analysis provides results that indicate a common understanding of incentives, obstacles, and opportunities for Open Source Software technologies in Public Administrations.},
	keywords = {FLOSS adoption, Italy, Public administrations, Survey},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_11},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_11},
	author = {Tosi, Davide and Lavazza, Luigi and Morasca, Sandro and Chiappa, Marco},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@conference {Robles:2014:FSD:2597073.2597129,
	title = {FLOSS 2013: A Survey Dataset About Free Software Contributors: Challenges for Curating, Sharing, and Combining},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {396{\textendash}399},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this data paper we describe a data set obtained by means of performing an on-line survey to over 2,000 Free Libre Open Source Software (FLOSS) contributors. The survey includes questions related to personal characteristics (gender, age, civil status, nationality, etc.), education and level of English, professional status, dedication to FLOSS projects, reasons and motivations, involvement and goals. We describe as well the possibilities and challenges of using private information from the survey when linked with other, publicly available data sources. In this regard, an example of data sharing will be presented and legal, ethical and technical issues will be discussed.
},
	keywords = {anonymization, data combining, data sharing, ethics, free software, microdata, msr data showcase, open data, open source, privacy, Survey},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597129},
	url = {http://doi.acm.org/10.1145/2597073.2597129},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr14gregorio.pdf},
	author = {Gregorio Robles and Reina, Laura Arjona and Serebrenik, Alexander and Vasilescu, Bogdan and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@proceedings {1445,
	title = {Emerging Hackerspaces {\textendash} Peer-Production Generation},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {94-111},
	publisher = {IFIP AICT},
	abstract = {This paper describes a peer-production movement, the hackerspace movement, its members and values. The emergence of hackerspaces, fablabs and makerspaces is changing how hacker communities and other like-minded communities function. Thus, an understanding of the nature of hackerspaces helps in detailing the features of contemporary peer-production. Building on previous work on {\textquoteright}fabbing{\textquoteright}, two different sets of results are presented: (1) empirical observations from a longitudinal study of hackerspace participants; and (2) a theoretical description of hacker generations as a larger context in which peer-production can be located. With regard to (1), research data has been collected through prolonged observation of hackerspace communities and two surveys.},
	keywords = {COMMUNITY, fabbing, fablab, hackerspace, makerspace, MOTIVATION, movement, open source, peer-production, Survey, sustainability},
	author = {Moilanen, Jarkko}
}
@conference {1316,
	title = {An Empirical Study of Volunteer Members{\textquoteright} Perceived Turnover in Open Source Software Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {"After designing the questionnaire, we conducted a web-based survey by inviting developers working in sourceforge.net and launchpad.net."},
	month = {01/2012},
	pages = {3396-3405},
	abstract = {Turnover of volunteer members and the ensuing instability bring about severe problems to open source software (OSS) projects. To better understand it, we based our study on Herzberg ́s two-factor theory to investigate the influence of hygiene factors on volunteer members ́ dissatisfaction and perceived turnover. After empirically testing the research model, we found shortcomings in project regulation and administration are the key reason for volunteer members ́ dissatisfaction, followed by future rewards and personal needs for software functionalities. By contrast, a possible lack of supportive working relationship among OSS developers was not found to be a trigger for developer dissatisfaction. Dissatisfaction was confirmed to be a significant predictor of perceived turnover. The results demonstrates generalized hygiene factors cannot unreflectively be transferred into the OSS context because volunteer members ́ personal expectation has a weaker influence on perceived turnover than objective attributes of OSS project. Our study further makes suggestions for project administrators.},
	keywords = {developers, launchpad, sourceforge, Survey},
	author = {Yu, Yiqing and Benlian, Alexander and Hess, Thomas}
}
@article {1519,
	title = {How the FLOSS Research Community Uses Email Archives},
	journal = {International Journal of Open Source Software and Processes},
	volume = {4},
	year = {2012},
	note = {classifies 72 FLOSS papers into various analysis categories},
	month = {12/2012},
	pages = {37 - 59},
	abstract = {Artifacts of the software development process, such as source code or emails between developers, are a frequent object of study in empirical software engineering literature. One of the hallmarks of free, libre, and open source software (FLOSS) projects is that the artifacts of the development process are publicly-accessible and therefore easily collected and studied. Thus, there is a long history in the FLOSS research community of using these artifacts to gain understanding about the phenomenon of open source software, which could then be compared to studies of software engineering more generally. This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects. It provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email. The outcome of this paper is to provide a broad overview for the software engineering and FLOSS research communities of how other researchers have used FLOSS email message artifacts in their work},
	keywords = {email, email archives, literature, mailing lists, review, Survey},
	issn = {1942-3934},
	doi = {10.4018/jossp.2012010103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp_v3_PREPRINT.pdf},
	author = {Squire, Megan}
}
@proceedings {1285,
	title = {Adoption of OSS Development Practices by the Software Industry: A Survey},
	year = {2011},
	month = {10/2011},
	pages = {233-243},
	publisher = {Springer},
	abstract = {The paper presents a survey of aspects related to the adoption of Open Source Software by the software industry. The aim of this study was to collect data related to practices and elements in the development process of companies that influence the trust in the quality of the product by potential adopters. The work is part of the research done inside the QualiPSo project and was carried out using a qualitative study based on a structured questionnaire focused on perceptions of experts and development practices used by companies involved in the Open Source Software industry. The results of the survey confirm intuitive concerns related to the adoption of Open Source Software as: the selection of the license, the quality issues addressed, and the development process tasks inside Open Source Software projects. The study uncovered specific aspects related to trust and trustworthiness of the Open Source Software development process that we did not find in previous studies as: the standards implemented by the OSS project, the project{\textquoteright}s roadmap is respected, and the communication channels that are available.},
	keywords = {qualipso, Survey},
	author = {Petrinja, Etiel and Sillitti, Alberto and Succi, Giancarlo}
}
@article {1320,
	title = {An Empirical Study of Open Source Software Usability},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {1 - 16},
	abstract = {Recent years have seen a sharp increase in the use of open source projects by common novice users; Open Source Software (OSS) is thus no longer a reserved arena for software developers and computer gurus. Although user-centered designs are gaining popularity in OSS, usability is still not considered one of the prime objectives in many design scenarios. This paper analyzes industry users{\textquoteright} perception of usability factors, including understandability, learnability, operability, and attractiveness on OSS usability. The research model of this empirical study establishes the relationship between the key usability factors and OSS usability from industrial perspective. In order to conduct the study, a data set of 105 industry users is included. The results of the empirical investigation indicate the significance of the key factors for OSS usability.},
	keywords = {Survey},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010101},
	author = {Raza, Arif and Capretz, Luiz Fernando and Ahmed, Faheem}
}
@proceedings {1283,
	title = {Framing the Conundrum of Total Cost of Ownership of Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {208-219},
	publisher = {Springer},
	abstract = {This paper reflects the results of phase I of our study on the total cost of ownership (TCO) of open source software adoption. Not only have we found TCO to be an intriguing issue but it is contentious, baffling and each company approaches it in a distinctive manner (and sometimes not at all). In effect it is a conundrum that needs unpacking before it can be explained and understood. Our paper discusses the components of TCO as total cost of ownership and total cost of acquisition (and besides). Using this broad dichotomy and its various components we then analyze our data to make sense of procurement decisions in relation to open source software in the public sector and private companies.},
	keywords = {benefits, exit costs, open source software, software adoption, Survey, tco, total cost of ownership},
	author = {Maha Shaikh and Cornford, Tony}
}
@proceedings {1279,
	title = {The Importance of Architectural Knowledge in Integrating Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {142-158},
	publisher = {Springer},
	abstract = {Open Source Software (OSS) is increasingly used in Component-Based Software Development (CBSD) of large software systems. An important issue in CBSD is selection of suitable components. Various OSS selection methods have been proposed, but most of them do not consider the software architecture aspects of OSS products. The Software Architecture (SA) research community refers to a product{\textquoteright}s architectural information, such as design decisions and underlying rationale, and used architecture patterns, as Architecture Knowledge (AK). In order to investigate the importance of AK of OSS components in integration, we conducted an exploratory empirical study. Based on in-depth interviews with 12 IT professionals, this paper presents insights into the following questions: 1) what AK of OSS is needed? 2) Why is AK of OSS needed? 3) Is AK of OSS generally available? And 4) what is the relative importance of AK? Based on these new insights, we provide a research agenda to further the research field of software architecture in OSS.},
	keywords = {architectural knowledge, component-based development, Open Source Software integration, OSS Integrator, software architecture, Survey},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris}
}
@proceedings {1275,
	title = {Preparing FLOSS for Future Network Paradigms: A Survey on Linux Network Management},
	year = {2011},
	month = {10/2011},
	pages = {75-89},
	publisher = {Springer},
	abstract = {Operating system tools must fulfill the requirements generated by the advances in networking paradigms. To understand the current state of the Free, Libre and Open Source Software (FLOSS) ecosystem, we present a survey on the main tools used to manage and interact with the network, and how they are organized in Linux-based operating systems. Based on the survey results, we present a reference Linux network stack that can serve as the basis for future heterogeneous network environments, contributing towards a standardized approach in Linux. Using this stack, and focusing on dynamic and spontaneous network interactions, we present an evolution path for network related technologies, contributing to Linux as a network research operating system and to FLOSS as a whole.},
	keywords = {linux, networking, Survey},
	author = {Matos, Alfredo and Thomson, John and Paulo Trezentos}
}
@conference {Meneely:2011:SDN:1985793.1985832,
	title = {Socio-technical developer networks: should we trust our measurements?},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	pages = {281{\textendash}290},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development teams must be properly structured to provide effectiv collaboration to produce quality software. Over the last several years, social network analysis (SNA) has emerged as a popular method for studying the collaboration and organization of people working in large software development teams. Researchers have been modeling networks of developers based on socio-technical connections found in software development artifacts. Using these developer networks, researchers have proposed several SNA metrics that can predict software quality factors and describe the team structure. But do SNA metrics measure what they purport to measure? The objective of this research is to investigate if SNA metrics represent socio-technical relationships by examining if developer networks can be corroborated with developer perceptions. To measure developer perceptions, we developed an online survey that is personalized to each developer of a development team based on that developer{\textquoteright}s SNA metrics. Developers answered questions about other members of the team, such as identifying their collaborators and the project experts. A total of 124 developers responded to our survey from three popular open source projects: the Linux kernel, the PHP programming language, and the Wireshark network protocol analyzer. Our results indicate that connections in the developer network are statistically associated with the collaborators whom the developers named. Our results substantiate that SNA metrics represent socio-technical relationships in open source development projects, while also clarifying how the developer network can be interpreted by researchers and practitioners.},
	keywords = {developer network, developers, linux, linux kernel, PHP, social network analysis, Survey, wireshark},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985832},
	url = {http://doi.acm.org/10.1145/1985793.1985832},
	author = {Meneely, Andrew and Williams, Laurie}
}
@article {10.1109/TSE.2010.63,
	title = {What Makes a Good Bug Report?},
	journal = {IEEE Transactions on Software Engineering},
	volume = {36},
	year = {2010},
	note = {"o find out which matter most, we asked 872 devel-
opers from the APACHE, ECLIPSE, and MOZILLA projects to:
1. Complete a survey on important information in bug reports and the problems they faced with them. We received a total of 156 responses to our survey (Section 2 and 3).
2. Rate the quality of bug reports from very poor to very good on a five-point Likert scale [22]. We received a total of 1,186 votes for 289 randomly selected bug reports (Section 4).
In addition, we asked 1,354 reporters1 from the same projects to complete a similar survey, out of which 310 responded. "},
	pages = {618-643},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {In software development, bug reports provide crucial information to developers. However, these reports widely differ in their quality. We conducted a survey among developers and users of APACHE, ECLIPSE, and MOZILLA to find out what makes a good bug report.
The analysis of the 466 responses revealed an information mis- match between what developers need and what users supply. Most developers consider steps to reproduce, stack traces, and test cases as helpful, which are at the same time most difficult to provide for users. Such insight is helpful to design new bug tracking tools that guide users at collecting and providing more helpful information.
Our CUEZILLA prototype is such a tool and measures the quality of new bug reports; it also recommends which elements should be added to improve the quality. We trained CUEZILLA on a sample of 289 bug reports, rated by developers as part of the survey. In our experiments, CUEZILLA was able to predict the quality of 31{\textendash}48\% of bug reports accurately.},
	keywords = {bug report, Survey},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2010.63},
	url = {http://dl.acm.org/citation.cfm?id=1453146},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bettenburg-fse-2008.pdf},
	author = {Zimmermann, Thomas and Premraj, Rahul and Bettenburg, Nicolas and Sascha Just and Schroter, Adrian and Weiss, Cathrin}
}
@article {Xu2009151,
	title = {Volunteers{\textquoteright} involvement in online community based software development},
	journal = {Information \& Management},
	volume = {46},
	number = {3},
	year = {2009},
	note = {"Data were collected through an online survey and by searching project archives. On Sourceforge.net, each developer was uniquely identified with a user account, and the developer{\textquoteright}s performance was assessed through the number of function points accepted by the project in a certain time period, obtained through conversion and calculation from the project{\textquoteright}s code repository. Data for other constructs were obtained from the developers{\textquoteright} response to the online survey. "
"a developer{\textquoteright}s performance was measured by the number of function points made and accepted into the project during the observed time period."

project age, development status, license type, number of developers},
	pages = {151 - 158},
	abstract = {We sought to gain understanding of voluntary developers{\textquoteright} involvement in open source software (OSS) projects. Data were collected from voluntary developers working on open source projects. Our findings indicated that a voluntary developer{\textquoteright}s involvement was very important to his or her performance and that involvement was dependent on individual motivations (personal software needs, reputation and skills gaining expectation, enjoyment in open source coding) and project community factors (leadership effectiveness, interpersonal relationship, community ideology). Our work contributes theoretically and empirically to the body of OSS research and has practical implications for OSS project management.},
	keywords = {age, developers, effectiveness, function points, ideology, leadership, MOTIVATION, scm, sourceforge, status, Survey, team size, Volunteers},
	issn = {0378-7206},
	doi = {DOI: 10.1016/j.im.2008.12.005},
	url = {http://www.sciencedirect.com/science/article/B6VD0-4VP1CN0-1/2/8e1c7be4fcedd1419209c5c843ffa923},
	author = {Bo Xu and Donald R. Jones and Bingjia Shao}
}
@article {flosswp113,
	title = {The Impact of Ideology on Effectiveness in Open Source Software Development Teams},
	journal = {MIS Quarterly},
	volume = {30},
	number = {2},
	year = {2006},
	note = {"...we collected data related to OSS projects hosted on Sourceforge (www.sourceforge.net)."
"Data was collected using two surveys and from the Sourceforge website."
},
	month = {2006},
	pages = {291-314},
	abstract = {The emerging work on understanding open source software has argued for the importance of understanding what leads to effectiveness in OSS development teams and has pointed to the importance of ideology. This paper develops a framework of the OSS ideology (including specific norms, beliefs, and values) and a theoretical model to show how adherence to components of the ideology impact effectiveness in OSS teams. The model is based on the idea that ideology provides clan control, which is important in OSS development settings because OSS teams generally lack formal behavioral and outcome controls. The paper hypothesizes both direct effects of ideology on OSS team effectiveness and indirect effects via influences on affective trust, cognitive trust, and communication quality. Hypotheses are tested using survey and objective data on OSS projects. Four effectiveness measures are used to capture unique aspects of effectiveness in OSS including both the extent to which a team attracts input from the community and the team{\textquoteright}s success in accomplishing project outcomes. Results support the main thesis that OSS team members{\textquoteright} adherence to the tenets of the OSS community ideology enhances OSS team effectiveness. The study uncovers several differences in the importance of OSS norms, beliefs, and values to different kinds of OSS team effectiveness and discusses implications for theory and practice.},
	keywords = {bug fixing, bug reports, bug tracking, communication, COMMUNITY, effectiveness, feature requests, ideology, metadata, sourceforge, Survey, team effort, team size, trust},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewartgosain2.pdf},
	author = {Stewart, K. and Gosain, S.}
}
@conference {1094,
	title = {Knowledge Reuse in Open Source Software: An Exploratory Study of 15 Open Source Projects},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2006},
	note = {"In a first step, we asked developers of different open source projects to respond to a very short web-based survey."...
"In a second step, we started with gathering data from 15 projects, including interviews. In parallel, the source code, CVS comments and to a certain extent email communication was analyzed to receive a dynamic, and within the limits of the method, complete picture of knowledge reuse practices."
"Projects included games (Adonthell, FlightGear, Xboard), text processing (Abiword), a GNU/Linux desktop (Xfce4), an instant messenger client (Miranda), fax software (HylaFAX), a content management system (Tiki/CMS Groupware), encryption software (OpenSSL), a collaborative music system (iRATE Radio), file sharing networks (GNUnet, Mnet, Freenet), a mailing list manager (Mailman), and an mp3 encoder (Lame)."
"Our data sources included interviews with key developers, source code, CVS comments, mailing lists and various Internet resources"},
	month = {2006},
	pages = {1-10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {To date, there is no investigation of knowledge reuse in open source software projects. This paper focuses on the forms of knowledge reuse and the factors impacting on them. It develops a theory drawn from data of 15 open source software projects and finds that the effort to search, integrate and maintain external knowledge influences the form of knowledge to be reused. Implications for firms and innovation research are discussed.},
	keywords = {cvs, email, knowledge reuse, lines of code, loc, source code, Survey},
	doi = {10.1109/HICSS.2005.378},
	url = {http://www.computer.org/csdl/proceedings/hicss/2005/2268/07/22680198b-abs.html},
	author = {von Krogh, G. and Spaeth, S. and Haefliger, S.}
}
@conference {703,
	title = {Participation in Free and Open Source Communities: An Empirical Study of Community Members{\textquoteright} Perceptions},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {221 - 231},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Although the defining factors of Free and Open Source Software (FOSS) are generally seen as the availability and accessibility of the source code, it is what these facilitate that is perhaps of more significance. Source code availability allows the sharing of code, skills, knowledge, and effort, focused on a particular piece of software under development. The result of this is the FOSS community, which although often perceived as a single group, is actually many small groups, each bound by a common interest in a particular piece of software and using the Internet as a communication medium. Although there have been studies focusing on the motivation of FOSS developers to contribute to software, there has been little investigation into the motives, attitudes, and the culture within the communities as a whole. There is much more to most of these communities than software development. Many also have extensive support networks for the use of software, portals for research, and social facilities. This paper describes the results of an investigation into how FOSS community members perceive the communities that they belong to, their reasons for being in the community, and the manner in which they participate.
},
	keywords = {Survey},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Participation\%20in\%20free\%20and\%20open\%20source.pdf},
	author = {Schofield, Andrew and Cooper, Grahame}
}
@article {1122,
	title = {Understanding the Motivations, Participation, and Performance of Open Source Software Developers: A Longitudinal Study of the Apache Projects},
	journal = {Management Science},
	volume = {52},
	year = {2006},
	note = {"analyzing archival data collected from OSS project records over a period of four years"
"Apart from the source and binary codes of the actual software programs, Apache products include developer websites, change logs, documentation, and developer communications in the form of e-mail archives. From these products, we extracted two types of information: each contributor{\textquoteright}s progression along the Apache career path, and each contributor{\textquoteright}s source code contributions to the project."},
	month = {07/2006},
	pages = {984 - 999},
	abstract = {Understanding what motivates participation is a central theme in the research on open source software (OSS) development. Our study contributes by revealing how the different motivations of OSS developers are interrelated, how these motivations influence participation leading to performance, and how past performance influences subsequent motivations. Drawing on theories of intrinsic and extrinsic motivation, we develop a theoretical model relating the motivations, participation, and performance of OSS developers. We evaluate our model using survey and archival data collected from a longitudinal field study of software developers in the Apache projects. Our results reveal several important findings. First, we find that developers{\textquoteright} motivations are not independent but rather are related in complex ways. Being paid to contribute to Apache projects is positively related to developers{\textquoteright} status motivations but negatively related to their use-value motivations. Perhaps surprisingly, we find no evidence of diminished intrinsic motivation in the presence of extrinsic motivations; rather, status motivations enhance intrinsic motivations. Second, we find that different motivations have an impact on participation in different ways. Developers{\textquoteright} paid participation and status motivations lead to above-average contribution levels, but use-value motivations lead to below-average contribution levels, and intrinsic motivations do not significantly impact average contribution levels. Third, we find that developers{\textquoteright} contribution levels positively impact their performance rankings. Finally, our results suggest that past-performance rankings enhance developers{\textquoteright} subsequent status motivations.},
	keywords = {apache, change logs, contributions, email, email archives, extrinsic motivation, intrinsic motivation, mailing lists, MOTIVATION, open source software, participation, software development performance, source code, status, Survey},
	issn = {1526-5501},
	doi = {10.1287/mnsc.1060.0554},
	author = {Roberts, Jeffrey A. and Il-Horn Hann and Slaughter, Sandra A.}
}
@proceedings {117,
	title = {A human capital perspective of organizational intention to adopt open source software},
	year = {2005},
	keywords = {Survey},
	author = {Yan Li and Chuan-Hoo Tan and Hock-Hai Teo and Alex Siow}
}
@proceedings {1185,
	title = {Contributing to OS Projects. A Comparison between Individual and Firms},
	year = {2004},
	note = {"Following the approach used in previous surveys on Open Source developers, we prepared an on-line questionnaire;"},
	pages = {18-22},
	abstract = {This paper studies the contributions software firms make to Open Source (OS) projects. Our goal is to ascertain whether they follow the same regularity of pattern seen for individual programmer An exhaustive empirical analysis was carried out using data on project membership1 , project coordination and the contributions made by 146 Italian firms that do business with OS software. We compare our findings with the results of the surveys taken on OS programmers. The availability of the data gathered by Hertel et al. ([10]) on 141 developers of the Linux kernel allowed a direct comparison to be carried out between the two sets2 .},
	keywords = {Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/19-23.pdf},
	author = {Andrea Bonaccorsi and Cristina Rossi}
}
@proceedings {1194,
	title = {Inside an Open Source Software Community: Empirical Analysis on Individual and Group Level},
	year = {2004},
	pages = {65-70},
	abstract = {An established Open Source Software community (Apache Cocoon) was explored using an online questionnaire about demographic data and individual and	group-related	factors.	Individual	factors encompassed forms of contributions, motivation, expertise and knowledge. Role structures, expectations towards other members, trust and collaboration issues were analysed at group level. More than 60\% of the developer community completed this questionnaire. Results provide a valuable basis for deeper understanding of knowledge sharing, collaboration and innovation processes in distributed work groups.},
	keywords = {apache, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maass66-71.pdf},
	author = {Maass, W.}
}
@proceedings {103,
	title = {Why developers participate in open source software projects: an empirical investigation},
	year = {2004},
	keywords = {Survey},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter}
}
@article {flosswp103,
	title = {Contributing to the common pool resources in Open Source software. A comparison between individuals and firms},
	year = {2003},
	month = {August},
	abstract = {This paper studies the contributions to Open Source projects of software firms. Our goal is to analyse whether they follow the same regularities that characterize the behaviour of individual programmers. An exhaustive empirical analysis is carried out using data on project membership, project coordination and contribution efforts of 146 Italian firms that do business with Open Source software. We follow a meta-analytic approach comparing our findings with the results of the surveys conducted on Free Software programmers. Moreover, the availability of the data gathered by Hertel et al. (2003) on 141 developers of the Linux kernel will allow direct comparisons between the two sets.},
	keywords = {developers, linux, linux kernel, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossidevelopers.pdf},
	author = {Andrea Bonaccorsi}
}
@article {2003,
	title = {From a Firm-Based to a Community-Based Model of Knowledge Creation: The Case of the Linux Kernel Development},
	journal = {Organization Science},
	volume = {14},
	number = {6},
	year = {2003},
	note = {"we study the Linux development community mainly by analyzing the artifacts that the Linux developers have produced. A key output of knowledge creation activities is the artifacts. The most important artifact, of course, is the Linux operating system source code."
"Along with the source code, a "Credits" text file and a "MAINTAINERS" text file are distributed to the users."
"An equally important artifact is the development activities archived in the Linux-kernel mailing list"..."Using the weekly Linux-kernel email archive for years 1995 to 2000 as a key source of data, we focus on people who have sent at least one email to the Linux-kernel mailing list. "
"In addition, we examine the developers{\textquoteright} demographic distributions, working patterns, and motivations by analyzing the raw data from an on-line survey"},
	pages = {pp. 633-649},
	publisher = {INFORMS},
	abstract = {We propose a new model of knowledge creation in purposeful, loosely coordinated, distributed systems, as an alternative to a firm-based one. Specifically, using the case of the Linux kernel development project, we build a model of community-based, evolutionary knowledge creation to study how thousands of talented volunteers, dispersed across organizational and geographical boundaries, collaborate via the Internet to produce a knowledge-intensive, innovative product of high quality. By comparing and contrasting the Linux model with the traditional/commercial model of software development and firm-based knowledge creation efforts, we show how the proposed model of knowledge creation expands beyond the boundary of the firm. Our model suggests that the product development process can be effectively organized as an evolutionary process of learning driven by criticism and error correction. We conclude by offering some theoretical implications of our community-based model of knowledge creation for the literature of organizational learning, community life, and the uses of knowledge in society.},
	keywords = {credits, developers, email, email archives, knowledge creation, linux kernel, mailing list, maintainers, scm, source code, Survey, Volunteers},
	issn = {10477039},
	url = {http://www.jstor.org/stable/4135125},
	author = {Lee, Gwendolyn K. and Cole, Robert E.}
}
@article {flosswp77,
	title = {Guarding the Commons: How Community Managed Software Projects Protect Their Work},
	journal = {Research Policy},
	volume = {32},
	year = {2003},
	note = {"Data was collected from three primary sources: 1) observation at project and user group meetings, technical presentations and conferences; 2) informant interviews; and 3) project data archived on the Internet that detailed project interactions and structural developments."

"Project data was collected from online archives and included documents such as: mission statements, charters, bylaws, meeting minutes, and mailing list archives."},
	month = {February},
	pages = {1179-1198},
	edition = {7},
	abstract = {Theorists often speculate why open source and free software project contributors give their work away. Although contributors make their work publicly available, they do not forfeit their rights to it. Community managed software projects protect their work by using several legal and normative tactics, which should not be conflated with a disregard for or neglect of intellectual property rights. These tactics allow a project?s intellectual property to be publicly and freely available and yet, governable. Exploration of this seemingly contradictory state may provide new insight into governance models for the management of digital intellectual property.},
	keywords = {Common Pool Resources, email, email archives, intellectual property, mailing list, open source, Public Goods, Software, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-omahony.pdf},
	author = {Siobhan O{\textquoteright}Mahony}
}
@article {116,
	title = {How open source software works: "free" user-to-user assistance},
	journal = {Research Policy},
	volume = {32},
	number = {6},
	year = {2003},
	note = {"The empirical data we collected for study was related to postings to the Apache Usenet help forum, CIWS-U (comp.infosystems.www.servers.unix). "
"For data regarding long-term participation in CIWS-U{\textemdash}who participated, long-term trends, etc.{\textemdash}we examined Usenet posting patterns from 1996 to 1999."
"The Usenet log data was obtained from a World Wide Web service called Deja.com (since acquired by Google)"
survey},
	pages = {923-943},
	abstract = {Research into free and open source software development projects has so far largely focused on how the major tasks of software development are organized and motivated. But a complete project requires the execution of "mundane but necessary" tasks as well. In this paper, we explore how the mundane but necessary task of field support is organized in the case of Apache web server software, and why some project participants are motivated to provide this service gratis to others. We find that the Apache field support system functions effectively. We also find that, when we partition the help system into its component tasks, 98\% of the effort expended by information providers in fact returns direct learning benefits to those providers. This finding considerably reduces the puzzle of why information providers are willing to perform this task "for free." Implications are discussed.},
	keywords = {apache, help, logs, MOTIVATION, participants, Survey, usenet},
	doi = {http://dx.doi.org/10.1016/S0048-7333(02)00095-1},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.110.8172\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhani2003.pdf},
	author = {Karim R Lakhani and von Hippel, Eric}
}
@conference {Wynn03organizationalstructure,
	title = {Organizational Structure of Open Source Projects: A Life Cycle Approach},
	booktitle = {Proceedings of 7th Annual Conference of the Southern Association for Information Systems},
	year = {2003},
	note = {"The three graphs in Figure 2 below were taken from smoothed download counts for existing open source projects on Sourceforge.net"
"A random sample of 150 open source projects will be taken from data provided by Sourceforge.net. Each project will be evaluated to determine their current life cycle stage (where possible) using download counts. Next, the project admins, developers, and several identifiable users for each evaluated project will be contacted via email to request completing a brief questionnaire to measure the current focus of the project, formal structure, division of labor, leader role, coordination, level of commitment, user success, and developer success. "},
	abstract = {The structure of open source project communities is discussed in relation to the organizational life cycle. In lieu of sales figures, the download counts for each project are used to identify the life cycle stage of a random sample of open source projects. A research model is proposed that attempts to measure the fit between the life cycle stage and the specific organizational characteristics of these projects (focus, division of labor, role of the leader, level of commitment, and coordination/control) as an indicator of the success of a project as measured by the satisfaction and involvement of both developers and users.},
	keywords = {division of labor, downloads, growth, interview, leadership, life cycle, lifecycle, project success, roles, sourceforge, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wynn2004.pdf},
	author = {Donald E. Wynn}
}
@proceedings {104,
	title = {Economic incentives for participating in open source software projects},
	year = {2002},
	note = {"The data for this research come from two primary sources: Apache project archives and a targeted survey of Apache participants. Archival data are open source project artifacts such as e-mail and source code archives, source code version control meta-data, and developer Web sites"
independent variables: patch, committer, work experience, programming experience, education, job switch, firm size, firm public, industry},
	pages = {365{\textendash}372},
	abstract = {Using the Internet as a basis for communication, collaboration, and storage of artifacts, the open source community is producing software of a quality that was previously thought to be achievable only by professional engineers following strict software development paradigms. This accomplishment is even more astounding as developers contribute to the source code without any remuneration. Open source leaders as well as academics have proposed theories about the motivation of open source developers that are rooted in diverse fields such as social psychology and anthropology. However, Lerner and Tirole (2000) argue that developer participation in open source projects may, in part, be explained by existing economic theory regarding career concerns. This research seeks to confirm or disconfirm the existence of economic returns to participation in open source development. Our findings suggest that greater open source participation per se, as measured in contributions made, is not associated with wage increases. However, a higher status in a merit-based ranking within the Apache Project is associated with significantly higher wages. This suggests that employers do not reward the gain in experience through open source participation as an increase in human capital. The results are also consistent with the notion that a high rank within the Apache Software Foundation is a credible signal of the productive capacity of a programmer.},
	keywords = {apache, contributions, email, email archives, mailing list, organizational sponsorship, participation, patch, scm, source code, Survey, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/42.pdf},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter and Roy Fielding}
}
@article {1095,
	title = {High Quality and Open Source Software Practices},
	journal = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We examined the publicly visible portions of these projects from November 2001 through March 2002, ...The SLOC counts for the predominate languages are shown},
	month = {2002},
	abstract = {Surveys suggest that, according to various metrics, the quality and dependability of today{\textquoteright}s open source software is roughly on par with commercial and government developed software. What are the prospects for advancing to much higher levels of quality in open source software? More specifically, what attributes must be possessed by quality-related interventions for them to be feasibly adoptable in open source practice? In order to identify some of these attributes, we conducted a preliminary survey of the quality practices of a number of successful open source projects. We focus, in particular, on attributes related to adoptability by the open source practitioner community.},
	keywords = {apache, bug report, bug tracker, bug tracking system, feature requests, gcc, gnome, kde, lines of code, linux, loc, mozilla, netbeans, perl, position paper, python, sloc, source code, Survey, tomcat, xfree86},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HalloranScherlis.pdf},
	author = {T. Halloran and W. Scherlis}
}
@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.}
}
