@proceedings {1875,
	title = {Considering the use of walled gardens for FLOSS project communication},
	year = {2017},
	month = {05/2017},
	abstract = {At its core, free, libre, and open source software (FLOSS) is defined by its adherence to a set of licenses that give various freedoms to the users of the software, for example the ability to use the software, to read or modify its source code, and to distribute the software to others. In addition, many FLOSS projects and developers also champion other values related to "freedom" and "openness", such as transparency, for example in communication and decision-making, or community-orientedness, for example in broadening access, collaboration, and participation. This paper explores how one increasingly common software development practice - communicating inside non-archived, third-party "walled gardens" - puts these FLOSS values into conflict. If communities choose to use non-archived walled gardens for communication, they may be prioritizing one type of openness (broad participation) over another (transparency). We use 18 FLOSS projects as a sample to describe how walled gardens are currently being used for intra-project communication, as well as to determine whether or not these projects provide archives of these communications. Findings will be useful to the FLOSS community as a whole as it seeks to under- stand the evolution and impact of its communication choices.},
	keywords = {apache, chat, communication, email, free software, irc, mailing list, open source, Slack, Stack Overflow, teams, Wordpress},
	doi = {10.1007/978-3-319-57735-7_1},
	url = {https://link.springer.com/content/pdf/10.1007\%2F978-3-319-57735-7_1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/preprint_0.pdf},
	author = {Squire, Megan}
}
@proceedings {1890,
	title = {Designing for Participation: Three Models for Developer Involvement in Hybrid OSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {23-33},
	publisher = {Springer},
	abstract = {This paper reports governance practices of three profit oriented companies that develop OSS software with the help of their respective open development communities. We explore how the companies allow development contributions from external stakeholders, and what knowledge they let out of their internal software development activities. The results lay ground for further research on how to organize openness of the software development process in hybrid setups where the needs of different stakeholders are partly competing - yet complementary.},
	keywords = {Community Management, Hybrid open source, open source},
	doi = {10.1007/978-3-319-57735-7_3},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_3},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and Mikkonen, Tommi and M{\"a}nnist{\"o}, Tomi}
}
@proceedings {1894,
	title = {Digging into the Eclipse Marketplace},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {60-65},
	publisher = {Springer},
	abstract = {Eclipse is an integrated development environment that can be extended with plug-ins. Thanks to Eclipse{\textquoteright}s success, a diverse community has been established with members coming from industry, open-source projects, and others, and a marketplace with more than 1.700 different plug-ins developed. Hence, the question arises how this marketplace is composed: Who contributes plug-ins? Which plug-ins are successful? Are there common characteristics or trends? To answer these questions, extensive investigations are necessary. In this paper, we present (i) an initial approach for corresponding analyses and (ii) preliminary results. Overall, we aim to pave the way for further research addressing, for example, motivations to participate in, or the evolution of, open marketplaces.},
	keywords = {Eclipse IDE, Eclipse Marketplace, empirical study, open source},
	doi = {10.1007/978-3-319-57735-7_7},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_7},
	author = {Kr{\"u}ger, J and Corr, N and Schr{\"o}ter, I and Leich, T}
}
@inbook {Kerzazi2017,
	title = {Knowledge Flows Within Open Source Software Projects: A Social Network Perspective},
	booktitle = {Advances in Ubiquitous Networking 2: Proceedings of the UNet{\textquoteright}16},
	year = {2017},
	pages = {247{\textendash}258},
	publisher = {Springer Singapore},
	organization = {Springer Singapore},
	address = {Singapore},
	abstract = {Developing software is knowledge-intensive activity, requiring extensive technical knowledge and awareness. The abstract part of development is the social interactions that drive knowledge flows between contributors, especially for Open Source Software (OSS). This study investigated knowledge sharing and propagation from social perspective using social network analysis (SNA). We mined and analyzed the issue and review histories of three OSS from GitHub. Particular attention has been paid to the socio-interactions through comments from contributors on reviews. We aim at explaining the propagation and density of knowledge flows within contributor networks. The results show that review requests flow from the core contributors toward peripheral contributors and comments on reviews are in a continuous loop from the core teams to the peripherals and back; and the core contributors leverage on their awareness and technical knowledge to increase their notoriety by playing the role of communication brokers supported by comments on work items.},
	keywords = {expertise, Knowledge flows, open source, SNA},
	isbn = {978-981-10-1627-1},
	doi = {10.1007/978-981-10-1627-1_19},
	url = {http://dx.doi.org/10.1007/978-981-10-1627-1_19},
	author = {Kerzazi, Noureddine and El Asri, Ikram},
	editor = {El-Azouzi, Rachid and Menasche, Daniel Sadoc and Sabir, Essa{\"\i}d and De Pellegrini, Francesco and Benjillali, Mustapha}
}
@proceedings {1904,
	title = {OSSpal: Finding and Evaluating Open Source Software},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {193-203},
	publisher = {Springer},
	abstract = {This paper describes the OSSpal project, which is aimed at helping companies, government agencies, and other organizations find high quality free and open source software (FOSS) that meets their needs. OSSpal is a successor to the Business Readiness Rating (BRR), combining quantitative and qualitative evaluation measures for software in various categories. Instead of a purely numeric calculated score OSSpal adds curation of high-quality FOSS projects and individual user reviews of these criteria. Unlike the BRR project, for which there was no automated support, OSSpal has an operational, publicly available website where users may search by project name or category, and enter ratings and reviews for projects.

},
	keywords = {Open source forges, software evaluation, software metrics, Software taxonomy},
	doi = {10.1007/978-3-319-57735-7_18},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_18},
	author = {Wasserman, A. and Guo, X. and McMillian, B. and Qian K. and Wei M.Y. and Xu, Q.}
}
@proceedings {1903,
	title = {Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {167-181},
	publisher = {Springer},
	abstract = {The dictum of {\textquotedblleft}Release early, release often.{\textquotedblright} by Eric Raymond as the Linux modus operandi highlights the importance of release management in open source software development. Nevertheless, there are very few empirical studies addressing release management in open source software development. It is already known that most open source software communities adopt either feature-based or time-based release strategies. Each of these has its advantages and disadvantages that are context-specific. Recent research reported that many prominent open source software projects have moved from feature-based to time-based releases. In this longitudinal case study, we narrate how OpenStack shifted towards a liberal six-month release cycle. If prior research discussed why projects should adopt time-based releases and how they can adopt such a strategy, we discuss how OpenStack adapted its software development processes, its organizational design and its tools toward a hybrid release management strategy {\textemdash} a strive for balancing the benefits and drawbacks of feature-based and time-based release strategies.},
	keywords = {openstack, release management},
	doi = {10.1007/978-3-319-57735-7_16},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_16},
	author = {Teixeira, Jose}
}
@proceedings {1897,
	title = {Understanding the Effects of Practices on KDE Ecosystem Health},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {89-100},
	publisher = {Springer},
	abstract = {Open source software ecosystems have adjusted and evolved a set of practices over the years to support the delivery of sustainable software. However, few studies have investigated the impacts of such practices on the health of these ecosystems. In this paper, we present the results of an ethnographic-based study conducted during the Latin-American KDE users and contributors meeting (LaKademy 2015) with the goal of collecting practices used within the KDE ecosystem and understanding how they affect ecosystem health. The analysis was based on softgoal interdependency graphs adapted to represent practices and relate them to non-functional requirements and goals. Our results provide a preliminary insight to understand how KDE ecosystem community interacts, which working practices have been adopted and how they affect ecosystem health.

},
	keywords = {Ethnographic studies, Open source software ecosystems, Software ecosystem health, Software practices},
	doi = {10.1007/978-3-319-57735-7_10},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_10},
	author = {Simone da Silva Amorim and John D. McGregor and Eduardo Santana de Almeida and Christina von Flach Garcia Chavez}
}
@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}
}
@article {Krishnamurthy:2016:PDP:2869770.2820618,
	title = {Peripheral Developer Participation in Open Source Projects: An Empirical Analysis},
	journal = {ACM Trans. Manage. Inf. Syst.},
	volume = {6},
	number = {4},
	year = {2016},
	pages = {14:1{\textendash}14:31},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of the Open Source model of software development depends on the voluntary participation of external developers (the peripheral developers), a group that can have distinct motivations from that of project founders (the core developers). In this study, we examine peripheral developer participation by empirically examining approximately 2,600 open source projects. In particular, we hypothesize that peripheral developer participation is higher when the potential for building reputation by gaining recognition from project stakeholders is higher. We consider recognition by internal stakeholders (such as core developers) and external stakeholders (such as end-users and peers). We find a positive association between peripheral developer participation and the potential of stakeholder recognition after controlling for bug reports, feature requests, and other key factors. Our findings provide important insights for OSS founders and corporate managers for open sourcing or OSS adoption decisions.
},
	keywords = {Code ownership, open source software, project management, software metrics},
	issn = {2158-656X},
	doi = {10.1145/2820618},
	url = {http://doi.acm.org/10.1145/2820618},
	author = {Krishnamurthy, Rajiv and Jacob, Varghese and Radhakrishnan, Suresh and Kutsal Dogan}
}
@article {1864,
	title = {Roles and politeness behavior in community-based free/libre open source software development},
	journal = {Information \& Management},
	year = {2016},
	month = {11/2016},
	abstract = {Community-based Free/Libre Open Source Software (FLOSS) development relies on contributions from both core and peripheral members. Prior research on core{\textendash}periphery has focused on software coding-related behaviors. We study how core{\textendash}periphery roles are related to social-relational behavior in terms of politeness behavior. Data from two FLOSS projects suggest that both core and peripheral members use more positive politeness strategies than negative strategies. Further, core and peripheral members use different strategies to protect positive face in positive politeness, which we term respect and intimacy, respectively. Our results contribute to FLOSS research and politeness theory.

},
	keywords = {Core{\textendash}periphery structure, open source software development, Politeness behavior},
	issn = {03787206},
	doi = {10.1016/j.im.2016.11.006},
	url = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Group_maintenance\%20paper\%20to\%20share.pdf},
	author = {Kangning Wei and Kevin Crowston and Eseryel, U.Yeliz and Robert Heckman}
}
@article {1857,
	title = {Is there a wage premium for volunteer OSS engagement? {\textendash} signalling, learning and noise},
	journal = {Applied Economics},
	year = {2016},
	month = {09/2016},
	pages = {1 - 16},
	publisher = {Routledge},
	abstract = {Volunteer-based open-source production has become a significant new model for the organization of software development. Economics often pictures this phenomenon as a case of signaling: Individuals engage in the volunteer programming of open-source software (OSS) as a labor-market signal resulting in a wage premium. Yet, this explanation could so far not be empirically tested. The present paper fills this gap by estimating an upper-bound composite wage premium of voluntary OSS contributions and by separating the potential signaling effect of OSS engagement from other effects. Although some 70\% of OSS contributors believe that OSS involvement benefits their careers, we find no actual labor market premium for OSS engagement. The presence of other motives such as fun of play or altruism render OSS contributions too noisy to function as a signal.},
	keywords = {open source software, peer production, signalling, voluntary work, wage formation},
	issn = {1466-4283},
	doi = {10.1080/00036846.2016.1218427},
	author = {Bitzer, J{\"u}rgen and Geishecker, Ingo and Schr{\"o}der, Philipp J. H.}
}
@proceedings {1750,
	title = {Co-evolution of Infrastructure and Source Code - An Empirical Study},
	year = {2015},
	month = {05/2015},
	abstract = {Infrastructure-as-code automates the process of
configuring and setting up the environment (e.g., servers, VMs
and databases) in which a software system will be tested and/or
deployed, through textual specification files in a language like
Puppet or Chef. Since the environment is instantiated automatically
by the infrastructure languages{\textquoteright} tools, no manual
intervention is necessary apart from maintaining the infrastructure
specification files. The amount of work involved with such
maintenance, as well as the size and complexity of infrastructure
specification files, have not yet been studied empirically. Through
an empirical study of the version control system of 265 OpenStack
projects, we find that infrastructure files are large and churn
frequently, which could indicate a potential of introducing bugs.
Furthermore, we found that the infrastructure code files are
coupled tightly with the other files in a project, especially test files,
which implies that testers often need to change infrastructure
specifications when making changes to the test framework and
tests.},
	keywords = {openstack},
	url = {http://mcis.polymtl.ca/publications/2015/msrjojo.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msrjojo.pdf},
	author = {Yujuan Jiang and Adams, Bram}
}
@proceedings {1772,
	title = {An Empirical Study of Architectural Change in Open-Source Software Systems},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {From its very inception, the study of software
architecture has recognized architectural decay as a regularly
occurring phenomenon in long-lived systems. Architectural decay
is caused by repeated changes to a system during its lifespan.
Despite decay{\textquoteright}s prevalence, there is a relative dearth of empirical
data regarding the nature of architectural changes that may lead
to decay, and of developers{\textquoteright} understanding of those changes. In
this paper, we take a step toward addressing that scarcity by
conducting an empirical study of changes found in software
architectures spanning several hundred versions of 14 opensource
systems. Our study reveals several new findings regarding
the frequency of architectural changes in software systems, the
common points of departure in a system{\textquoteright}s architecture during
maintenance and evolution, the difference between system-level
and component-level architectural change, and the suitability
of a system{\textquoteright}s implementation-level structure as a proxy for its
architecture.},
	keywords = {architectural change, architecture recovery, open-source systems, software architecture, software evolution},
	url = {http://softarch.usc.edu/~pooyan/publications/emparch_msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/emparch_msr15.pdf},
	author = {Duc Minh Le and Pooyan Behnamghader and Joshua Garcia{\textdaggerdbl} Daniel Link and Arman Shahbazian and Nenad Medvidovic}
}
@article {1746,
	title = {Evaluation of FLOSS by Analyzing Its Software Evolution:},
	journal = {Journal of Information Technology Research},
	volume = {8},
	year = {2015},
	month = {01/2015},
	pages = {62 - 81},
	abstract = {In today{\textquoteright}s world, management often rely on FLOSS (Free/Libre/Open Source Software) systems to run their organizations. However, the nature of FLOSS is different from the software they have been using in the last decades. Its development model is distributed, and its authors are diverse as many volunteers and companies may collaborate in the project. In this paper, we want to shed some light on how to evaluate a FLOSS system by looking at the Moodle platform, which is currently the most used learning management system among educational institutions worldwide. In contrast with other evaluation models that have been proposed so far, the one we present is based on retrieving historical information that can be obtained publicly from the Internet, allowing us to study its evolution. As a result, we will show how by using our methodology management can take informed decisions that lower the risk that organizations face when investing in a FLOSS system.  },
	keywords = {free software, LMS, moodle, open source, software engineering, software evaluation, software evolution},
	issn = {1938-7865},
	doi = {10.4018/JITR.2015010105},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Evaluation\%20of\%20FLOSS\%20by\%20Analyzing\%20its\%20Software\%20Evolution\%20-\%20An\%20Example\%20Using\%20the\%20Moodle\%20Platform.pdf},
	author = {Macho, H{\'e}ctor J. and Gregorio Robles and Gonz{\'a}lez-Barahona, Jesus M}
}
@inbook {1734,
	title = {Examining Usability Work and Culture in OSS},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {58-67},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Organizational culture has been recognized as an influential factor affecting the successes and failures of usability work in organizations; however, there is a lack of research on organizational culture in open source software (OSS) development. This paper shows that there are different kinds of cultures in OSS development projects and builds propositions on the relationship between culture and usability work in OSS development projects. Partly those are derived from the literature, partly from an exploratory empirical inquiry. We speculate whether there is an ideal culture type for usability work in OSS development or whether usability work should be modified to fit the different cultures of OSS development projects.
},
	keywords = {culture, empirical study, open source software, Usability},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_6},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_6},
	author = {Rajanen, Mikko and Iivari, Netta},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1741,
	title = {First Results About Motivation and Impact of License Changes in Open Source Projects},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {137-145},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and open source software is characterized by the freedoms and criteria that are warranted by specific licenses. These licenses describe the rights and duties of the licensors and licensees. However, a licensing change may be necessary in the life of an open source project to meet legal developments or to allow the implementation of new business models. This paper examines the motivations and impacts of license changes in open source projects. After a state of the art on the subject, a set of case studies where projects changed their license is presented. Then a set of motivations to change licenses, the ways to legally make this change, the problems caused by this change and a set of benefits of the license change are discussed.
},
	keywords = {Business model, Contributor agreement, intellectual property, license, open source},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_13},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_13},
	author = {Viseur, Robert and Gregorio Robles},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1732,
	title = {How Developers Acquire FLOSS Skills},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {23-32},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {With the increasing prominence of open collaboration as found in free/libre/open source software projects and other joint production communities, potential participants need to acquire skills. How these skills are learned has received little research attention. This article presents a large-scale survey (5,309 valid responses) in which users and developers of the beta release of a popular file download application were asked which learning styles were used to acquire technical and social skills. We find that the extent to which a person acquired the relevant skills through informal methods tends to be higher if the person is a free/libre/open source code contributor, while being a professional software developer does not have this effect. Additionally, younger participants proved more likely to make use of formal methods of learning. These insights will help individuals, commercial companies, educational institutions, governments and open collaborative projects decide how they promote learning.
},
	keywords = {competencies, Informal learning, Non-formal learning, open source, Skills, Software developer},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_3},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss-2015.pdf},
	author = {Barcomb, Ann and Grottke, Michael and Stauffert, Jan-Philipp and Dirk Riehle and Jahn, Sabrina},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@booklet {1781,
	title = {Lessons Learned from Applying Social Network Analysis on an Industrial Free/Libre/Open Source Software Ecosystem},
	year = {2015},
	abstract = {Many software projects are no longer done in-house by a single organization. Instead, we are in a new age where software is developed by a networked community of individuals and organizations, which base their relations to each other on mutual interest. Paradoxically, recent research suggests that software development can actually be jointly-developed by rival firms. For instance, it is known that the mobile-device makers Apple and Samsung kept collaborating in open source projects while running expensive patent wars in the court. Taking a case study approach, we explore how rival firms collaborate in the open source arena by employing a multi-method approach that combines qualitative analysis of archival data (QA) with mining software repositories (MSR) and Social Network Analysis (SNA). While exploring collaborative processes within the OpenStack ecosystem, our research contributes to Software Engineering research by exploring the role of groups, sub-communities and business models within a high-networked open source ecosystem. Surprising results point out that competition for the same revenue model (i.e., operating conflicting business models) does not necessary affect collaboration within the ecosystem. Moreover, while detecting the different sub-communities of the OpenStack community, we found out that the expected social tendency of developers to work with developers from same firm (i.e., homophony) did not hold within the OpenStack ecosystem. Furthermore, while addressing a novel, complex and unexplored open source case, this research also contributes to the management literature in coopetition strategy and high-tech entrepreneurship with a rich description on how heterogeneous actors within a high-networked ecosystem (involving individuals, startups, established firms and public organizations) joint-develop a complex infrastructure for big-data in the open source arena.},
	keywords = {business models, cloud computing, homophily, open source, Open-Coopetition, openstack, social network analysis, Software ecosystems},
	url = {http://arxiv.org/abs/1507.04587},
	author = {Teixeira, Jose and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@proceedings {1748,
	title = {Mining Component Repositories for Installability Issues},
	year = {2015},
	month = {05/2015},
	abstract = {Component repositories play an increasingly relevant
role in software life-cycle management, from software
distribution to end-user, to deployment and upgrade management.
Software components shipped via such repositories are
equipped with rich metadata that describe their relationship (e.g.,
dependencies and conflicts) with other components.
In this practice paper we show how to use a tool, distcheck,
that uses component metadata to identify all the components in
a repository that cannot be installed (e.g., due to unsatisfiable
dependencies), provides detailed information to help developers
understanding the cause of the problem, and fix it in the
repository.
We report about detailed analyses of several repositories: the
Debian distribution, the OPAM package collection, and Drupal
modules. In each case, distcheck is able to efficiently identify not
installable components and provide valuable explanations of the
issues. Our experience provides solid ground for generalizing the
use of distcheck to other component repositories.},
	keywords = {drupal, opam},
	url = {http://www.dicosmo.org/preprints/msr-2015-distcheck.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-2015-distcheck.pdf},
	author = {Abate, Pietro and Di Cosmo, Roberto and Gesbert, Louis and Fabrice Le Fessant and Ralf Treinen and Zacchiroli, Stefano}
}
@conference {barcomb:2015:multiple,
	title = {A multiple case study of small free software businesses as social entrepreneurships},
	booktitle = {Proceedings of the 11th International Symposium on Open Collaboration (OpenSym 2015)},
	year = {2015},
	abstract = {Free/libre and open source software are frequently described as a single community or movement. The difference between free software and open source ideology may influence founders, resulting in different types of companies being created. Specifically, the relationship between free/libre software ideology and social entrepreneurships is investigated. This paper presents seven case studies of businesses, five of which were founded by people who  identify with the free/libre software movement. The result is a theory that small businesses founded by free/libre software advocates have three characteristics of social entrepreneurships. First, social benefit is prioritized over wealth creation. Second, the business{\textquoteright}s social mission is not incidental but is furthered through its for-profit activities, rather than supported by the company{\textquoteright}s profits. Third, the company{\textquoteright}s success is defined in part by the success of its social mission Free/libre software entrepreneurs who recognize their activities as social entrepreneurships can benefit from the existing literature on the unique challenges faced by socially-oriented businesses.},
	keywords = {free software, open source software, public good, small business, social entrepreneurship, social ventures},
	url = {https://opus4.kobv.de/opus4-fau/frontdoor/index/index/docId/6334},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p100-barcomb.pdf},
	author = {Barcomb, Ann}
}
@inbook {1738,
	title = {A Qualitative Study on the Adoption of Open Source Software in Information Technology Outsourcing Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {103-113},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The purpose of this paper is to identify the influence of Outsourcing on Open source software (OSS) and further investigate the factors that impact the adoption of OSS in global Information Technology (IT) outsourcing organizations serviced by Indian IT services providers. This exploratory research adopted positivism research philosophy and qualitative approach. An in-depth interview was conducted with ten participants across IT outsourcing organizations, IT service providers, and OSS service providers. The results show that IT outsourcing was not found to have an impact on OSS adoption. However, eight factors including management support and OSS support availability was identified to influence OSS adoption. IT services providers can utilize this research model to increase their understanding of why some IT outsourcing organizations choose to adopt OSS, while seemingly similar ones facing similar market conditions do not.
},
	keywords = {Diffusion of innovation, Indian IT, IT outsourcing, open source software, OSS adoption, TOE},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_10},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_10},
	author = {Ramanathan, Lakshmanan and Iyer, Sundaresan Krishnan},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1740,
	title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {124-133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in.
},
	keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_12},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12},
	author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1737,
	title = {Smart Route Planning Using Open Data and Participatory Sensing},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {91-100},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Smart cities are not merely the infusion of technology into a city{\textquoteright}s infrastructure, but also require citizens interacting with their urban environment in a smart and informed manner. Transportation is key aspect of smart cities. In this paper, we present a smart route planning open-source system; SMART-GH utilizes open data and participatory sensing, where citizens actively participate in collecting data about the city in their daily environment, e.g., noise, air pollution, etc. SMART-GH then augments the routing logic with sensor data to answer queries such as {\textquoteleft}return the least noisy route{\textquoteright}. SMART-GH enables citizens to make smarter decisions about their daily commute, and subsequently improve their quality of life.
},
	keywords = {Open-data, open-source, Participatory sensing, Smart-city-routing},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_9},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nallur15.pdf},
	author = {Nallur, Vivek and Elgammal, Amal and Clarke, Siobh{\'a}n},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1736,
	title = {A Systematic Approach for Evaluating BPM Systems: Case Studies on Open Source and Proprietary Tools},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {81-90},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Business Process Management Systems (BPMS) provide support for modeling, developing, deploying, executing and evaluating business processes in an organization. Selecting a BPMS is not a trivial task, not only due to the many existing alternatives, both in the open source and proprietary realms, but also because it requires a thorough evaluation of its capabilities, contextualizing them in the organizational environment in which they will be used. In this paper we present a methodology to guide the systematic evaluation of BPMS that takes into account the specific needs of each organization. It provides a list of key characteristics of BPMS which are ranked by the organization and evaluated using test cases and quantitative criteria. We also present case studies of open source and proprietary BPMS evaluations following our proposal.
},
	keywords = {Business Process Management Systems (BPMS), Evaluation methodology, Open source and proprietary BPMS, Systematic approach},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_8},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_8},
	author = {Delgado, Andrea and Calegari, Daniel and Milanese, Pablo and Falcon, Renatta and Garc{\'\i}a, Esteban},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@booklet {1709,
	title = {Understanding and Supporting the Choice of an Appropriate Task to Start With In Open Source Software Communities },
	howpublished = {Hawaii International Conference on System Sciences 48},
	year = {2015},
	pages = {5299-5308},
	publisher = {IEEE},
	abstract = {Open Source Software (OSS) projects leverage the
contribution of outsiders. In fact, the sustainability of
many projects relies on retaining some of these
newcomers. Usually these communities do not
coordinate the work of the newcomers, who go to the
issue trackers and self-select a task to start with. We
found that {\textquotedblleft}finding a way to start{\textquotedblright} was reported as an
important issue by practitioners. To further investigate
this specific barrier, we conducted a qualitative
analysis with data obtained from semi-structured
interviews with 36 subjects from 14 different projects,
including newcomers and experienced members. We
used procedures of Grounded Theory {\textendash} open and axial
coding {\textendash} to analyze the data. We found that newcomers
are not confident enough to choose their initial task
and they need information about the tasks or direction
from the community to support choosing a task more
suitable for them. We also present a set of strategies
identified in the literature, interviews, and state-of-the practice
that can provide newcomers with such
information, enabling them to be more confident when
choosing their first tasks and collaborate with the
community. },
	keywords = {coordination, joining process, new developer, newcomers, onboarding, open source software, task selection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HICSS-48_present.pdf},
	author = {Steinmacher, Igor and Conte, Tayana and Gerosa, MarcoAur{\'e}lio}
}
@proceedings {1752,
	title = {Why Power Laws? An Explanation from Fine-Grained Code Changes},
	year = {2015},
	note = {"The data used in this section come from four open source Java projects. We used CVSANALY to collect data from their Git repositories."},
	abstract = {Throughout the years, empirical studies have found
power law distributions in various measures across many software
systems. However, surprisingly little is known about how
they are produced. What causes these power law distributions?
We offer an explanation from the perspective of fine-grained
code changes. A model based on preferential attachment and selforganized
criticality is proposed to simulate software evolution.
The experiment shows that the simulation is able to render power
law distributions out of fine-grained code changes, suggesting
preferential attachment and self-organized criticality are the
underlying mechanism causing the power law distributions in
software systems.},
	keywords = {Apache Maven, cvsanaly, eclipse, git, Google Guice, java, jedit, open source},
	url = {https://users.soe.ucsc.edu/~linzhp/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015.pdf},
	author = {Zhongpeng Lin and Jim Whitehead}
}
@proceedings {1573,
	title = {"A bit of code": How the Stack Overflow Community Creates Quality Postings},
	year = {2014},
	month = {01/2014},
	pages = {1425-1434},
	publisher = {IEEE Computer Society},
	abstract = {The Stack Overflow web site is an online community where programmers can ask and answer one another{\textquoteright}s questions, earning points and badges. The site offers guidance in the form of a Frequently Asked Questions (FAQ), beginning with "What kind of questions can I ask here?" The answer explains that "the best Stack Overflow questions have a bit of source code in them". This paper explores the role of source code and non-source code text on Stack Overflow in both questions and answers. The primary contribution of this paper is to provide a more detailed understanding of whether the presence of source code (and how much) actually will produce the "best" Stack Overflow questions or answers. A second contribution of this paper is to determine how the non-code portions of the text might also contribute the "best" Stack Overflow postings.  },
	keywords = {COLLABORATION, collaborative development, data mining, developer network, knowledge collaboration, open content, text mining},
	doi = {http://dx.doi.org/10.1109/HICSS.2014.185},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hicssSMFinalWatermark.pdf},
	author = {Squire, Megan and Funkhouser, Christian}
}
@inbook {1619,
	title = {The Census of the Brazilian Open-Source Community},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {202-211},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

During a long time, software engineering research has been trying to better understand open-source communities and uncover two fundamental questions: (i) who are the contributors and (i) why they contribute. Most of these researches focus on well-known OSS projects, but little is known about the OSS movement in emerging countries. In this paper, we attempt to fill this gap by presenting a picture of the Brazilian open-source contributor. To achieve this goal, we examined activities from more than 12,400 programmers on Github, during the period of a year. Subsequently, we correlate our findings with a survey that was answered by more than 1,000 active contributors. Our results show that exists an OSS trend in Brazil: most part of the contributors are active, performing around 30 contributions per year, and they contribute to OSS basically by altruism.
},
	keywords = {Brazilian OSS Community, github, OSS},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_30},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_30},
	author = {Pinto, Gustavo and Kamei, Fernando},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@article {9400325220140301,
	title = {COLLABORATION THROUGH OPEN SUPERPOSITION: A THEORY OF THE OPEN SOURCE WAY.},
	journal = {MIS Quarterly},
	volume = {38},
	number = {1},
	year = {2014},
	pages = {29 - A9},
	abstract = {This paper develops and illustrates the theory of collaboration through open superposition: the process of depositing motivationally independent layers of work on top of each other over time. The theory is developed in a study of community-based free and open source software (FLOSS) development, through a research arc of discovery (participant observation), replication (two archival case studies), and theorization. The theory explains two key findings: (1) the overwhelming majority of work is accomplished with only a single programmer working on any one task, and (2) tasks that appear too large for any one individual are more likely to be deferred until they are easier rather than being undertaken through structured team work. Moreover, the theory explains how working through open superposition can lead to the discovery of a work breakdown that results in complex, functionally interdependent, work being accomplished without crippling search costs. We identify a set of socio-technical},
	keywords = {COLLABORATION, COMPUTER programmers, COMPUTER programming, COMPUTER software, coordination, FREEWARE (Computer software), INFORMATION storage \& retrieval systems, open source software, research, socio-technical system},
	issn = {02767783},
	author = {Howison, James and Kevin Crowston}
}
@inbook {1605,
	title = {Crafting a Systematic Literature Review on Open-Source Platforms},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {113-122},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This working paper unveils the crafting of a systematic literature review on open-source platforms. The high-competitive mobile devices market, where several players such as Apple, Google, Nokia and Microsoft run a platforms- war with constant shifts in their technological strategies, is gaining increasing attention from scholars. It matters, then, to review previous literature on past platforms-wars, such as the ones from the PC and game-console industries, and assess its implications to the current mobile devices platforms-war. The paper starts by justifying the purpose and rationale behind this literature review on open-source platforms. The concepts of open-source software and computer-based platforms were then discussed both individually and in unison, in order to clarify the core-concept of {\textquotedblleft}open-source platform{\textquotedblright} that guides this literature review. The detailed design of the employed methodological strategy is then presented as the central part of this paper. The paper concludes with preliminary findings organizing previous literature on open-source platforms for the purpose of guiding future research in this area.
},
	keywords = {Ecosystems, FLOSS, open-source, Platforms, R\&D Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_16},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_16},
	author = {Teixeira, Jose and Baiyere, Abayomi},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Robles:2014:EDE:2597073.2597107,
	title = {Estimating Development Effort in Free/Open Source Software Projects by Mining Software Repositories: A Case Study of OpenStack},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {222{\textendash}231},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Because of the distributed and collaborative nature of free / open source software (FOSS) projects, the development effort invested in a project is usually unknown, even after the software has been released. However, this information is becoming of major interest, especially ---but not only--- because of the growth in the number of companies for which FOSS has become relevant for their business strategy. In this paper we present a novel approach to estimate effort by considering data from source code management repositories. We apply our model to the OpenStack project, a FOSS project with more than 1,000 authors, in which several tens of companies cooperate. Based on data from its repositories and together with the input from a survey answered by more than 100 developers, we show that the model offers a simple, but sound way of obtaining software development estimations with bounded margins of error.
},
	keywords = {effort estimation, free software, mining software repositories, open source, openstack},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597107},
	url = {http://doi.acm.org/10.1145/2597073.2597107},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles_0.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Cervig{\'o}n, Carlos and Capiluppi, Andrea and Izquierdo-Cort{\'a}zar, Daniel}
}
@proceedings {roblesestimating,
	title = {Estimating Development Effort in Free/Open Source Software Projects by Mining Software Repositories: A Case Study of OpenStack},
	year = {2014},
	month = {05/2014},
	abstract = {Because of the distributed and collaborative nature of free/open source software (FOSS) projects, the development effort invested in a project is usually unknown, even after the software has been released. However, this information is becoming of major interest, especially - but not only- because of the growth in the number of companies for which FOSS has become relevant for their business strategy. In this paper we present a novel approach to estimate effort by considering data from source code management repositories. We apply our model to the OpenStack project, a FOSS
project with more than 1,000 authors, in which several tens of companies cooperate. Based on data from its repositories and together with the input from a survey answered by more than 100 developers, we show that the model offers a simple, but sound way of obtaining software development estimations
with bounded margins of error.},
	keywords = {effort estimation, openstack},
	url = {http://gsyc.urjc.es/~grex/repro/2014-msr-effort/msr14-robles-estimating-effort.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr14-robles-estimating-effort.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jesus M and Cervig{\'o}n, Carlos and Capiluppi, Andrea}
}
@inbook {1615,
	title = {An Exploration of Code Quality in FOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {181-190},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

It is a widely held belief that Free/Open Source Software (FOSS) development leads to the creation of software with the same, if not higher quality compared to that created using proprietary software development models. However there is little research on evaluating the quality of FOSS code, and the impact of project characteristics such as age, number of core developers, code-base size, etc. In this exploratory study, we examined 110 FOSS projects, measuring the quality of the code and architectural design using code smells. We found that, contrary to our expectations, the overall quality of the code is not affected by the size of the code base, but that it was negatively impacted by the growth of the number of code contributors. Our results also show that projects with more core developers don{\textquoteright}t necessarily have better code quality.
},
	keywords = {Code Quality, FOSS, open source software, success metrics},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_26},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_26},
	author = {Ahmed, Iftekhar and Ghorashi, Soroush and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@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.}
}
@inbook {1617,
	title = {Flow Research SXP Agile Methodology for FOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {195-198},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This paper aims to explain a procedure that takes into account the different research processes carried out in developing an open-source, allowing control and management. This study is the SXP methodology applied in this type of project was carried out, allowing the validity of the basis of this research.
},
	keywords = {methodology SXP, open-source, production, research, Software},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_28},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_28},
	author = {Pe{\~n}alver Romero, GladysMarsi and Leyva Samada, LisandraIsabel and Abad, AbelMeneses},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1594,
	title = {How Do Social Interaction Networks Influence Peer Impressions Formation? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {31-40},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Due to their lack of physical interaction, Free and Open Source Software (FOSS) participants form impressions of their teammates largely based on sociotechnical mechanisms including: code commits, code reviews, mailing-lists, and bug comments. These mechanisms may have different effects on peer impression formation. This paper describes a social network analysis of the WikiMedia project to determine which type of interaction has the most favorable characteristics for impressions formation. The results suggest that due to lower centralization, high interactivity, and high degree of interactions between participants, the code review interactions have the most favorable characteristics to support impression formation among FOSS participants.},
	keywords = {COLLABORATION, FOSS, open source, OSS, social network analysis},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_4},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_4},
	author = {Bosu, Amiangshu and Carver, JeffreyC.},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Vasilescu:2014:SQS:2531602.2531659,
	title = {How Social Q\&A Sites Are Changing Knowledge Sharing in Open Source Software Communities},
	booktitle = {Proceedings of the 17th ACM Conference on Computer Supported Cooperative Work \&\#38; Social Computing},
	series = {CSCW {\textquoteright}14},
	year = {2014},
	pages = {342{\textendash}354},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Historically, mailing lists have been the preferred means for coordinating development and user support activities. With the emergence and popularity growth of social Q\&A sites such as the StackExchange network (e.g., StackOverflow), this is beginning to change. Such sites offer different socio-technical incentives to their participants than mailing lists do, e.g., rich web environments to store and manage content collaboratively, or a place to showcase their knowledge and expertise more vividly to peers or potential recruiters. A key difference between StackExchange and mailing lists is gamification, i.e., StackExchange participants compete to obtain reputation points and badges. In this paper, we use a case study of R (a widely-used tool for data analysis) to investigate how mailing list participation has evolved since the launch of StackExchange. Our main contribution is the assembly of a joint data set from the two sources, in which participants in both the texttt{r-help} mailing list and StackExchange are identifiable. This permits their activities to be linked across the two resources and also over time. With this data set we found that user support activities show a strong shift away from texttt{r-help}. In particular, mailing list experts are migrating to StackExchange, where their behaviour is different. First, participants active both on texttt{r-help} and on StackExchange are more active than those who focus exclusively on only one of the two. Second, they provide faster answers on StackExchange than on texttt{r-help}, suggesting they are motivated by the emph{gamified} environment. To our knowledge, our study is the first to directly chart the changes in behaviour of specific contributors as they migrate into gamified environments, and has important implications for knowledge management in software engineering.},
	keywords = {a, crowdsourced knowledge, gamification., mailing lists, open source, social q\&\#38},
	isbn = {978-1-4503-2540-0},
	doi = {10.1145/2531602.2531659},
	url = {http://doi.acm.org/10.1145/2531602.2531659},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw14.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Devanbu, Prem and Filkov, Vladimir}
}
@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla{\textquoteright}s automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009\% of crash reports end up in a bug report, but as many as 2.33\% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@inbook {1612,
	title = {A Layered Approach to Managing Risks in OSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {168-171},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

In this paper, we propose a layered approach to managing risks in OSS projects. We define three layers: the first one for defining risk drivers by collecting and summarising available data from different data sources, including human-provided contextual information; the second layer, for converting these risk drivers into risk indicators; the third layer for assessing how these indicators impact the business of the adopting organisation. The contributions are: 1) the complexity of gathering data is isolated in one layer using appropriate techniques, 2) the context needed to interpret this data is provided by expert involvement evaluating risk scenarios and answering questionnaires in a second layer, 3) a pattern-based approach and risk reasoning techniques to link risks to business goals is proposed in the third layer.
},
	keywords = {Layered Model, open source, OSS, Risk Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_23},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_23},
	author = {Franch, Xavier and Kenett, Ron and Mancinelli, Fabio and Susi, Angelo and Ameller, David and Ben-Jacob, Ron and Siena, Alberto},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Yamashita:2014:MSO:2597073.2597116,
	title = {Magnet or Sticky? An OSS Project-by-project Typology},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {344{\textendash}347},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {For Open Source Software (OSS) projects, retaining existing contributors and attracting new ones is a major concern. In this paper, we expand and adapt a pair of population migration metrics to analyze migration trends in a collection of open source projects. Namely, we study: (1) project stickiness, i.e., its tendency to retain existing contributors and (2) project magnetism, i.e., its tendency to attract new contributors. Using quadrant plots, we classify projects as attractive (highly magnetic and sticky), stagnant (highly sticky, weakly magnetic), fluctuating (highly magnetic, weakly sticky), or terminal (weakly magnetic and sticky). Through analysis of the MSR challenge dataset, we find that: (1) quadrant plots can effectively identify at-risk projects, (2) stickiness is often motivated by professional activity and (3) transitions among quadrants as a project ages often coincides with interesting events in the evolution history of a project.
},
	keywords = {Developer migration, Magnet, mining challenge, msr challenge, open source, Sticky},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597116},
	url = {http://doi.acm.org/10.1145/2597073.2597116},
	attachments = {https://flosshub.org/sites/flosshub.org/files/yamashita.pdf},
	author = {Yamashita, Kazuhiro and McIntosh, Shane and Kamei, Yasutaka and Ubayashi, Naoyasu}
}
@unpublished {1799,
	title = {Measuring the Health of Open Source Software Ecosystems: Moving Beyond the Scope of Project Health},
	year = {2014},
	abstract = {Background. The livelihood of an open source ecosystem is important to different ecosystem participants: software developers, end-users, investors, and participants want to know whether their ecosystem is healthy and performing well. Currently, there exists no working operationalization available that can be used to determine the health of open source ecosystems. Health is typically looked at from a project scope, not from an ecosystem scope. Objectives. With such an operationalization, stakeholders can make better decisions on whether to invest in an ecosystem: developers can select the healthiest ecosystem to join, keystone organizers can establish which governance techniques are effective, and end-users can select ecosystems that are robust, will live long, and prosper. Method. Design research is used to create the health operationalization. The evaluation step is done using four ecosystem health projects from literature. Results. The Open Source Ecosystem Health Operationalization is provided, which establishes the health of a complete software ecosystem, using the data from collections of open source projects that belong to the ecosystem. Conclusion. The groundwork is done, by providing a summary of research challenges, for more research in ecosystem health. With the operationalization in hand, re- searchers no longer need to start from scratch when researching open source ecosystems{\textquoteright} health.},
	keywords = {open source ecosystems, Software ecosystem health, Software repository mining},
	url = {https://www.dropbox.com/s/borc730uw32kkzp/SECOhealth.pdf?dl=0},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SECOhealth\%20\%281\%29.pdf},
	author = {Slinger Jansen}
}
@conference {Eckhardt:2014:MMO:2642803.2642810,
	title = {The Merits of a Meritocracy in Open Source Software Ecosystems},
	booktitle = {Proceedings of the 2014 European Conference on Software Architecture Workshops},
	series = {ECSAW {\textquoteright}14},
	year = {2014},
	pages = {7:1{\textendash}7:6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The Eclipse open source ecosystem has grown from a small internal IBM project to one of the biggest Integrated Development Environments in the market. Open source communities and ecosystems do not follow the standard governance strategies typically used in large organizations. A meritocracy is a frequently occurring form of governance on different levels in open ecosystems. In this paper we investigate how this form of governance influences the health of projects within the Eclipse ecosystem in terms of the amount of commits within each month. We analyzed the hierarchy of Eclipse, how merits are conceptualized within the ecosystem and the effect of the appointments of mentors and project leads on the amount of commits. From our research, we can conclude that this system is not always as fair as it seems; merits are only a benefit in some cases.},
	keywords = {Ecosystem Health, Meritocracy, open source, Software ecosystems},
	isbn = {978-1-4503-2778-7},
	doi = {10.1145/2642803.2642810},
	url = {http://doi.acm.org/10.1145/2642803.2642810},
	author = {Eckhardt, Evert and Kaats, Erwin and Slinger Jansen and Alves, Carina}
}
@conference {Beller:2014:MCR:2597073.2597082,
	title = {Modern Code Reviews in Open-source Projects: Which Problems Do They Fix?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {202{\textendash}211},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Code review is the manual assessment of source code by humans, mainly intended to identify defects and quality problems. Modern Code Review (MCR), a lightweight variant of the code inspections investigated since the 1970s, prevails today both in industry and open-source software (OSS) systems. The objective of this paper is to increase our understanding of the practical benefits that the MCR process produces on reviewed source code. To that end, we empirically explore the problems fixed through MCR in OSS systems. We manually classified over 1,400 changes taking place in reviewed code from two OSS projects into a validated categorization scheme. Surprisingly, results show that the types of changes due to the MCR process in OSS are strikingly similar to those in the industry and academic systems from literature, featuring the similar 75:25 ratio of maintainability-related to functional problems. We also reveal that 7{\textendash}35\% of review comments are discarded and that 10{\textendash}22\% of the changes are not triggered by an explicit review comment. Patterns emerged in the review data; we investigated them revealing the technical factors that influence the number of changes due to the MCR process. We found that bug-fixing tasks lead to fewer changes and tasks with more altered files and a higher code churn have more changes. Contrary to intuition, the person of the reviewer had no impact on the number of changes.
},
	keywords = {code review, defects, open source software},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597082},
	url = {http://doi.acm.org/10.1145/2597073.2597082},
	attachments = {https://flosshub.org/sites/flosshub.org/files/beller.pdf},
	author = {Beller, Moritz and Bacchelli, Alberto and Zaidman, Andy and Juergens, Elmar}
}
@conference {Guo:2014:ODC:2597073.2597094,
	title = {Oops! Where Did That Code Snippet Come from?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {52{\textendash}61},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A kernel oops is an error report that logs the status of the Linux kernel at the time of a crash. Such a report can provide valuable first-hand information for a Linux kernel maintainer to conduct postmortem debugging. Recently, a repository has been created that systematically collects kernel oopses from Linux users. However, debugging based on only the information in a kernel oops is difficult. We consider the initial problem of finding the offending line, i.e., the line of source code that incurs the crash. For this, we propose a novel algorithm based on approximate sequence matching, as used in bioinformatics, to automatically pinpoint the offending line based on information about nearby machine-code instructions, as found in a kernel oops. Our algorithm achieves 92\% accuracy compared to 26\% for the traditional approach of using only the oops instruction pointer.},
	keywords = {debugging, linux kernel, oops, sequence alignment},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597094},
	url = {http://doi.acm.org/10.1145/2597073.2597094},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guo.pdf},
	author = {Guo, Lisong and Lawall, Julia and Muller, Gilles}
}
@inbook {1603,
	title = {A Performance Analysis of Wireless Mesh Networks Implementations Based on Open Source Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {107-110},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Wireless mesh networks (WMNs) have emerged as a promising technology, capable of provide broadband connectivity at low cost. Implementations based on Open Source Software of these networks offer advantages for providing broadband networking communications in scenarios where cabling is too expensive or prohibitive such as rural environments. In this paper we evaluate the performance of small scale wireless mesh WMN routing protocols for WMNs: B.A.T.M.A.N. Advanced and the 802.11s standard. We also compare an OpenFlow controller implemented over the WMN, verifying their bandwidth, datagram loss and jitter.
},
	keywords = {network performance, Open Source Software for research and innovation, OpenFlow, OpenWRT, Wireless Mesh Networks},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_14},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_14},
	author = {Armuelles Voinov, Iv{\'a}n and Cede{\~n}o, AidelenChung and Chung, Joaqu{\'\i}n and Gonz{\'a}lez, Grace},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@article {1745,
	title = {SENTIMENT ANALYSIS OF FREE/OPEN SOURCE DEVELOPERS: PRELIMINARY FINDINGS FROM A CASE STUDY},
	journal = {Revista Eletr{\^o}nica de Sistemas de Informa{\c c}{\~a}o},
	volume = {13},
	year = {2014},
	month = {08/2014},
	abstract = {Software development is a human intensive activity. And as such, how developers face their tasks is of major importance. In an environment such as the one that is common in FOSS (free/open source software) projects where professionals (i.e., paid developers) share the development effort with volunteers, the morale of the development and user community is of major importance. In this paper, we present a preliminary analysis using sentiment analysis techniques to a FOSS project. We therefore mine the mailing list of a project and apply these techniques to the most relevant participants. Although the application is at this time limited, we hope that this experience can be of benefit in the future to determine situations that may affect the developers or the project, such as low productivity, developer abandonment, project forking, etc. },
	keywords = {developer productivity, FLOSS, mailing lists, natural language processing, openSUSE, sentiment analysis, software development; software repository mining},
	doi = {10.5329/RESI.2014.1302006},
	url = {http://189.16.45.2/ojs/index.php/reinfo/article/view/1677},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1677-6732-1-PB.pdf},
	author = {Rousinopoulos, Athanasios-Ilias and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@conference {Vasilescu:2014:SDH:2556420.2556833,
	title = {Software Developers Are Humans, Too!},
	booktitle = {Proceedings of the Companion Publication of the 17th ACM Conference on Computer Supported Cooperative Work \&\#38; Social Computing},
	series = {CSCW Companion {\textquoteright}14},
	year = {2014},
	pages = {97{\textendash}100},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source communities can be seen as knowledge-sharing ecosystems: participants learn from the community and from one another, and share their knowledge through contributions to the source code repositories or by offering support to users. With the emergence and growing popularity of social media sites targeting software developers (e.g., StackOverflow, GitHub), the paths through which knowledge flows within open-source software knowledge-sharing ecosystems are also beginning to change. My dissertation research seeks to raise our understanding of these changes.},
	keywords = {human aspects, open-source, software developers},
	isbn = {978-1-4503-2541-7},
	doi = {10.1145/2556420.2556833},
	url = {http://doi.acm.org/10.1145/2556420.2556833},
	author = {Vasilescu, Bogdan}
}
@conference {Padhye:2014:SEC:2597073.2597113,
	title = {A Study of External Community Contribution to Open-source Projects on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {332{\textendash}335},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source software projects are primarily driven by community contribution. However, commit access to such projects{\textquoteright} software repositories is often strictly controlled. These projects prefer to solicit external participation in the form of patches or pull requests. In this paper, we analyze a set of 89 top-starred GitHub projects and their forks in order to explore the nature and distribution of such community contribution. We first classify commits (and developers) into three categories: core, external and mutant, and study the relative sizes of each of these classes through a ring-based visualization. We observe that projects written in mainstream scripting languages such as JavaScript and Python tend to include more external participation than projects written in upcoming languages such as Scala. We also visualize the geographic spread of these communities via geocoding. Finally, we classify the types of pull requests submitted based on their labels and observe that bug fixes are more likely to be merged into the main projects as compared to feature enhancements.
},
	keywords = {community participation, core committers, external contribution, mining challenge, mining software repositories, msr challenge, Open-source software, pull requests},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597113},
	url = {http://doi.acm.org/10.1145/2597073.2597113},
	author = {Padhye, Rohan and Mani, Senthil and Sinha, Vibha Singhal}
}
@conference {Teixeira:2014:UCO:2641580.2641627,
	title = {Understanding Coopetition in the Open-Source Arena: The Cases of WebKit and OpenStack},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {39:1{\textendash}39:5},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In an era of software crisis, the move of firms towards distributed software development teams is being challenged by emerging collaboration issues. On this matter, the open-source phenomenon may shed some light, as successful cases on distributed collaboration in the open-source community have been recurrently reported. In our research we explore collaboration networks in the WebKit and OpenStack high-networked open-source projects, by mining their source-code version-control-systems data with Social Network Analysis (SNA). Our approach allows us to observe how key events in the industry affect open-source collaboration networks over time. With our findings, we highlight the explanatory power from network visualizations capturing the collaborative dynamics of high-networked software projects over time. Moreover, we argue that competing companies that sell similar products in the same market, can collaborate in the open-source community while publicly manifesting intense rivalry (e.g. Apple vs Samsung patent-wars). After integrating our findings with the current body of theoretical knowledge in management strategy, economics, strategic alliances and coopetition, we propose the novel notion of open-coopetition, where rival firms collaborate with competitors in the open-source community. We argue that classical coopetition management theories do not fully explain the competitive and collaborative issues that are simultaneously present and interconnected in the WebKit and OpenStack open-source communities. We propose the development of the novel open-coopetition theory for a better understanding on how rival-firms collaborate with competitors by open-source manners.
},
	keywords = {COLLABORATION, Competition, Coopetition, Ecosystems, FLOSS, Open-Coopetition, open-source, OSS, Strategic Alliances},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641627},
	url = {http://doi.acm.org/10.1145/2641580.2641627},
	author = {Teixeira, Jose}
}
@inbook {1604,
	title = {Use of Open Software Tools for Data Offloading Techniques Analysis on Mobile Networks},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {111-112},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This research aims to highlight the benefits of using free software based tools for studying a LTE mobile network with realistic parameters. We will overload this LTE network and offload it through data offloading techniques such as small cells and WiFi offload. For this research, discreteevent open software network simulator ns3 will be implemented. Ns3 is a network simulator based on the programming language C++, and has all the necessary libraries to simulate an LTE and WiFi network.
},
	keywords = {Data Offloading, LTE, ns3, OSS for research and education, small cells, WiFi},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_15},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_15},
	author = {Koo, Jos{\'e}M. and Espino, JuanP. and Armuelles, Iv{\'a}n and Villarreal, Rub{\'e}n},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Barcomb:2014:VAR:2641580.2641628,
	title = {Volunteer Attraction and Retention in Open Source Communities},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {40:1{\textendash}40:2},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The importance of volunteers in open source has led to the position of community manager becoming more common in foundations and projects. Yet the advice for volunteer management and retention is fragmented, incomplete, contradictory, and has not been empirically examined. Our aim is to fill this gap by creating a comprehensive guidebook of best practices drawing from open source practitioner guides and general literature on volunteering, and to subject a subset of practices to empirical study. A method for evaluating volunteer attrition in terms of value to the organization will also be developed.
},
	keywords = {Community Management, FLOSS, open source, Recruitment, Service Duration, Volunteer Management, Volunteer Retention, Volunteers},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641628},
	url = {http://doi.acm.org/10.1145/2641580.2641628},
	author = {Barcomb, Ann}
}
@inbook {1626,
	title = {When Are OSS Developers More Likely to Introduce Vulnerable Code Changes? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {234-236},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We analyzed peer code review data of the Android Open Source Project (AOSP) to understand whether code changes that introduce security vulnerabilities, referred to as vulnerable code changes (VCC), occur at certain intervals. Using a systematic manual analysis process, we identified 60 VCCs. Our results suggest that AOSP developers were more likely to write VCCs prior to AOSP releases, while during the post-release period they wrote fewer VCCs.
},
	keywords = {FOSS, open source, OSS, security, vulnerability},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_37},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_37},
	author = {Bosu, Amiangshu and Carver, JeffreyC. and Hafiz, Munawar and Hilley, Patrick and Janni, Derek},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@book {1546,
	title = {A Dual Model of Open Source License Growth},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {uses ohloh snapshot, march 2008},
	pages = {245 - 256},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Every open source project needs to decide on an open source license. This decision is of high economic relevance: Just which license is the best one to help the project grow and attract a community? The most common question is: Should the project choose a restrictive (reciprocal) license or a more permissive one? As an important step towards answering this question, this paper analyses actual license choice and correlated project growth from ten years of open source projects. It provides closed analytical models and finds that around 2001 a reversal in license choice occurred from restrictive towards permissive licenses.
},
	keywords = {ohloh},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss2013.hofmann.pdf},
	author = {Hofmann, Gottfried and Dirk Riehle and Carsten Kolassa and Mauerer, Wolfgang},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {abdouSEKE2013,
	title = {{Managing Corrective Actions to Closure in Open Source Software Test Process}},
	booktitle = {The 25th International Conference on Software Engineering and Knowledge Engineering (SEKE 2013)},
	year = {2013},
	pages = {306{\textendash}311},
	address = {Boston, USA},
	abstract = {In assessing test process maturity, one of the goals is to manage disciplinary issues. Managing corrective actions to closure is known to aid software quality assurance, in general, and testing process activities, in particular. In this paper, a framework for software testing assessment, namely OSS-TPA, that aims to evaluate corrective actions in OSS test process, is proposed. The OSS-TPA framework is based on earlier studies and relies on a conceptual model for test process activities in OSS development. Using success factors in OSS development, the relationship between the maturity of managing corrective actions and the adoption of OSS is investigated.},
	keywords = {open source software, software engineering, software quality, Software testing, Test Process Improvement.},
	url = {http://index.ksi.edu/conf/seke/2013/cr/282.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/282.pdf},
	author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj}
}
@article {IJC397,
	title = {Preliminary steps toward a general theory of internet-based collective-action in digital information commons: Findings from a study of open source software projects},
	journal = {International Journal of the Commons},
	volume = {7},
	number = {2},
	year = {2013},
	abstract = {This paper presents some of the findings from a 5-year empirical study of FOSS (free/libre and open source software) commons, completed in 2011. FOSS projects are Internet-based common property regimes where the project source code is developed over the Internet. The resulting software is generally distributed with a license that provides users with the freedoms to access, use, read, modify and redistribute the software. In this study we used three different and very large datasets (approximately 107,000; 174,000 and 1400 cases respectively) with information on FOSS projects residing in Sourceforge.net, one of the largest, if not the largest, FOSS repository in the world. We employ various quantitative methods to uncover factors that lead some FOSS projects to ongoing collaborative success, while others become abandoned. After presenting some of our study{\textquoteright}s results, we articulate the collaborative {\textquotedblleft}story{\textquotedblright} of FOSS that emerged. We close the paper by discussing some key findings that can contribute to a general theory of Internet-based collective-action and FOSS-like forms of digital online commons.},
	keywords = {collaborative success and abandonment, common property regime, digital information commons, flossmole, Free/libre software, open source software, sourceforge, srda},
	issn = {1875-0281},
	url = {http://www.thecommonsjournal.org/index.php/ijc/article/view/URN\%3ANBN\%3ANL\%3AUI\%3A10-1-114926},
	author = {Charles Schweik and Robert English}
}
@conference {Scacchi:2013:PSO:2486046.2486068,
	title = {Processes in Securing Open Architecture Software Systems},
	booktitle = {Proceedings of the 2013 International Conference on Software and System Process},
	series = {ICSSP 2013},
	year = {2013},
	pages = {126{\textendash}135},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our goal is to identify and understand issues that arise in the development and evolution processes for securing open architecture (OA) software systems. OA software systems are those developed with a mix of closed source and open source software components that are configured via an explicit system architectural specification. Such a specification may serve as a reference model or product line model for a family of concurrently sustained OA system versions/variants. We employ a case study focusing on an OA software system whose security must be continually sustained throughout its ongoing development and evolution. We limit our focus to software processes surrounding the architectural design, continuous integration, release deployment, and evolution found in the OA system case study. We also focus on the role automated tools, software development support mechanisms, and development practices play in facilitating or constraining these processes through the case study. Our purpose is to identify issues that impinge on modeling (specification) and integration of these processes, and how automated tools mediate these processes, as emerging research problems areas for the software process research community. Finally, our study is informed by related research found in the prescriptive versus descriptive practice of these processes and tool usage in studies of conventional and open source software development projects.},
	keywords = {configuration, continuous software development, Open architecture, process integration, process modeling, security},
	isbn = {978-1-4503-2062-7},
	doi = {10.1145/2486046.2486068},
	url = {http://doi.acm.org/10.1145/2486046.2486068},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi-Alspaugh-ICSSP13.pdf},
	author = {Walt Scacchi and Alspaugh, Thomas A.}
}
@article {1565,
	title = {Towards base rates in software analytics},
	journal = {Science of Computer Programming},
	year = {2013},
	month = {11/2013},
	abstract = {Nowadays a vast and growing body of open source software (OSS) project data is publicly available on the internet. Despite this public body of project data, the field of software analytics has not yet settled on a solid quantitative base for basic properties such as code size, growth, team size, activity, and project failure. What is missing is a quantification of the base rates of such properties, where other fields (such as medicine) commonly rely on base rates for decision making and the evaluation of experimental results. The lack of knowledge in this area impairs both research activities in the field of software analytics and decision making on software projects in general. This paper contributes initial results of our research towards obtaining base rates using the data available at Ohloh (a large-scale index of OSS projects). Zooming in on the venerable {\textquoteleft}lines of code{\textquoteright} metric for code size and growth, we present and discuss summary statistics and identify further research challenges.},
	keywords = {ohloh},
	issn = {01676423},
	doi = {10.1016/j.scico.2013.11.023},
	url = {http://www.sciencedirect.com/science/article/pii/S0167642313003079},
	author = {Bruntink, Magiel}
}
@article {1554,
	title = {Using software analytics to understand how companies interact in free software communities},
	journal = {IEEE Software},
	year = {2013},
	month = {2013},
	pages = {1 - 1},
	abstract = {

Free, open source software development communities may become large and complex. They may also be a focus of interest for competing companies relying on their outcomes, with their employees joining the development and maintenance effort. In those cases it is specially important for both companies and communities to understand how this collaboration is working, and how it matches their policies and expectations. In this paper we show two cases (OpenStack and WebKit) which we have studied using analytics techniques on the data obtained from their software development repositories. From them, we conclude that analytics on this data can improve the factual knowledge about how development communities are performing in aspects which are of interest to companies, and fundamental to ensure transparency and fairness.
},
	keywords = {openstack, webkit},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Gonzalez-Barahona, Jesus and Izquierdo, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@proceedings {1439,
	title = {A Comprehensive Study of Software Forks: Dates, Reasons and Outcomes},
	volume = {378},
	year = {2012},
	pages = {1-14},
	publisher = {IFIP AICT},
	abstract = {Summary. In general it is assumed that a software product evolves within the authoring company or group of developers that develop the project. However, in some cases different groups of developers make the software evolve in different directions, a situation which is commonly known as a fork. In the case of free software, although forking is a practice that is considered as a last resort, it is inherent to the four freedoms. This paper tries to shed some light on the practice of forking. Therefore, we have identified significant forks, several hundreds in total, and have studied them in depth. Among the issues that have been analyzed for each fork is the date when the forking occurred, the reason of the fork, and the outcome of the fork, i.e., if the original or the forking project are still developed. Our investigation shows, among other results, that forks occur in every software domain, that they have become more frequent in recent years, and that very few forks merge with the original project.},
	keywords = {forking, forks, free software, Legal, open source, social, software evolution, sustainability},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_0.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@conference {1375,
	title = {The Effects of Diversity in Global, Distributed Collectives: A Study of Open Source Project Success},
	booktitle = {Information Systems Research},
	year = {2012},
	abstract = {Diversity is a defining characteristic of global collectives facilitated by the Internet. Though substantial evidence suggests that diversity has profound implications for a variety of outcomes including performance, member engagement, and withdrawal behavior, the effects of diversity have been predominantly investigated in the context of organizational workgroups or virtual teams. We use a diversity lens to study the success of non-traditional virtual work groups exemplified by open source software (OSS) projects. Building on the diversity literature, we propose that three types of diversity (separation, variety and disparity) influence two critical outcomes for OSS projects: community engagement and market success. We draw on the OSS literature to further suggest that the effects of diversity on market success are moderated by the application development stage. We instantiate the operational definitions of three forms of diversity to the unique context of open source projects. Using archival data from 357 projects hosted on SourceForge, we find that disparity diversity, reflecting variation in participants{\textquoteleft} contribution-based reputation, is positively associated with success. The impact of separation diversity, conceptualized as culture and measured as diversity in the spoken language and country of participants, has a negative impact on community engagement but an unexpected positive effect on market success. Variety diversity, reflected in dispersion in project participant roles, positively influences community engagement and market success. The impact of diversity on market success is conditional on the development stage of the project. We discuss how the study{\textquoteleft}s findings advance the literature on antecedents of OSS success, expand our theoretical understanding of diversity, and present the practical implications of the results for managers of distributed collectives.},
	keywords = {diversity, global collectives, open source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/isr_2012.pdf},
	author = {Daniel, Sherae L. and Ritu Agarwal and Stewart, Katherine J.}
}
@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}
}
@proceedings {1295,
	title = {Aspects of an Open Source Software Sustainable Life Cycle},
	year = {2011},
	month = {10/2011},
	pages = {325-329},
	publisher = {Springer},
	abstract = {In this paper we present a literature overview about OSS sustainability, considering not only financial resources, but also community growth, source code and tools management. Based on these aspects, we define an OSS life cycle that may contribute to OSS projects sustainability.},
	keywords = {Financial Resources, OSS Communities, OSS Sustainability, software maintenance},
	author = {Arantes, Flavia Linhalis and Freire, Fernanda Maria Pereira}
}
@article {1383,
	title = {A comparative study of challenges in integrating Open Source Software and Inner Source Software},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {12/2011},
	pages = {1319 - 1336},
	abstract = {Context

Several large software-developing organizations have adopted Open Source Software development (OSSD) practices to develop in-house components that are subsequently integrated into products. This phenomenon is also known as {\textquotedblleft}Inner Source{\textquotedblright}. While there have been several reports of successful cases of this phenomenon, little is known about the challenges that practitioners face when integrating software that is developed in such a setting.
Objective

The objective of this study was to shed light on challenges related to building products with components that have been developed within an Inner Source development environment.
Method

Following an initial systematic literature review to generate seed category data constructs, we performed an in-depth exploratory case study in an organization that has a significant track record in the implementation of Inner Source. Data was gathered through semi-structured interviews with participants from a range of divisions across the organization. Interviews were transcribed and analyzed using qualitative data analysis techniques.
Results

We have identified a number of challenges and approaches to address them, and compared the findings to challenges related to development with OSS products reported in the literature. We found that many challenges identified in the case study could be mapped to challenges related to integration of OSS.
Conclusion

The results provide important insights into common challenges of developing with OSS and Inner Source and may help organizations to understand how to improve their software development practices by adopting certain OSSD practices. The findings also identify the areas that need further research.
Highlights

► We performed a case study that has adopted Open Source development practices. ► We studied the challenges encountered and approaches taken by the organization. ► We performed a systematic review to identify challenges related to Open Source. ► We compared the findings from the review to the findings from the case study. ► Most identified challenges could be mapped to the findings from the literature.},
	keywords = {Open Source Software;     Inner Source;     Software development;     Challenges;     Case study;     Empirical studies},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.06.007},
	url = {http://www.sciencedirect.com/science/article/pii/S095058491100142X},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris and Fitzgerald, Brian}
}
@article {1418,
	title = {Effort estimation of FLOSS projects: a study of the Linux kernel},
	journal = {Empirical Software Engineering},
	year = {2011},
	pages = {1-29},
	abstract = {Empirical research on Free/Libre/Open Source Software (FLOSS) has shown that developers tend to cluster around two main roles: {\textquotedblleft}core{\textquotedblright} contributors differ from {\textquotedblleft}peripheral{\textquotedblright} developers in terms of a larger number of responsibilities and a higher productivity pattern. A further, cross-cutting characterization of developers could be achieved by associating developers with {\textquotedblleft}time slots{\textquotedblright}, and different patterns of activity and effort could be associated to such slots. Such analysis, if replicated, could be used not only to compare different FLOSS communities, and to evaluate their stability and maturity, but also to determine within projects, how the effort is distributed in a given period, and to estimate future needs with respect to key points in the software life-cycle (e.g., major releases). This study analyses the activity patterns within the Linux kernel project, at first focusing on the overall distribution of effort and activity within weeks and days; then, dividing each day into three 8-hour time slots, and focusing on effort and activity around major releases. Such analyses have the objective of evaluating effort, productivity and types of activity globally and around major releases. They enable a comparison of these releases and patterns of effort and activities with traditional software products and processes, and in turn, the identification of company-driven projects (i.e., working mainly during office hours) among FLOSS endeavors. The results of this research show that, overall, the effort within the Linux kernel community is constant (albeit at different levels) throughout the week, signalling the need of updated estimation models, different from those used in traditional 9am{\textendash}5pm, Monday to Friday commercial companies. It also becomes evident that the activity before a release is vastly different from after a release, and that the changes show an increase in code complexity in specific time slots (notably in the late night hours), which will later require additional maintenance efforts.},
	keywords = {complexity, effort estimation, Effort models, mining software repositories, open source software},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9191-7},
	url = {http://www.springerlink.com/content/612r616k8t52m867/fulltext.html},
	author = {Capiluppi, Andrea and Izquierdo-Cort{\'a}zar, Daniel}
}
@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 {1298,
	title = {Health Informatics: The Relevance of Open Source and Multilevel Modeling},
	year = {2011},
	month = {10/2011},
	pages = {338-347},
	publisher = {Springer},
	abstract = {Health information features significant spatial-temporal and domain complexities, which brings challenges to the implementation of patient-centered, interoperable and semantically coherent healthcare information systems. This position paper supports the idea that the multilevel modeling approach is essential to ensure interoperability at the semantic level, but true interoperability is only achieved by the adoption of open standards, and open source implementations are needed for promote competition based on software quality. The Multilevel Healthcare Information Modelling (MLHIM) specifications are presented as the fully open source multilevel modeling reference implementation, and best practices for the development of multilevel- based open source healthcare applications are suggested.},
	keywords = {Health informatics, multilevel modeling, open source software},
	author = {Cavalini, Luciana T. and Cook, Timothy W.}
}
@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}
}
@conference {Sethanandha:2011:IOS:1985793.1986018,
	title = {Improving open source software patch contribution process: methods and tools},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	pages = {1134{\textendash}1135},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The patch contribution process (PCP) is very important to the sustainability of OSS projects. Nevertheless, there are several issues on patch contribution in mature OSS projects, which include time consuming process, lost and ignored patches, slow review process. These issues are recognized by researchers and OSS projects, but have not been addressed. In this dissertation, I apply Kanban method to guide process improvement and tools development to reduce PCP cycle time.},
	keywords = {coordination, free software, kanban, lean methods, open source software, patches, productivity},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1986018},
	url = {http://doi.acm.org/10.1145/1985793.1986018},
	author = {Bhuricha Deen Sethanandha}
}
@proceedings {1284,
	title = {Libre Software as an Innovation Enabler in India: Experiences of a Bangalorian Software SME},
	year = {2011},
	month = {10/2011},
	pages = {220-232},
	publisher = {Springer},
	abstract = {Free/Libre and open source software (FLOSS) has been advocated for its presumed capacity to support native software industries in developing countries. It is said to create new spaces for exploration and to lower entry barriers to mature software markets, for example. However, little empirical research has been conducted concerning FLOSS business in a developing country setting and, thus, there is not much evidence to support or refute these claims. This paper presents a business case study conducted in India, a country branded as a {\textquoteright}software powerhouse{\textquoteright} of the developing world. The findings show how FLOSS has opened up significant opportunities for the case company, especially in terms of improving its innovative capability and upgrading in the software value chain. On the other hand, they also highlight some challenges to FLOSS involvement that rise specifically from the Indian context.},
	keywords = {free software, India, INNOVATION, open source, software business},
	author = {Henttonen, Katja}
}
@proceedings {1281,
	title = {License Update and Migration Processes in Open Source Software Projects},
	year = {2011},
	note = {"The case studies in this report are part of an ongoing, multi-year research project discovering and modeling open source software processes. Our research methodology is ethnographically informed, applying a grounded theory to the analysis of artifacts found in OSS projects. The primary data sources in this study come from mailing list archives of the Apache and NetBeans projects."},
	month = {10/2011},
	pages = {177-195},
	publisher = {Springer},
	abstract = {Open source software (OSS) has increasingly been the subject of research efforts. Central to this focus is the nature under which the software can be distributed, used, and modified and the causes and consequent effects on software development, usage, and distribution. At present, we have little understanding of, what happens when these licenses change, what motivates such changes, and how new licenses are created, updated, and deployed. Similarly, little attention has been paid to the agreements under which contributions are made to OSS projects and the impacts of changes to these agreements. We might also ask these same questions regarding the licenses governing how individuals and groups contribute to OSS projects. This paper focuses on addressing these questions with case studies of processes by which the Apache Software Foundation{\textquoteright}s creation and migration to Version 2.0 of the Apache Software License and the NetBeans project{\textquoteright}s migration to the Joint Licensing Agreement.},
	keywords = {apache, case study, email, email archive, license evolution, mailing list, netbeans, open source, process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@conference {Jergensen:2011:OPM:2025113.2025127,
	title = {The onion patch: migration in open source ecosystems},
	booktitle = {Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering},
	series = {ESEC/FSE {\textquoteright}11},
	year = {2011},
	pages = {70{\textendash}80},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Past research established that individuals joining an Open Source community typically follow a socialization process called "the onion model": newcomers join a project by first contributing at the periphery through mailing list discussions and bug trackers and as they develop skill and reputation within the community they advance to central roles of contributing code and making design decisions. However, the modern Open Source landscape has fewer projects that operate independently and many projects under the umbrella of software ecosystems that bring together projects with common underlying components, technology, and social norms. Participants in such an ecosystems may be able to utilize a significant amount of transferrable knowledge when moving between projects in the ecosystem and, thereby, skip steps in the onion model. In this paper, we examine whether the onion model of joining and progressing in a standalone Open Source project still holds true in large project ecosystems and how the model might change in such settings.},
	keywords = {contribution model, open source software, project ecosystem},
	isbn = {978-1-4503-0443-6},
	doi = {10.1145/2025113.2025127},
	url = {http://doi.acm.org/10.1145/2025113.2025127},
	author = {Jergensen, Corey and Sarma, Anita and Wagstrom, Patrick}
}
@article {1398,
	title = {The search for a research method for studying OSS process innovation},
	journal = {Empirical Software Engineering},
	volume = {16},
	year = {2011},
	month = {8/2011},
	pages = {514 - 537},
	abstract = {Medium-sized, open-participation Open Source Software (OSS) projects do not usually perform explicit software process improvement on any routine basis. It would be useful to understand how to get such a project to accept a process improvement proposal and hence to perform process innovation. We want to determine an effective and feasible qualitative research method for studying the above question. We present (narratively) a case study of how we worked towards and eventually found such a research method. The case involves four attempts at collecting suitable data about innovation episodes (direct participation (twice), polling developers for episodes, manually finding episodes in mailing list archives) and the adaptation of the Grounded Theory data analysis methodology. Direct participation allows gathering rather rich data, but does not allow for observing a sufficiently large number of innovation episodes. Polling developers for episodes did not prove to be useful. Using mailing list archives to find data to be analyzed is both feasible and effective. We also describe how the data thus found can be analyzed based on the Grounded Theory Method with suitable adjustments. By-and-large, our findings ought to apply to studying various phenomena in OSS development processes that are similarly heavyweight and infrequent. However, specific details may block this possibility and we cannot predict which details that might be. The amount of effort involved in direct participation approaches to qualitative research can easily be underestimated. Also, survey approaches are not well-suited for many process issues in OSS, because too few developers are sufficiently process-conscious. An approach based on passive observation is a viable alternative in the OSS context due to the availability of large amounts of fairly complete archival data. },
	keywords = {argouml, Bochs, bugzilla, Flyspray, FreeDOS, gEDA, grounded theory, Grub, Innovation introduction, KVM, mailing list, Methodology, MonetDB, open source, Request Tracket, Rox, U-Boot, Xfce},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9160-1},
	author = {Prechelt, Lutz and Oezbek, Christopher}
}
@conference {1308,
	title = {Social interactions around cross-system bug fixings},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"We rely on information stored in versioning database and mailing lists of both systems and develop methods to reconstruct and integrate different historical database"},
	month = {05/2011},
	pages = {143-152},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Cross-system bug fixing propagation is frequent among systems having similar characteristics, using a common framework, or, in general, systems with cloned source code fragments. While previous studies showed that clones tend to be properly maintained within a single system, very little is known about cross-system bug management.

This paper describes an approach to mine explicitly documented cross-system bug fixings, and to relate their occurrences to social characteristics of contributors discussing through the project mailing lists--e.g., degree, betweenness, and brokerage--as well as to the contributors{\textquoteright} activity on source code.

The paper reports results of an empirical study carried out on FreeBSD and OpenBSD kernels. The study shows that the phenomenon of cross-system bug fixing between these two projects occurs often, despite the limited overlap of contributors. The study also shows that cross-system bug fixings mainly involve contributors with the highest degree, betweenness and brokerage level, as well as contributors that change the source code more than others.},
	keywords = {bug fixing, bug tracking system, committers, email, email archives, freebsd, mailing list, openbsd},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985463},
	author = {Cerulo, Luigi and Cimitile, Marta and Di Penta, Massimiliano and Canfora, Gerardo}
}
@proceedings {1280,
	title = {Successful Reuse of Software Components: A Report from the Open Source Perspective},
	year = {2011},
	month = {10/2011},
	pages = {159-176},
	publisher = {Springer},
	abstract = {A promising way of software reuse is Component-Based Software Development (CBSD). There is an increasing number of OSS products available that can be freely used in product development. However, OSS communities themselves have not yet taken full advantage of the {\textquotedblleft}reuse mechanism{\textquotedblright}. Many OSS projects duplicate effort and code, even when sharing the same application domain and topic. One successful counter-example is the FFMpeg multimedia project, since several of its components are widely and consistently reused into other OSS projects. This paper documents the history of the libavcodec library of components from the FFMpeg project, which at present is reused in more than 140 OSS projects. Most of the recipients use it as a black-box component, although a number of OSS projects keep a copy of it in their repositories, and modify it as such. In both cases, we argue that libavcodec is a successful example of reusable OSS library of components.},
	keywords = {component-based software development, OSS components, Software reuse},
	author = {Capiluppi, Andrea and Boldyreff, Cornelia and Stol, Klaas-Jan}
}
@proceedings {1271,
	title = {Towards a Unified Definition of Open Source Quality},
	year = {2011},
	note = {"In order to answer the research question, how is quality defined in the FLOSS literature, we performed a literature review."

"we searched Google Scholar for journal articles and conference papers containing the terms {\textquotedblleft}open source{\textquotedblright} and {\textquotedblleft}quality{\textquotedblright}"

"This process left us with 24 papers, to which we then added 16 from the quality and defect-fixing categories in [34] that met the above stated criteria.
This left us with 40 papers that defined quality and performed some form of empirical validation of that definition."

"there is little consensus in the FLOSS literature when it comes to defining quality."

defect resolution versus modularity: "Defect resolution rates (amount of defects resolved, speed of resolution) are the best way to measure a community{\textquoteright}s commitment to quality, because they recognize that FLOSS is not a static product, but ever evolving. These rates should be calculated per release, and not cumulatively, because the cycle of FLOSS evolution is the release. Researchers should be careful to only include defects and not new feature requests, duplicates, or poorly reported bugs into their calculations.
Modularity is being touted as the main driver of FLOSS quality success, but it needs to be further defined and studied in order to understand how it works."},
	month = {10/2011},
	pages = {17-33},
	publisher = {Springer},
	abstract = {Software quality needs to be specified and evaluated in order to determine the success of a development project, but this is a challenge with Free/Libre Open Source Software (FLOSS) because of its permanently emergent state. This has not deterred the growth of the assumption that FLOSS is higher quality than traditionally developed software, despite of mixed research results. With this literature review, we found the reason for these mixed results is that that quality is being defined, measured, and evaluated differently. We report the most popular definitions, such as software structure measures, process measures, such as defect fixing, and maturity assessment models. The way researchers have built their samples has also contributed to the mixed results with different project properties being considered and ignored. Because FLOSS projects are evolving, their quality is too, and it must be measured using metrics that take into account its community{\textquoteright}s commitment to quality rather than just its software structure. Challenges exist in defining what constitutes a defect or bug, and the role of modularity in affecting FLOSS quality.},
	keywords = {literature review, measurement, open source, quality, Software},
	author = {Ruiz, Claudia and Robinson, William}
}
@proceedings {1286,
	title = {Towards Improving OSS Products Selection {\textendash} Matching Selectors and OSS Communities Perspectives},
	year = {2011},
	month = {10/2011},
	pages = {244-258},
	publisher = {Springer},
	abstract = {Adopting third-party software is becoming an economical and strategic need for today organizations. A fundamental part of its successful adoption is the informed selection of products that best fit the organization needs. One of the main current problems hampering selection, specially of OSS products is the vast amount of unstructured, incomplete, evolvable and widespread information about products that highly increases the risks of taking a wrong decision. In this paper, we aim to inform and provide evidence to OSS communities that help them to envisage improvements on their information rendering strategies to satisfy industrial OSS selectors{\textquoteright} needs. Our results are from the matching between the informational needs of 23 OSS selectors from diverse software-intensive organizations, and the in-depth study of 9 OSS communities of different sizes and domains. The results evidenced specific areas of improvement that might help to enhance the industrial OSS selection practice.},
	keywords = {empirical study, information rendering strategy, open source software, selection},
	author = {Ayala, Claudia and Cruzes, Daniela S. and Franch, Xavier and Conradi, Reidar}
}
@conference {Rigby:2011:UBB:1985793.1985867,
	title = {Understanding broadcast based peer review on open source software projects},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	note = {http://helium.cs.uvic.ca/other/Rigby2011ICSE.pdf

5 projects},
	pages = {541{\textendash}550},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software peer review has proven to be a successful technique in open source software (OSS) development. In contrast to industry, where reviews are typically assigned to specific individuals, changes are broadcast to hundreds of potentially interested stakeholders. Despite concerns that reviews may be ignored, or that discussions will deadlock because too many uninformed stakeholders are involved, we find that this approach works well in practice. In this paper, we describe an empirical study to investigate the mechanisms and behaviours that developers use to find code changes they are competent to review. We also explore how stakeholders interact with one another during the review process. We manually examine hundreds of reviews across five high profile OSS projects. Our findings provide insights into the simple, community-wide techniques that developers use to effectively manage large quantities of reviews. The themes that emerge from our study are enriched and validated by interviewing long-serving core developers.},
	keywords = {apache, case studies, email, freebsd, grounded theory, kde, linux, linux kernel, open source software, peer review, subversion},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985867},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Rigby2011ICSE.pdf},
	author = {Peter C. Rigby and Storey, Margaret-Anne}
}
@article {howison2010validity-issues,
	title = {Validity Issues in the Use of Social Network Analysis with Digital Trace data},
	journal = {Journal of the Association for Information Systems},
	volume = {12},
	year = {2011},
	chapter = {Article 2},
	abstract = {There is an exciting natural match between social network analysis methods and the growth of data sources produced by social interactions via information technologies, from online communities to corporate information systems. Information Systems researchers have not been slow to embrace this combination of method and data. Such systems increasingly provide "digital trace data" that provide new research opportunities. Yet digital trace data are substantively different from the survey and interview data for which network analysis measures and interpretations were originally developed. This paper examines ten validity issues associated with the combination of data digital trace data and social network analysis methods, with examples from the IS literature, to provide recommendations for improving the validity of research using this combination.},
	keywords = {information system, Online Communities, social network analysis, Virtuality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HowisonSNADigitalTraceData-WorkingPaper.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@proceedings {1293,
	title = {Virtual Health Information Infrastructures: A Scalable Regional Model},
	year = {2011},
	month = {10/2011},
	pages = {316-319},
	publisher = {Springer},
	abstract = {Integrating research, education and evidence-based medical practice requires complex infrastructures and network linkages among these critical activities. This research examines communities of practice and open source software tools in development of scalable virtual infrastructures for the regional Virtual Health Library of the Latin American and Caribbean Health Sciences System (Bireme) and embedded national cases. Virtual infrastructures refer to an environment characterized by overlapping distribution networks accessible through Internet portals and websites designed to facilitate integrated use of available resources. Case analysis shows engagement of interdisciplinary communities of practice for scalable virtual infrastructure design. This research program considers theory and methods for study of transferability of the Latin American model to large health care systems in other cultures.},
	keywords = {Bireme, Communities Of Practice, culture, open source systems, virtual infrastructures},
	author = {Seror, Ann}
}
@conference {1305,
	title = {Visualizing collaboration and influence in the open-source software community},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"This data set includes the complete social graph of 500,000 follow links as well as over 1,000,000 commits and 50,000 users."

"...a large fraction of [GitHub] users provide a location in their profile, which we can turn into geographic coordinates using a geocoding API like PlaceFinder...

"For each repository, we extract the owner, collaborator, and contributor usernames, plus branch names. New user- names help to find new repositories, while branch names are used to fetch commit metadata. Using this method, the crawler uncovered 40,860 code repositories, representing 33,388 unique project names and 1,219,872 individual commits."

"In addition to crawled data, we use the complete GitHub user follower graph from Jan 19, 2011. This graph includes 452,248 links connecting 106,247 unique users, 47\% (49,500) of which could be geocoded with the PlaceFinder API"},
	month = {05/2011},
	pages = {223-226},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We apply visualization techniques to user profiles and repository metadata from the GitHub source code hosting service. Our motivation is to identify patterns within this development community that might otherwise remain obscured. Such patterns include the effect of geographic distance on developer relationships, social connectivity and influence among cities, and variation in project-specific contribution styles (e.g., centralized vs. distributed). Our analysis examines directed graphs in which nodes represent users{\textquoteright} geographic locations and edges represent (a) follower relationships, (b) successive commits, or (c) contributions to the same project. We inspect this data using a set of visualization techniques: geo-scatter maps, small multiple displays, and matrix diagrams. Using these representations, and tools based on them, we develop hypotheses about the larger GitHub community that would be difficult to discern using traditional lists, tables, or descriptive statistics. These methods are not intended to provide conclusive answers; instead, they provide a way for researchers to explore the question space and communicate initial insights.},
	keywords = {COLLABORATION, data exploration, geography, geoscatter, github, graph, mapping, metadata, open source, social graph, user profiles, visualization},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985476},
	url = {http://vis.stanford.edu/files/2011-GotHub-MSR.pdf},
	author = {Marschner, Eli and Rosenfeld, Evan and Heer, Jeffrey and Heller, Brandon}
}
@article {1388,
	title = {Adoption of open source software in software-intensive organizations {\textendash} A systematic literature review},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {11/2010},
	pages = {1133 - 1154},
	abstract = {Context

Open source software (OSS) is changing the way organizations develop, acquire, use, and commercialize software.
Objective

This paper seeks to identify how organizations adopt OSS, classify the literature according to these ways of adopting OSS, and with a focus on software development evaluate the research on adoption of OSS in organizations.
Method

Based on the systematic literature review method we reviewed publications from 24 journals and seven conference and workshop proceedings, published between 1998 and 2008. From a population of 24,289 papers, we identified 112 papers that provide empirical evidence on how organizations actually adopt OSS.
Results

We show that adopting OSS involves more than simply using OSS products. We moreover provide a classification framework consisting of six distinctly different ways in which organizations adopt OSS. This framework is used to illustrate some of the opportunities and challenges organizations meet when approaching OSS, to show that OSS can be adopted successfully in different ways, and to organize and review existing research. We find that existing research on OSS adoption does not sufficiently describe the context of the organizations studied, and it fails to benefit fully from related research fields. While existing research covers a large number of topics, it contains very few closely related studies. To aid this situation, we offer directions for future research.
Conclusion

The implications of our findings are twofold. On the one hand, practitioners should embrace the many opportunities OSS offers, but consciously evaluate the consequences of adopting it in their own context. They may use our framework and the success stories provided by the literature in their own evaluations. On the other hand, researchers should align their work, and perform more empirical research on topics that are important to organizations. Our framework may be used to position this research and to describe the context of the organization they are studying.},
	keywords = {open source software, organizations, software development, Systematic literature review},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.05.008},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584910000972},
	author = {Hauge, {\O}yvind and Ayala, Claudia and Conradi, Reidar}
}
@article {1382,
	title = {Analysis of virtual communities supporting OSS projects using social network analysis},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {3/2010},
	pages = {296 - 303},
	abstract = {This paper analyses the behaviour of virtual communities for Open Source Software (OSS) projects. The development of OSS projects relies on virtual communities, which are built on relationships among members, being their final objective sharing knowledge and improving the underlying project. This study addresses the interactive collaboration in these kinds of communities applying social network analysis (SNA). In particular, SNA techniques will be used to identify those members playing a middle-man role among other community members. Results will illustrate the importance of this role to achieve successful virtual communities.},
	keywords = {arm, email, Knowledge brokers, linux, mailing list, open source software, social network analysis, virtual communities},
	issn = {09505849},
	doi = {10.1016/j.infsof.2009.10.007},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584909001888},
	author = {Toral, S.L. and Mart{\'\i}nez-Torres, M.R. and Barrero, F.}
}
@inbook {springerlink:10.1007/978-3-642-13244-5_20,
	title = {Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?},
	booktitle = {Open Source Software: New Horizons},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {319},
	year = {2010},
	note = {"We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository."},
	pages = {252-267},
	publisher = {Springer Boston},
	organization = {Springer Boston},
	abstract = {Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.},
	keywords = {flossmole, oss2010, sourceforge},
	url = {http://dx.doi.org/10.1007/978-3-642-13244-5_20},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s and Madey, Gregory and Noll, John}
}
@conference {1358,
	title = {Extracting source code from e-mails},
	booktitle = {Proceedings of ICPC 2010 (18th IEEE International Conference on Program Comprehension)},
	year = {2010},
	note = {"We want to extract source code fragments from e-mail messages. To do this, we first need to select e-mails that contain source code fragments, and then we extract such fragments from the content in which they are enclosed."

"we manually build a statistically significant benchmark taking sample e- mails from five unrelated open source Java software systems."

},
	pages = {24-33},
	abstract = {E-mails, used by developers and system users to communicate over a broad range of topics, offer a valuable source of information. If archived, e-mails can be mined to support program comprehension activities and to provide views of a software system that are alternative and complementary to those offered by the source code.

However, e-mails are written in natural language, and therefore contain noise that makes it difficult to retrieve the important data. Thus, before conducting an effective system analysis and extracting data for program comprehension, it is necessary to select the relevant messages, and to expose only the meaningful information.

In this work we focus both on classifying e-mails that hold fragments of the source code of a system, and on extracting the source code pieces inside the e-mail. We devised and analyzed a number of lightweight techniques to accomplish these tasks. To assess the validity of our techniques, we manually inspected and annotated a statistically significant number of e-mails from five unrelated open source software systems written in Java. With such a benchmark in place, we measured the effectiveness of each technique in terms of precision and recall.},
	keywords = {argouml, email, freenet, jmeter, mailing lists, mina, natural language, openjpa, source code},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icpc2010.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {1221,
	title = {From Proprietary to Open Source: Building a Network of Trust},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {When a corporation is about to release a product as open source a large network of trust must be built and maintained. Open source and commercial domains have radically different aspects of trust. Still, trust is vital in products survival in both settings. This paper focuses on building cognitive, or rational, trust in both commercial and open source domains. We set the view angle so that trust can be approached via the various relationships between the stakeholders involved in the community building process. Towards this goal, the paper focuses on the first steps of the process by proposing a set of best practices.},
	keywords = {oss2010, osscomm, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm001.pdf},
	author = {Sirkkala, Petri and Hammouda, Imed and Aaltonen, Timo}
}
@conference {1255,
	title = {{\textquoteright}Letting go of Control{\textquoteright} to Embrace Open Source: Implications for Company and Community},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {It is increasingly understood across the information technology and services sector that engagement with the open source software model can serve as a means for firms to capture intellectual energy, learn about productive software processes, access relevant technical skills, identify and recruit staff, as well as obtain valuable resources including code. This paper reports a study undertaken within two large global IT companies that have been actively involved with open source for more than ten years. The study involved over 30 semi-structured interviews with employees of the companies drawn from top, middle, and lower level management, and included active and experienced developer as well as open source community members. Our findings indicate how these companies have adapted their day-to-day management practices to take into account the need for flexibility and freedom expected by open source communities. This paper focuses on how they {\textquoteright}let go of control{\textquoteright} and what the implications of this are for both companies and the communities involved. Our data reveals a number of themes and in this paper we focus on three principal ones; issues of requirements, total cost of adoption, and alignment of open source engagement with long term company strategy.},
	keywords = {adoption, companies, interviews, organizations},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-01.pdf},
	author = {Maha Shaikh and Cornford, Tony}
}
@conference {bird2010lee,
	title = {{Linkster: Enabling Efficient Manual Mining}},
	booktitle = {Demonstration Track, Proceedings of the 17th SIGSOFT Symposium on Foundations of Software Engineering},
	year = {2010},
	note = {"LINKSTER efficiently displays, integrates, and allows inspection and annotation of information from three main sources of data: source code repositories, developer mailing lists archives, and bug tracking databases. LINKSTER requires access to a source code repository for file content and a database which contains the raw mined repository, mailing list, and bug tracking information. All notes and annotations made by the user are also recorded in the database."},
	publisher = {ACM},
	organization = {ACM},
	abstract = {While many uses of mined software engineering data are automatic in nature, some techniques and studies either require, or can be improved, by manual methods. Unfortunately, manually inspecting, analyzing, and annotating mined data can be difficult and tedious, especially when information from multiple sources must be integrated. Oddly, while there are numerous tools and frameworks for automatically mining and analyzing data, there is a dearth of tools which facilitate manual methods. To fill this void, we have developed LINKSTER, a tool which integrates data from bug databases, source code repositories, and mailing list archives to allow manual inspection and annotation. LINKSTER has already been used successfully by an OSS project lead to obtain data for one empirical study.},
	keywords = {artifacts, bug, bug tracking, data mining, email, mailing lists, open source, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2010lee.pdf},
	author = {Christian Bird and Adrian Bachman and Rahman, Foyzur and Bernstein, Abraham}
}
@conference {837,
	title = {Lurking? Cyclopaths? A Quantitative Lifecyle Analysis of User Behavior in a Geowiki},
	booktitle = {ACM Conference on Computer-Human Interaction (CHI)},
	year = {2010},
	month = {04/2010},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Atlanta, GA},
	keywords = {content,, geographic, geowiki,, information,, lurking, open, volunteer, volunteered, Wiki,, work,},
	author = {Panciera, K. and Priedhorsky, R. and Erickson, T. and Terveen, L.}
}
@conference {Oezbek:2010:OCS:1833272.1833274,
	title = {The onion has cancer: some social network analysis visualizations of open source project communication},
	booktitle = {Proceedings of the 3rd International Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development (FLOSS {\textquoteright}10)},
	series = {FLOSS {\textquoteright}10},
	year = {2010},
	note = {paper d/l from www.inf.fu-berlin.de/~oezbek/pub/OezThiPre10-SNA.pdf

"We study the introduction of process innovations in Open Source projects [33] by manually extracting innovation episodes from arch- ives of mailing-lists and analyzing these episodes qualitatively by the Grounded Theory Method [38]."

"we took all messages from the mailing-list archives in 2007 of the projects we were studying, turned each participant into a node (unifying multi- ple e-mail addresses where needed [6]), and computed relationship strength between A and B as the number of e-mails that are a reply of B to a message from A or vice versa, according to the in-reply-to header of the e-mail."

Our data set covers 11 of the 13 projects (from 7 different do- mains, selected from mailing-list archive Gmane to build a diverse set of projects) for which we analyzed innovation episodes. They include three workflow applications (Bugzilla, Flyspray, Request Tracker), two desktop environments (Rox, Xfce), two design tools (ArgoUML, a UML CASE tool; gEDA, a set of electronic design automation tools), one bootloader (Grub), one hardware emulator (Bochs), one operating system (FreeDOS), and one database man- agement system (MonetDB).},
	pages = {5{\textendash}10},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Background: People contribute to OSS projects in wildly different degrees, from reporting a single defect once and never coming back to spending many hours each workday on the project over several years - or anything in between. It is a common conception that these degrees of participation sort the participants into a number of similar groups which are layered like the peels of an onion: The onion model. Objective: We check whether this model of gradually different degrees of participation is valid with respect to the participation in OSS project mailing-list traffic. Methods: We perform social network analysis based on replies to mailing-list messages and use visualization to check the nature of three different groups of participants. Results: There appears to be a discontinuity with respect to core members: The degree to which very active core members (as opposed to less active co-developers) react to e-mails of senders from the project{\textquoteright}s periphery is significantly higher than would be expected from their level of activity in general. Limitations: The effect might be an artifact of the assumption that each mailing-list message can be treated the same. Conclusions: We conclude that core member status may be qualitatively (rather than just quantitatively) different and the transition of individual mailing-list participants towards ever higher participation is qualitatively discontinuous.},
	keywords = {argouml, Bochs, bugzilla, communication structure, Flyspray, gEDA, Grub, MonetDB, open source process, request tracker, Rox, social network analysis, Xfce},
	isbn = {978-1-60558-978-7},
	doi = {10.1145/1833272.1833274},
	url = {http://doi.acm.org/10.1145/1833272.1833274},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OezThiPre10-SNA.pdf},
	author = {Oezbek, Christopher and Prechelt, Lutz and Thiel, Florian}
}
@conference {Hissam,
	title = {On Open and Collaborative Software Development in the DoD},
	booktitle = {Seventh Annual Acquisition Research Symposium, {NPS} Proceedings -},
	volume = {1},
	number = {1},
	year = {2010},
	month = {04/2010},
	pages = {219{\textendash}235},
	publisher = {Naval Postgraduate School},
	organization = {Naval Postgraduate School},
	address = {Monterey, California},
	abstract = {The US Department of Defense (specifically, but not limited to, the DoD CIO{\textquoteright}s Clarifying Guidance Regarding Open Source Software, DISA{\textquoteright}s launch of Forge.mil and OSD{\textquoteright}s Open Technology Development Roadmap Plan) has called for increased use of open source software and the adoption of best practices from the free/open source software (F/OSS) community to foster greater reuse and innovation between programs in the DoD. In our paper, we examine some key aspects of open and collaborative software development inspired by the success of the F/OSS movement as it might manifest itself within the US DoD. This examination is made from two perspectives: the reuse potential among DoD programs sharing software and the incentives, strategies and policies that will be required to foster a culture of collaboration needed to achieve the benefits indicative of F/OSS. Our conclusion is that to achieve predictable and expected reuse, not only are technical infrastructures needed, but also a shift to the business practices in the software development and delivery pattern seen in the traditional acquisition lifecycle is needed. Thus, there is potential to overcome the challenges discussed within this paper to engender a culture of openness and community collaboration to support the DoD mission.},
	keywords = {collaborative development, open source software, reuse, software engineering},
	url = {http://www.acquisitionresearch.net/cms/_files/FY2010/NPS-AM-10-037.pdf},
	author = {Hissam, S. A. and Weinstock, C. and Bass, L.}
}
@conference {1220,
	title = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {The Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) aims at building a commu- nity of researchers and practitioners to share experiences and discuss chal- lenges involved in building and maintaining open source communities. De- tailed	information	regarding	the	workshop	is	available	at http://tutopen.cs.tut.fi/oscomm10/.},
	keywords = {oscomm, oscomm2010, oss2010, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm000.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@article {Singh:2010:SEI:1824760.1824763,
	title = {The small-world effect: The influence of macro-level properties of developer collaboration networks on open-source project success},
	journal = {ACM Trans. Softw. Eng. Methodol.},
	volume = {20},
	number = {2},
	year = {2010},
	pages = {6:1{\textendash}6:27},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {In this study we investigate the impact of community-level networks{\textemdash}relationships that exist among developers in an OSS community{\textemdash}on the productivity of member developers. Specifically, we argue that OSS community networks characterized by small-world properties would positively influence the productivity of the member developers by providing them with speedy and reliable access to more quantity and variety of information and knowledge resources. Specific hypotheses are developed and tested using longitudinal data on a large panel of 4,279 projects from 15 different OSS communities hosted at Sourceforge. Our results suggest that significant variation exists in small-world properties of OSS communities at Sourceforge. After accounting for project, foundry, and time-specific observed and unobserved effects, we found a statistically significant relationship between small-world properties of a community and the technical and commercial success of the software produced by its members. In contrast to the findings of prior research, we also found the lack of a significant relationship between closeness and betweenness centralities of the project teams and their success. These results were robust to a number of controls and model specifications.},
	keywords = {collaborative software development, online community, open source software development, productivity, small world networks, social networks, sourceforge, team formation},
	issn = {1049-331X},
	doi = {10.1145/1824760.1824763},
	url = {http://doi.acm.org/10.1145/1824760.1824763},
	author = {Param Vir Singh}
}
@mastersthesis {barcomb:2010:sociability,
	title = {The Sociability of Free Software: A GNU Look at Free Software Identified Businesses as Social Entrepreneurships},
	year = {2010},
	school = {Maastricht University},
	type = {masters},
	abstract = {This research strives to address the gap in the literature surrounding companies which identify with the philosophical values associated with the Free Software movement, which have historically been associated with Open Source businesses. It investigates whether ethically-motivated Free Software identified companies resemble social entrepreneurships. This work also examines whether there are significant differences between the business practices of Free Software identified companies, Free Software, and Open Source enterprises in order to assess if it is appropriate to address them as a group. The study is based on seven case studies, and includes one company which is a Free Software business, but does not identify with the Free Software philosophy, as well as one company which is ethically-motivated but identifies with Open Source rather than Free Software. The results indicate that there is good reason to believe that adherence to Free Software philosophy creates socially-aware businesses, which may be social entrepreneurships. No problems were discovered with the practice of grouping together Free Software and Open Source companies in the study of business practices, provided that a broad definition of success is used.
},
	keywords = {free software, open source software, public good, small business, social entrepreneurship, social ventures},
	url = {http://barcomb.org/cgi/paper.cgi?paper=barcomb:2010:sociability},
	attachments = {https://flosshub.org/sites/flosshub.org/files/barcomb-2010-sociability.pdf},
	author = {Barcomb, Ann}
}
@conference {1259,
	title = {Towards an Openness Rating System for Open Source Software},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	pages = {1 - 8},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {Many open source software projects are not very open to third party developers. The point of open source is to enable anyone to fix bugs or add desired capabilities without holding them hostage to the original developers. This principle is important because an open source project{\textquoteright}s developers may be unresponsive or unable to meet third party needs, even if funding support for requested improvements is offered.This paper presents a simple rating system for evaluating the openness of software distributions. The rating system considers factors such as platform portability, documentation, licensing, and contribution policy. Several popular open source products are rated in order to illustrate the efficacy of the rating system.},
	keywords = {alice, case study, contribution, documentation, freespire, galib, latex, license, linux, linux kernel, mediaportal, openness, openoffice, opensolaris, rating, unicon},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.405},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10-07-04.pdf},
	author = {Bein, Wolfgang and Jeffery, Clinton}
}
@article {1387,
	title = {Using the DEMO methodology for modeling open source software development processes},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {6/2010},
	pages = {656 - 671},
	abstract = {Context

Open source software development (OSSD) process modeling has received increasing interest in recent years. These efforts aim to identify common elements in the development process between multiple open source software (OSS) projects. However, the complexity inherent to OSSD process modeling puts significant demands on the modeling language.
Objective

In this paper, we propose that the Design and Engineering Methodology for Organizations (DEMO) may provide an interesting alternative to develop OSSD process models. DEMO exhibits two unique features within the context of OSSD process modeling. First, DEMO analyzes processes at the ontological level and provides high-level process descriptions, instead of focusing on the implementation level. Second, DEMO studies the communication patterns between human actors, instead of the sequences in which activities are performed.
Method

We investigate the feasibility of using DEMO to construct OSSD process models by means of a case study. DEMO models were constructed to describe the NetBeans Requirements and Release process. In addition, the quality of these DEMO models was evaluated using a quality framework for conceptual modeling.
Results

Our results showed that our DEMO models exhibited a high level of abstraction, thereby reducing the complexity of the OSSD process models. In addition, the evaluation of the models developed in this paper by using the quality framework for conceptual modeling showed that the models were of high quality.
Conclusions

We have shown that the DEMO methodology can be successfully used to model OSSD processes and to obtain abstract and high-quality OSSD process models. However, given some potential drawbacks with respect to understandability and implementability, we primarily propose the use of DEMO within OSSD process modeling as an analysis tool that should be complemented with other techniques and models for communication and reenactment purposes.},
	keywords = {DEMO, Enterprise ontology, open source software, Software process modeling},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.02.002},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584910000157},
	author = {Huysmans, Philip and Ven, Kris and Verelst, Jan}
}
@article {1239,
	title = {Weaving a Semantic Web Across OSS Repositories},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {29 - 40},
	abstract = {Several public repositories and archives of {\textquotedblleft}facts{\textquotedblright} about libre software projects, maintained either by open source communities or by research communities, have been flourishing over the Web in recent years. These have enabled new analysis and support for new quality assurance tasks. This paper presents some complementary existing tools, projects and models proposed both by OSS actors or research initiatives that are likely to lead to useful future developments in terms of study of the FLOSS phenomenon, and also to the very practitioners in the FLOSS development projects. A goal of the research conducted within the HELIOS project is to address bugs traceability issues. In this regard, the authors investigate the potential of using Semantic Web technologies in navigating between many different bugtracker systems scattered all over the open source ecosystem. By using Semantic Web techniques, it is possible to interconnect the databases containing data about open-source software projects development, which enables OSS partakers to identify resources, annotate them, and further interlink those using dedicated properties and collectively designing a distributed semantic graph.},
	keywords = {archive, bug, bugtracker, database, debian, forge, interoperability, ontology, OSLC-CM, RDF, repository of repositories, semantic, semantic Web},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd2009-olivier-berger.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Quang Vu Dang and Lauriere, St{\'e}phane}
}
@conference {953,
	title = {When process data quality affects the number of bugs: Correlations in software engineering datasets},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {62 - 71},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Software engineering process information extracted from version control systems and bug tracking databases are widely used in empirical software engineering. In prior work, we showed that these data are plagued by quality deficiencies, which vary in its characteristics across projects. In addition, we showed that those deficiencies in the form of bias do impact the results of studies in empirical software engineering. While these findings affect software engineering researchers the impact on practitioners has not yet been substantiated. In this paper we, therefore, explore (i) if the process data quality and characteristics have an influence on the bug fixing process and (ii) if the process quality as measured by the process data has an influence on the product (i.e., software) quality. Specifically, we analyze six Open Source as well as two Closed Source projects and show that process data quality and characteristics have an impact on the bug fixing process: the high rate of empty commit messages in Eclipse, for example, correlates with the bug report quality. We also show that the product quality - measured by number of bugs reported - is affected by process data quality measures. These findings have the potential to prompt practitioners to increase the quality of their software process and its associated data quality.},
	keywords = {apache, bug reports, eclipse, gnome, log files, mozilla, netbeans, openoffice.org, version control},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463286},
	attachments = {https://flosshub.org/sites/flosshub.org/files/62bachmann-msr10.pdf},
	author = {Bachmann, Adrian and Bernstein, Abraham}
}
@conference {929,
	title = {Code siblings: Technical and legal implications of copying code between applications},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {81 - 90},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Source code cloning does not happen within a single system only. It can also occur between one system and another. We use the term code sibling to refer to a code clone that evolves in a different system than the code from which it originates. Code siblings can only occur when the source code copyright owner allows it and when the conditions imposed by such license are not incompatible with the license of the destination system. In some situations copying of source code fragments are allowed - legally - in one direction, but not in the other. In this paper, we use clone detection, license mining and classification, and change history techniques to understand how code siblings - under different licenses - flow in one direction or the other between Linux and two BSD Unixes, FreeBSD and OpenBSD. Our results show that, in most cases, this migration appears to happen according to the terms of the license of the original code being copied, favoring always copying from less restrictive licenses towards more restrictive ones. We also discovered that sometimes code is inserted to the kernels from an outside source.},
	keywords = {bsd, fossology, freebsd, linux, openbsd, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069483},
	attachments = {https://flosshub.org/sites/flosshub.org/files/81CodeSiblings.pdf},
	author = {Daniel M. German and Di Penta, Massimiliano and Gueheneuc, Yann-Gael and Antoniol, Giuliano}
}
@article {1414,
	title = {Competition and production of digital public goods},
	journal = {International Journal of Intelligent Control and Systems},
	volume = {14},
	number = {1},
	year = {2009},
	pages = {77-86},
	chapter = {77},
	abstract = {With the Internet has come the phenomenon of people volunteering to work on digital public goods such as open source software and online encyclopedia articles. Presumably, the success of individual public goods has an effect on attracting volunteers. However, the definition of success is ill-defined. This paper explores the impact of different success metrics on a simple public goods model. The findings show that the different success metrics considered do have an impact on the behavior of the model, with the largest differences being between consumer-oriented and producer-oriented metrics. This indicates that many proposed success metrics may be mapped into one of these two categories and within a category, all success metrics measure the same phenomenon. We argue that the characteristics of producer-oriented metrics more closely match real world phenomena, indicating that public goods are driven by producer, and not consumer, interests.},
	keywords = {digital public goods, FLOSS, open source software, sourceforge, success metrics, wikipedia},
	url = {http://www.public.asu.edu/~majansse/pubs/ijics2009.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijics2009.pdf},
	author = {Radtke, Nicholas P. and Janssen, Marco A.}
}
@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.}
}
@conference {844,
	title = {A Jury of Your Peers: Quality, Experience and Ownership in Wikipedia},
	booktitle = {The International Symposium on Wiki{\textquoteright}s and Open Collaboration},
	year = {2009},
	month = {10/2009},
	address = {Orlando, FL},
	keywords = {experience,, ownership,, peer, peer,, quality, review,, wikipedia,, wikiwork,},
	author = {Halfaker, A. and Kittur, N. and Kraut, R. and Riedl, J.}
}
@article {1118,
	title = {Monetary donations to an open source software platform},
	journal = {Research Policy},
	volume = {38},
	year = {2009},
	month = {03/2009},
	pages = {404 - 414},
	abstract = {Online open source software platforms, such as Sourceforge.net, play a vital role in creating an ecosystem that enables the creation and growth of open source projects. However, there is little research exploring the interactions between open source stakeholders and the platform. We believe that the sustainability of the platform crucially depends on financial incentives. While platforms can obtain these incentives through multiple means, in this paper we focus on one form of financial incentives{\textemdash}voluntary monetary donations by open source community members. We report findings from two empirical studies that examine factors that impact donations. Study 1 investigates the factors that cause some community members to donate and not others. We find that the decision to donate is impacted by relational commitment with open source software platform, donation to projects and accepting donations from others. Study 2 examines what drives the level of donation. We find that the length of association with the platform and relational commitment affects donation levels.},
	keywords = {Collective action, Donation, Identification, incentives, metadata, MOTIVATION, Open source software platform, projects, Reciprocity, Relational commitment, sourceforge},
	issn = {00487333},
	doi = {10.1016/j.respol.2008.11.004},
	author = {Sandeep Krishnamurthy and Tripathi, Arvind K.}
}
@conference {1263,
	title = {Multiple Social Networks Analysis of FLOSS Projects using Sargas},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"The interval of analysis for the first three networks was from 2003/02/24 to 2003/11/03. These networks were created using the OSSNetwork tool [18]. The source code of the PMD project was collected starting on 2002/06/24..."
"Transflow performs a co-changes analysis of the source code modification history and creates a matrix where software components are connected by taking into account the frequency that they have been changed together (i.e., in the same check-in): if two files have been changed together in the same check-in, an edge is created to link these two files."},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {Due to their characteristics and claimed advantages, several researchers have been investigating free and open-source projects. Different aspects are being studied: for instance, what motivates developers to join FLOSS projects, the tools, processes and practices used in FLOSS projects, the evolution of FLOSS communities among other things. Researchers have studied collaboration and coordination of open source software developers using an approach known as social network analysis and have gained important insights about these projects. Most researchers, however, have not focused on the integrated study of these networks and, accordingly, in their interrelationships. This paper describes an approach and tool to combine multiple social networks to study the evolution of open-source projects. Our tool, named Sargas, allows comparison and visualization of different social networks at the same time. Initial results of our analysis can be used to extend the "onion-model" of open source participation.},
	keywords = {case study, multiple social networks, ossnetwork, pmd, social network analysis, transflow},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.316},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-06.pdf},
	author = {de Sousa, S.F. and Balieiro, M.A. and dos R. Costa, J.M. and de Souza, C.R.B.}
}
@conference {765,
	title = {The role of patch review in software evolution: an analysis of the mozilla firefox},
	booktitle = {The joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	month = {08/2009},
	pages = {9-18},
	publisher = {ACM},
	organization = {ACM},
	type = {Paper in Conference Proceedings},
	address = {Amsterdam, The Netherlands},
	abstract = {Patch review is the basic mechanism for validating the design and implementation of patches and maintaining consistency in some commercial and Free/Libre/Open Source Software (FLOSS) projects. We examine the inner-workings of the development process of the successful and mature Mozilla foundation and highlight how different parties involved affect and steer the process. Although reviewers are the primary actors in the patch review process, success in the process can only be achieved if the community supports reviewers adequately. Peer developers play the supporting role by offering insight and ideas that help create more quality patches. Moreover, they reduce the huge patch backlog reviewers have to clear by identifying and eliminating immature patches.},
	keywords = {inspection, open source development},
	isbn = {978-1-60558-678-6},
	doi = {http://doi.acm.org/10.1145/1595808.1595813},
	url = {http://ase.cpsc.ucalgary.ca/ase/uploads/Publications/iwpse31-nurolahzade.pdf},
	author = {Mehrdad Nurolahzade},
	editor = {Seyed Mehdi Nasehi and Shahedul Huq Khandkar and Shreya Rawal}
}
@article {schryen2009security,
	title = {Security of Open Source and Closed Source Software: An Empirical Comparison of Published Vulnerabilities},
	journal = {AMCIS 2009 Proceedings},
	year = {2009},
	pages = {387},
	abstract = {Reviewing literature on open source and closed source security reveals that the discussion is often determined by biased attitudes toward one of these development styles. The discussion specifically lacks appropriate metrics, methodology and hard data. This paper contributes to solving this problem by analyzing and comparing published vulnerabilities of eight open source software and nine closed source software packages, all of which are widely deployed. Thereby, it provides an extensive empirical analysis of vulnerabilities in terms of mean time between vulnerability disclosures, the development of disclosure over time, and the severity of vulnerabilities, and allows for validating models provided in the literature. The investigation reveals that (a) the mean time between vulnerability disclosures was lower for open source software in half of the cases, while the other cases show no differences, (b) in contrast to literature assumption, 14 out of 17 software packages showed a significant linear or piecewise linear correlation between time and the number of published vulnerabilities, and (c) regarding the severity of vulnerabilities, no significant differences were found between open source and closed source.},
	keywords = {closed source software, empirical comparison, open source software, security, Vulnerabilities},
	url = {http://epub.uni-regensburg.de/21296/1/Schryen_-_AMCIS_09_-_Security_of_open_source_and_closed_source_software_-_Web_version.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Schryen_-_AMCIS_09_-_Security_of_open_source_and_closed_source_software_-_Web_version.pdf},
	author = {Schryen, Guido}
}
@conference {926,
	title = {Tracking concept drift of software projects using defect prediction quality},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {51 - 60},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Defect prediction is an important task in the mining of software repositories, but the quality of predictions varies strongly within and across software projects. In this paper we investigate the reasons why the prediction quality is so fluctuating due to the altering nature of the bug (or defect) fixing process. Therefore, we adopt the notion of a concept drift, which denotes that the defect prediction model has become unsuitable as set of influencing features has changed - usually due to a change in the underlying bug generation process (i.e., the concept). We explore four open source projects (Eclipse, OpenOffice, Netbeans and Mozilla) and construct file-level and project-level features for each of them from their respective CVS and Bugzilla repositories. We then use this data to build defect prediction models and visualize the prediction quality along the time axis. These visualizations allow us to identify concept drifts and - as a consequence - phases of stability and instability expressed in the level of defect prediction quality. Further, we identify those project features, which are influencing the defect prediction quality using both a tree induction-algorithm and a linear regression model. Our experiments uncover that software systems are subject to considerable concept drifts in their evolution history. Specifically, we observe that the change in number of authors editing a file and the number of defects fixed by them contribute to a project{\textquoteright}s concept drift and therefore influence the defect prediction quality. Our findings suggest that project managers using defect prediction models for decision making should be aware of the actual phase of stability or instability due to a potential concept drift.},
	keywords = {bugzilla, cvs, defect prediction, eclipse, mozilla, netbeans, openoffice},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069480},
	attachments = {https://flosshub.org/sites/flosshub.org/files/51MSR2009_0111_Ekanayake_Jayalath.pdf},
	author = {Ekanayake, Jayalath and Tappolet, Jonas and Gall, Harald C. and Bernstein, Abraham}
}
@conference {Yatani:2009:UWO:1518701.1518853,
	title = {Understanding how and why open source contributors use diagrams in the development of Ubuntu},
	booktitle = {Proceedings of the 27th international conference on Human factors in computing systems},
	series = {CHI {\textquoteright}09},
	year = {2009},
	note = {"To examine how and why diagrams are used in any and all aspects of the software development process of an OSS project, we performed a series of semi-structured interviews with contributors to one particular effort{\textemdash}Ubuntu."
"Our study was divided into two phases. First, we asked participants to complete a questionnaire and provide us with information and materials for discussion. The questionnaire featured questions about participants{\textquoteright} OSS experience, project participation, their roles in each project, and basic demographics. We also asked participants to share diagrams they had created, modified or used as part of their work on Ubuntu. In the second phase of the study, we conducted semi-structured interviews with participants."},
	pages = {995{\textendash}1004},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Some of the most interesting differences between Open Source Software (OSS) development and commercial co-located software development lie in the communication and collaboration practices of these two groups of developers. One interesting practice is that of diagramming. Though well studied and important in many aspects of co-located software development (including communication and collaboration among developers), its role in OSS development has not been thoroughly studied. In this paper, we report our investigation on how and why Ubuntu contributors use diagrams in their work. Our study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts. We describe differences in the use and practices of diagramming, their possible reasons, and present design considerations for potential systems aimed at better supporting diagram use in OSS development.},
	keywords = {developers, diagramming, interviews, open source software (oss), software development, Ubuntu, visual representation},
	isbn = {978-1-60558-246-7},
	doi = {http://doi.acm.org/10.1145/1518701.1518853},
	url = {http://doi.acm.org/10.1145/1518701.1518853},
	author = {Yatani, Koji and Chung, Eunyoung and Jensen, Carlos and Truong, Khai N.}
}
@article {Fang:2009:USP:1554441.1554443,
	title = {Understanding Sustained Participation in Open Source Software Projects},
	journal = {J. Manage. Inf. Syst.},
	volume = {25},
	year = {2009},
	month = {April},
	pages = {9{\textendash}50},
	publisher = {M. E. Sharpe, Inc.},
	address = {Armonk, NY, USA},
	abstract = {Prior research into open source software (OSS) developer participation has emphasized individuals{\textquoteright} motivations for joining these volunteer communities, but it has failed to explain why people stay or leave in the long run. Building upon Lave and Wenger{\textquoteright}s theory of legitimate peripheral participation (LPP), this paper offers a longitudinal investigation of one OSS community in which sustained participation is hypothesized to be associated with the coevolution of two major elements of LPP theory: "situated learning" (the process of acting knowledgeably and purposefully in the world) and "identity construction" (the process of being identified within the community). To test this hypothesis, data were collected from multiple sources, including online public project documents, electronic mail messages, tracker messages, and log files. Results from qualitative analyses revealed that initial conditions to participate did not effectively predict long-term participation, but that situated learning and identity construction behaviors were positively linked to sustained participation. Furthermore, this study reveals that sustained participants distinguished themselves by consistently engaging in situated learning that both made conceptual (advising others) and practical contributions (improving the code). Implications and future research are discussed.},
	keywords = {Communities Of Practice, Legitimate Peripheral Participation, Open Source Projects, Open Source Software Community, Qualitative Study},
	issn = {0742-1222},
	doi = {10.2753/MIS0742-1222250401},
	url = {http://portal.acm.org/citation.cfm?id=1554441.1554443},
	author = {Fang, Yulin and Neufeld, Derrick}
}
@article {10.1109/HICSS.2009.998,
	title = {Understanding the Nature and Production Model of Hybrid Free and Open Source Systems: The Case of Varnish},
	journal = {42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	pages = {1-11},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {This is a detailed interpretive case study analysis of an open source software project, called Varnish. The conceptual framework is based on the literature covering issues of commons based production models and the organization of open source projects. The comparative analysis reveals that Varnish is a hybrid project, encompassing the features of open source software while managed by a company as a proprietary project would. It is also hybrid in the sense that it employs a combination of hierarchical and commons based peer production model features. This mix of characters addresses a variety of problems related to each of the aforementioned categories.},
	keywords = {case study, organizational sponsorship, peer production, varnish},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.998},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-02.pdf},
	author = {Zegaye Seifu Wubishet}
}
@article {1338,
	title = {What Makes Free/Libre Open Source Software (FLOSS) Projects Successful? An Agent-Based Model of FLOSS Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {1 - 13},
	abstract = {The last few years have seen a rapid increase in the number of Free/Libre Open Source Software (FLOSS) projects. Some of these projects, such as Linux and the Apache web server, have become phenomenally successful. However, for every successful FLOSS project there are dozens of FLOSS projects which never succeed. These projects fail to attract developers and/or consumers and, as a result, never get off the ground. The aim of this research is to better understand why some FLOSS projects flourish while others wither and die. This article presents a simple agent-based model that is calibrated on key patterns of data from SourceForge, the largest online site hosting open source projects. The calibrated model provides insight into the conditions necessary for FLOSS success and might be used for scenario analysis of future developments of FLOSS.},
	keywords = {Agent-Based Model, Emergent Properties, FLOSS, open source, Prediction Success, Simulation},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040101},
	url = {http://www.public.asu.edu/~majansse/pubs/ijossp09.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp09.pdf},
	author = {Radtke, Nicholas P. and Janssen, Marco A. and Collofello, James S.}
}
@article {denBesten2008316,
	title = {The allocation of collaborative efforts in open-source software},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"we have selected a set of 10 large open-source projects"
apache, cvs, gaim, gcc, ghostscript, mozilla, netbsd, openssh, postgresql, python
"Our data were extracted from logs of development activity generated by software version control systems. For each project in the selection, we extracted CVS development logs"
"We notably computed for each file in the sample, and for each month in its history, the number of distinct maintainers that had committed a change during that month, and the number of commits, the blocks of code addition, each file had received during that month."
"other variables used in the regressions are proxies for the size, age, and granularity of files; the size of a file is represented as its number of lines of code (LOCs), its age by its creation date (Youth), and its granularity by the number of functions it contains."},
	pages = {316 - 322},
	abstract = {The article investigates the allocation of collaborative efforts among core developers (maintainers) of open-source software by analyzing on-line development traces (logs) for a set of 10 large projects. Specifically, we investigate whether the division of labor within open-source projects is influenced by characteristics of software code. We suggest that the collaboration among maintainers tends to be influenced by different measures of code complexity. We interpret these findings by providing preliminary evidence that the organization of open-source software development would self-adapt to characteristics of the code base, in a {\textquoteright}stigmergic{\textquoteright} manner.},
	keywords = {age, apache, complexity, cvs, division of labor, functions, gaim, gcc, ghostscript, lines of code, loc, log files, mozilla, netbsd, openssh, postgresql, python, revision control, scm, size, source code, Stigmergy, version control},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.003},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SSG4PN-1/2/88b3824c30a31c18929d8a5ca6d64f62},
	author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice}
}
@conference {Hill:2008:AAM:1370750.1370771,
	title = {AMAP: automatically mining abbreviation expansions in programs to enhance software maintenance tools},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {79{\textendash}88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When writing software, developers often employ abbreviations in identifier names. In fact, some abbreviations may never occur with the expanded word, or occur more often in the code. However, most existing program comprehension and search tools do little to address the problem of abbreviations, and therefore may miss meaningful pieces of code or relationships between software artifacts. In this paper, we present an automated approach to mining abbreviation expansions from source code to enhance software maintenance tools that utilize natural language information. Our scoped approach uses contextual information at the method, program, and general software level to automatically select the most appropriate expansion for a given abbreviation. We evaluated our approach on a set of 250 potential abbreviations and found that our scoped approach provides a 57\% improvement in accuracy over the current state of the art.},
	keywords = {automatic abbreviation expansion, azureus, itext.net, liferay, maintenance, natural language, openoffice.org, program comprehension, source code, tiger envelopes, tools},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370771},
	url = {http://doi.acm.org/10.1145/1370750.1370771},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p79-hill.pdf},
	author = {Hill, Emily and Fry, Zachary P. and Boyd, Haley and Sridhara, Giriprasad and Novikova, Yana and Pollock, Lori and Vijay-Shanker, K.}
}
@conference {1207,
	title = {Cross-repository data linking with RDF and OWL},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {non-experimental},
	month = {2009},
	pages = {15-22},
	abstract = {This paper provides an approach to the problem of integrating data from multiple research repositories for FLOSS 
data. It introduces semantic web technologies (RDF, OWL, OWL-DL reasoners and SPARQL) to argue that these are useful for building shared research infrastructure. The paper illustrates its point by describing parts of an ontology developed for the integration and analysis of project communications drawn from FLOSSmole, the Notre Dame archive and direct collection of data. RDF vocabularies provide a way to agree on things we agree about as well as a way to be clearer about ways in which we disagree.},
	keywords = {data integration, flossmole, forges, integration, owl, RDF, repositories, semantic, semantic Web, sparql, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/howison2008.pdf},
	author = {Howison, James}
}
@conference {SGKL09,
	title = {Evaluating the Quality of Open Source Software},
	booktitle = {Electronic Notes in Theoretical Computer Science},
	volume = {233},
	year = {2008},
	note = {"the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way"
"The data collection system collects the raw data from open source projects"
Mailing lists are measured in: Number of unique subscribers, Number of messages in user/support list per month, Number of messages in developers list per month, Average thread depth},
	month = {03/2009},
	pages = {5{\textendash}28},
	publisher = {The Reengineering Forum},
	organization = {The Reengineering Forum},
	abstract = {Traditionally, research on quality attributes was either kept under wraps within the organization that performed it, or carried out by outsiders using narrow, black-box techniques. The emergence of open source software has changed this picture allowing us to evaluate both software products and the processes that yield them. Thus, the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way. Even better, the large number of (often competing) open source projects makes it possible to contrast the quality of comparable systems serving the same domain. Furthermore, by combining historical source code snapshots with significant events, such as bug discoveries and fixes, we can further dig into the causes and effects of problems. Here we present motivating examples, tools, and techniques that can be used to evaluate the quality of open source (and by extension also proprietary) software. },
	keywords = {bug tracking system, email, email archives, mailing list, metrics, open source, process quality attributes, product quality attributes, source code, SQO-OSS, wiki},
	doi = {10.1016/j.entcs.2009.02.058},
	url = {http://www.dmst.aueb.gr/dds/pubs/conf/2008-SQM-SQOOSS/html/SGKL09.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entcs-sqooss.pdf},
	author = {Diomidis Spinellis and Gousios, Georgios and Vassilios Karakoidas and Panagiotis Louridas and Paul J. Adams and Samoladas, Ioannis and Ioannis Stamelos}
}
@article {GonzalezBarahona2008356,
	title = {Geographic origin of libre software developers},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {Empirical Issues in Open Source Software},
	pages = {356 - 363},
	abstract = {This paper examines the claim that libre (free, open source) software involves global development. The anecdotal evidence is that developers usually work in teams including individuals residing in many different geographical areas, time zones and even continents and that, as a whole, the libre software community is also diverse in terms of national origin. However, its exact composition is difficult to capture, since there are few records of the geographical location of developers. Past studies have been based on surveying a limited (and sometimes biased) sample and extrapolating that sample to the global distribution of developers. In this paper we present an alternate approach in which databases are analyzed to create traces of information from which the geographical origin of developers can be inferred. Applying this technique to the SourceForge users database and the mailing lists archives from several large projects, we have estimated the geographical origin of more than one million individuals who are closely related to the libre software development process. The paper concludes that the result is a good proxy for the actual distribution of libre software developers working on global projects.},
	keywords = {developers, email, email address, email archives, geography, mailing list, open source software, sourceforge, timezone, users},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.07.001},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4T3DCPK-1/2/3981dfbc523eae1d1ce65fb1f0c0edb7},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Roberto Andradas-Izquierdo and Rishab Aiyer Ghosh}
}
@article {499,
	title = {The Material and Social Dynamics of Motivation: Contributions to Open Source Language Technology Development},
	journal = {Science Studies},
	number = {2},
	year = {2008},
	note = {"I conducted a two-phased qualitative analysis on multiple data (thematic phone-inter- views, notes from OpenOffice.org conference 2004 meetings, historical documents, mailing list discussions, homepages, Google, blogs, real-time video and audio presentations from OpenOffice.org conference 2005)."},
	abstract = {Volunteer motivation has been a central theme in Free/Libre/Open Source Software (FLOSS) literature. This research has been largely dominated by economists who rely in their surveys on the distinction between intrinsic and extrinsic motivations and the "hacker ethic" for profit juxtaposition. The paper argues that survey-based analytical frameworks and research designs have led to a focus on some motivational attributions at the expense of others. It then presents a case study that explores dynamic, non individualistic and content-sensitive aspects of motivations. The approach is based on socio-cultural psychology and the author{\textquoteright}s observations of a hybrid firm-community FLOSS project, OpenOffice.org. Instead of separating intrinsic motivations from extrinsic ones, it is argued that complex and changing patterns of motivations are tied to changing objects and personal histories prior to and during participation. The boundary between work and hobby in an individual{\textquoteright}s participation path is blurred and shifting.},
	keywords = {contributions, developers, email, email archives, mailing list, MOTIVATION, openoffice, openoffice.org, secondary data, Volunteers},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Freeman.pdf},
	author = {Stephanie Freeman}
}
@conference {Rigby:2008:OSS:1368088.1368162,
	title = {Open source software peer review practices: a case study of the apache server},
	booktitle = {Proceedings of the 30th International Conference on Software Engineering (ICSE 2008)},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	note = {http://faculty.salisbury.edu/~xswang/Research/Papers/SERelated/testing/p541-rigby.pdf},
	pages = {541{\textendash}550},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Peer review is seen as an important quality assurance mechanism in both industrial development and the open source software (OSS) community. The techniques for performing inspections have been well studied in industry; in OSS development, peer reviews are less well understood. We examine the two peer review techniques used by the successful, mature Apache server project: review-then-commit and commit-then-review. Using archival records of email discussion and version control repositories, we construct a series of metrics that produces measures similar to those used in traditional inspection experiments. Specifically, we measure the frequency of review, the level of participation in reviews, the size of the artifact under review, the calendar time to perform a review, and the number of reviews that find defects. We provide a comparison of the two Apache review techniques as well as a comparison of Apache review to inspection in an industrial project. We conclude that Apache reviews can be described as (1) early, frequent reviews (2) of small, independent, complete contributions (3) conducted asynchronously by a potentially large, but actually small, group of self-selected experts (4) leading to an efficient and effective peer review technique.},
	keywords = {apache, cvs, email, inspection, mining software repositories (email), open source software, peer review, version control},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368162},
	url = {http://doi.acm.org/10.1145/1368088.1368162},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p541-rigby.pdf},
	author = {Peter C. Rigby and Daniel M. German and Storey, Margaret-Anne}
}
@conference {Krogstie:2008:PTB:1368088.1368201,
	title = {Power through brokering: open source community participation in software engineering student projects},
	booktitle = {Proceedings of the 30th international conference on Software engineering},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	pages = {791{\textendash}800},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Many software engineering projects use open source software tools or components. The project team{\textquoteright}s active participation in the open source community may be necessary for the team to use the technology. Based on an in-depth field study of industry software engineering project students interacting with an open source community, we find that participation in the community may affect the team{\textquoteright}s work and learning by strengthening the power of the broker between the team and the community. We outline pitfalls and benefits of having student teams acquire development-related knowledge from open source communities. The findings are relevant to the organization and supervision of software engineering student projects interacting with open source communities.},
	keywords = {Communities Of Practice, computer science education, FLOSS, open source, software engineering, software engineering education},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368201},
	url = {http://doi.acm.org/10.1145/1368088.1368201},
	author = {Krogstie, Birgit R.}
}
@conference {WeiBgerber:2008:SPG:1370750.1370767,
	title = {Small patches get in!},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {67{\textendash}76},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {While there is a considerable amount of research on analyzing the change information stored in software repositories, only few researcher have looked at software changes contained in email archives in form of patches. In this paper we look at the email archives of two open source projects and answer questions like the following: How many emails contain patches? How long does it take for a patch to be accepted? Does the size of the patch influence its chances to be accepted or the duration until it gets accepted? Obviously, the answers to these questions can be helpful for the authors of patches, in particular because some of the answers are surprising.},
	keywords = {case study, cvs, email, email archives, flac, mailing list, openafs, patch acceptance, patches, revision control, scm},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370767},
	url = {http://doi.acm.org/10.1145/1370750.1370767},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p67-weissgerber.pdf},
	author = {Wei{\ss}gerber, Peter and Neu, Daniel and Diehl, Stephan}
}
@conference {Spinellis:2008:TFK:1368088.1368140,
	title = {A tale of four kernels},
	booktitle = {Proceedings of the 30th international conference on Software engineering},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	pages = {381{\textendash}390},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The FreeBSD, GNU/Linux, Solaris, and Windows operating systems have kernels that provide comparable facilities. Interestingly, their code bases share almost no common parts, while their development processes vary dramatically. We analyze the source code of the four systems by collecting metrics in the areas of file organization, code structure, code style, the use of the C preprocessor, and data organization. The aggregate results indicate that across various areas and many different metrics, four systems developed using wildly different processes score comparably. This allows us to posit that the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any.},
	keywords = {comparison, freebsd, linux, open source, opensolaris, proprietary software, windows, wrk},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368140},
	url = {http://doi.acm.org/10.1145/1368088.1368140},
	author = {Diomidis Spinellis}
}
@article {Barcellini:2008:UDM:1379919.1380288,
	title = {User and developer mediation in an Open Source Software community: Boundary spanning through cross participation in online discussions},
	journal = {Int. J. Hum.-Comput. Stud.},
	volume = {66},
	number = {7},
	year = {2008},
	pages = {558{\textendash}570},
	publisher = {Academic Press, Inc.},
	address = {Duluth, MN, USA},
	abstract = {The aim of this research is to analyse how design and use are mediated in Open Source Software (OSS) design. Focusing on the Python community, our study examines a {\textquoteright}{\textquoteright}pushed-by-users{\textquoteright}{\textquoteright} design proposal through the discussions occurring in two mailing-lists: one, user-oriented and the other, developer-oriented. To characterize the links between users and developers, we investigate the activities and references (knowledge sharing) performed by the contributors to these two mailing-lists. We found that the participation of users remains local to their community. However, several key participants act as boundary spanners between the user and the developer communities. This emerging role is characterized by cross-participation in parallel same-topic discussions in both mailing-lists, cohesion between cross-participants, the occupation of a central position in the social network linking users and developers, as well as active, distinctive and adapted contributions. The user championing the proposal acts as a key boundary spanner coordinating the process and using explicit linking strategies. We argue that OSS design may be considered as a form of {\textquoteright}{\textquoteright}role emerging design{\textquoteright}{\textquoteright}, i.e. design organized and pushed through emerging roles and through a balance between these roles. The OSS communities seem to provide a suitable socio-technical environment to enable such role emergence. },
	keywords = {Boundary spanners, Cross-participants, Distributed design, Open Source Software Community, Role emerging design},
	issn = {1071-5819},
	doi = {10.1016/j.ijhcs.2007.10.008},
	url = {http://dx.doi.org/10.1016/j.ijhcs.2007.10.008},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie}
}
@article {126,
	title = {Investigating recognition-based performance in an open content community: A social capital perspective},
	journal = {Information \& Management},
	volume = {44},
	number = {3},
	year = {2007},
	note = {Times Cited: 0},
	month = {Apr},
	pages = {240-252},
	abstract = {As the open source movement grows, it becomes important to understand the dynamics that affect the motivation of participants who contribute their time freely to such projects. One important motivation that has been identified is the desire for formal recognition in the open source community. We investigated the impact of social capital in participants{\textquoteright} social networks on their recognition-based performance; i.e., the formal status they are accorded in the community. We used a sample of 465 active participants in the Wikipedia open content encyclopedia community to investigate the effects of two types of social capital and found that network closure, measured by direct and indirect ties, had a significant positive effect on increasing participants{\textquoteright} recognition-based performance. Structural holes had mixed effects on participants{\textquoteright} status, but were generally a source of social capital. (C) 2007 Elsevier B.V. All rights reserved.},
	keywords = {open content, recognition-based performance, social capital, social networks, social status, virtual communities},
	isbn = {0378-7206},
	author = {Okoli, C. and Oh, Wonseok}
}
@article {Wang:2007:MEO:1317471.1317479,
	title = {Measuring the evolution of open source software systems with their communities},
	journal = {SIGSOFT Softw. Eng. Notes},
	volume = {32},
	year = {2007},
	note = {"1. M1: The number of modules in software system at a series of specific moment.
2. CD: The number of developers (code contributors) at a series of specific moment.
3. MC: The correlation of M1 and CD."
"We get the information of Modules from the Launchpad[1] which is a distributed collaborative infrastructure for Ubuntu and other open source software development. Ubuntu mainly grows though a manner of adding new packages. So, we treat packages as the modules we mention before. In Ubuntu community, some members are in charge of auditing the packages and add them to Ubuntu, here developers are refers them."},
	month = {November},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {Open Source Software (OSS) has become the subject of much commercial and academic interest in last few years. As traditional software, OSS also evolves to fulfill the need of stakeholders. Therefore, providing quantitative metrics for OSS evolution has also become an urgent issue. However, most existing studies of software evolution have been performed on systems developed within a single company using traditional management techniques. These metrics models are inadequate to measure OSS evolution. In this paper, we describe a preliminary evolution metrics set for evaluating OSS. The most significant novelty of this model is that it takes specific properties of Open Source Community (OSC) into consideration. In another word, we measure the evolution of OSS and OSC together. We also provide a lightweight case study on Ubuntu project using this metrics set. We find out that the Open Source Community and its members also play essential role in OSS evolution. We expect this metrics model can bring better understandings and explanations of phenomena in open source development and evolution.},
	keywords = {evolution, launchpad, metrics, open source community, open source software, Ubuntu},
	issn = {0163-5948},
	doi = {http://doi.acm.org/10.1145/1317471.1317479},
	url = {http://doi.acm.org/10.1145/1317471.1317479},
	author = {Yi Wang and Defeng Guo and Shi, Huihui}
}
@article {125,
	title = {Membership herding and network stability in the open source community: The Ising perspective},
	journal = {Management Science},
	volume = {53},
	number = {7},
	year = {2007},
	month = {Jul},
	pages = {1086-1101},
	abstract = {The aim of this paper is twofold: (1) to conceptually understand membership dynamics in the open source software (OSS) community, and (2) to explore how different network characteristics (i.e., network size and connectivity) influence the stability of an OSS network. Through the lens of Ising theory, which is widely accepted in physics, we investigate basic patterns of interaction and present fresh conceptual insight into dynamic and reciprocal relations among OSS community members. We also perform computer simulations based on empirical data collected from two actual OSS communities. Key findings include: (1) membership herding is highly present when external influences (e.g., the availability of other OSS projects) are weak, but decreases significantly when external influences increase, (2) propensity for membership herding is most likely to be seen in a large network with random connectivity, and (3) for large networks, when external influences are weak, random connectivity will result in higher network strength than scale-free connectivity (as external influences increase, however, the reverse phenomenon is observed). In addition, scale-free connectivity appears to be less volatile than random connectivity in response to an increase in the strength of external influences. We conclude with several implications that may be of significance to OSS stakeholders in particular, and to a broader range of online communities in general.},
	keywords = {BEHAVIOR, DYNAMICS, ECONOMICS, INNOVATION, INVESTMENT, Ising theory, membership herding, MODEL, MOTIVATION, network connectivity, network stability, open source, PHASE-TRANSITION, UNCERTAINTY},
	isbn = {0025-1909},
	author = {Oh, Wonseok and Jeon, Sangyong}
}
@conference {997,
	title = {Mining CVS Repositories to Understand Open-Source Project Developer Roles},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {8 - 8},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {This paper presents a model to represent the interactions of distributed open-source software developers and utilizes data mining techniques to derive developer roles. The model is then applied on case studies of two open-source projects, ORAC-DR and Mediawiki with encouraging results.},
	keywords = {cvs, developer interaction, developers, mediawiki, orac-dr, roles, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300008.pdf},
	author = {Yu, Liguo and Ramaswamy, Srini}
}
@conference {999,
	title = {Mining Software Repositories with iSPAROL and a Software Evolution Ontology},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {10 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {One of the most important decisions researchers face when analyzing the evolution of software systems is the choice of a proper data analysis/exchange format. Most existing formats have to be processed with special programs written specifically for that purpose and are not easily extendible. Most scientists, therefore, use their own database(s) requiring each of them to repeat the work of writing the import/export programs to their format.

We present EvoOnt, a software repository data exchange format based on the Web Ontology Language (OWL). EvoOnt includes software, release, and bug-related information. Since OWL describes the semantics of the data, EvoOnt is (1) easily extendible, (2) comes with many existing tools, and (3) allows to derive assertions through its inherent Description Logic reasoning capabilities.

The paper also shows iSPARQL -- our SPARQL-based Semantic Web query engine containing similarity joins. Together with EvoOnt, iSPARQL can accomplish a sizable number of tasks sought in software repository mining projects, such as an assessment of the amount of change between versions or the detection of bad code smells. To illustrate the usefulness of EvoOnt (and iSPARQL), we perform a series of experiments with a real-world Java project. These show that a number of software analyses can be reduced to simple iSPARQL queries on an EvoOnt dataset.},
	keywords = {database, eclipse, evoont, java, owl, semantic, sparql},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300010.pdf},
	author = {Kiefer, Christoph and Bernstein, Abraham and Tappolet, Jonas}
}
@article {119,
	title = {Social network structures in open source software development teams},
	journal = {Journal of Database Management},
	volume = {18},
	number = {2},
	year = {2007},
	note = {"Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure."

no pdf},
	month = {Apr-Jun},
	pages = {25-40},
	abstract = {Drawing on social network theories and previous studies, this research examines the dynamics of social network structures in open source software (OSS) teams. Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure. The finding suggests that the interaction pattern of OSS projects evolves from a single hub at the beginning to a corel periphery model as the projects move forward.},
	keywords = {bug tracking, bugs, COMMUNITY, INNOVATION, longitudinal study, MODEL, open source, social, social network analysis, social networks, sourceforge, structure},
	isbn = {1063-8016},
	author = {Long, Y. and Siau, K.}
}
@conference {Tsunoda:2006:AOD:1137983.1138031,
	title = {Analyzing OSS developers{\textquoteright} working time using mailing lists archives},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {181{\textendash}182},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our mining question is {\textquotedblleft}when OSS developers work?{\textquotedblright} OSS developers{\textquoteright} working time may be a good indicator to understand the development style of a project. (For example, if many developers work in office hour, these might be daily works in a company.)},
	keywords = {developers, email, email archives, mailing lists, mining challenge, msr challenge, overtime work, postgresql, workload},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138031},
	url = {http://doi.acm.org/10.1145/1137983.1138031},
	attachments = {https://flosshub.org/sites/flosshub.org/files/181AnalyzingOSS.pdf},
	author = {Tsunoda, Masateru and Monden, Akito and Kakimoto, Takeshi and Kamei, Yasutaka and Matsumoto, Ken-ichi}
}
@conference {Gurbani:2006:CSC:1134285.1134352,
	title = {A case study of a corporate open source development model},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {472{\textendash}481},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source practices and tools have proven to be highly effective for overcoming the many problems of geographically distributed software development. We know relatively little, however, about the range of settings in which they work. In particular, can corporations use the open source development model effectively for software projects inside the corporate domain? Or are these tools and practices incompatible with development environments, management practices, and market-driven schedule and feature decisions typical of a commercial software house? We present a case study of open source software development methodology adopted by a significant commercial software project in the telecommunications domain. We extract a number of lessons learned from the experience, and identify open research questions.},
	keywords = {architecture, case study, open source, session initiation protocol, software development, vkg},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134352},
	url = {http://doi.acm.org/10.1145/1134285.1134352},
	author = {Gurbani, Vijay K. and Garvert, Anita and Herbsleb, James D.}
}
@conference {682,
	title = {Collaborative Maintenance in Large Open-Source Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {233 - 244},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The paper investigates collaborative work among maintainers of open source software by analyzing the logs of a set of 10 large projects. We inquire whether teamwork can be influenced by several characteristics of code. Preliminary results suggest that collaboration among maintainers in most large open-source projects seems to be positively influenced by file vintage and by Halstead volume of files, and negatively by McCabe complexity and size measured in SLOCs. These results could be consistent with an increased attractivity of files created early in the history of a project, and with maintainers being less attracted by more verbose code and by more complex code, although in this last case it might also reflect the fact that more complex files would be de facto more exclusive in terms of maintenance.
},
	keywords = {apache, COLLABORATION, complexity, cvs, gaim, gcc, ghostscript, halstead, lines of code, loc, mccabe, mozilla, netbsd, openssh, postgresql, python, sloc},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Collaborative\%20Maintenance.pdf},
	author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice}
}
@conference {Amor:2006:EEC:1139113.1139116,
	title = {Effort Estimation by Characterizing Developer Activity},
	booktitle = {Proceedings of the 2006 International Workshop on Economics Driven Software Engineering Research},
	series = {EDSER {\textquoteright}06},
	year = {2006},
	pages = {3{\textendash}6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {During the latest years libre (free, open source) software has gained a lot of attention from the industry. Following this interest, the research community is also studying it. For instance, many teams are performing quantitative analysis on the large quantity of data which is publicly available from the development repositories maintained by libre software projects. However, not much of this research is focused on cost or effort estimations, despite its importance (for instance, for companies developing libre software or collaborating with libre software projects), and the availability of some data which could be useful for this purpose. Our position is that classical effort estimation models can be improved from the study of these data, at least when applied to libre software. In this paper, we focus on the characterization of developer activity, which we argue can improve effort estimation. This activity can be traced with a lot of detail, and the resulting data can also be used for validation of any effort estimation model.
},
	keywords = {developer characterization, effort estimation, mining software repositories, open source software, software economics},
	isbn = {1-59593-396-4},
	doi = {10.1145/1139113.1139116},
	url = {http://doi.acm.org/10.1145/1139113.1139116},
	author = {Amor, Juan Jose and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@conference {Robles:2006:GLD:1137983.1138017,
	title = {Geographic location of developers at SourceForge},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {144{\textendash}150},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The development of libre (free/open source) software is usually performed by geographically distributed teams. Participation in most cases is voluntary, sometimes sporadic, and often not framed by a pre-defined management structure. This means that anybody can contribute, and in principle no national origin has advantages over others, except for the differences in availability and quality of Internet connections and language. However, differences in participation across regions do exist, although there are little studies about them. In this paper we present some data which can be the basis for some of those studies. We have taken the database of users registered at SourceForge, the largest libre software development web-based platform, and have inferred their geographical locations. For this, we have applied several techniques and heuristics on the available data (mainly e-mail addresses and time zones), which are presented and discussed in detail. The results show a snapshot of the regional distribution of SourceForge users, which may be a good proxy of the actual distribution of libre software developers. In addition, the methodology may be of interest for similar studies in other domains, when the available data is similar (as is the case of mailing lists related to software projects).},
	keywords = {distributed, email, email address, free software, geographical location, geography, libre software, mining software repositories, open source software, sourceforge, timezone},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138017},
	url = {http://doi.acm.org/10.1145/1137983.1138017},
	attachments = {https://flosshub.org/sites/flosshub.org/files/144GeographicLocation.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@conference {Askari:2006:ITE:1137983.1138013,
	title = {Information theoretic evaluation of change prediction models for large-scale software},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {126{\textendash}132},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper, we analyze the data extracted from several open source software repositories. We observe that the change data follows a Zipf distribution. Based on the extracted data, we then develop three probabilistic models to predict which files will have changes or bugs. The first model is Maximum Likelihood Estimation (MLE), which simply counts the number of events, i.e., changes or bugs, that happen to each file and normalizes the counts to compute a probability distribution. The second model is Reflexive Exponential Decay (RED) in which we postulate that the predictive rate of modification in a file is incremented by any modification to that file and decays exponentially. The third model is called RED-Co-Change. With each modification to a given file, the RED-Co-Change model not only increments its predictive rate, but also increments the rate for other files that are related to the given file through previous co-changes. We then present an information-theoretic approach to evaluate the performance of different prediction models. In this approach, the closeness of model distribution to the actual unknown probability distribution of the system is measured using cross entropy. We evaluate our prediction models empirically using the proposed information-theoretic approach for six large open source systems. Based on this evaluation, we observe that of our three prediction models, the RED-Co-Change model predicts the distribution that is closest to the actual distribution for all the studied systems.},
	keywords = {bugs, change analysis, cvs, evaluation approach, file, freebsd, information theory, kde, koffice, log files, netbsd, openbsd, postgresql, prediction, prediction models, scm, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138013},
	url = {http://doi.acm.org/10.1145/1137983.1138013},
	attachments = {https://flosshub.org/sites/flosshub.org/files/126InformationTheoretic.pdf},
	author = {Askari, Mina and Holt, Ric}
}
@article {1232,
	title = {Integration of libre software applications to create a collaborative work platform for researchers at GET},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	month = {07/2006},
	pages = {1-16},
	publisher = {IGI Global},
	abstract = {Libre software provides powerful applications ready to be integrated for the build-up of platforms for internal use in organizations. We describe the architecture of the collaborative work platform which we have integrated, designed for researchers at GET. We present the elements we have learned during this project in particular with respect to contribution to external libre projects, in order to better ensure the maintainability of the internal applications, and to phpGroupware as a framework for specific applications development.},
	keywords = {collaborative work environment, contribution, free software, groupware, in-house applications, libre software, open source software, OpenLDAP, phpGroupware, PicoLibre, ProGET, Sympa, TWiki, WebDAV, wiki},
	author = {Olivier Berger and Christian Bac and Benoit Hamet}
}
@article {Grewal:2006:LLL:1246148.1246155,
	title = {Location, Location, Location: How Network Embeddedness Affects Project Success in Open Source Systems},
	journal = {Management Science},
	volume = {52},
	number = {7},
	year = {2006},
	month = {July},
	pages = {1043{\textendash}1056},
	publisher = {INFORMS},
	address = {Institute for Operations Research and the Management Sciences (INFORMS), Linthicum, Maryland, USA},
	abstract = {The community-based model for software development in open source environments is becoming a viable alternative to traditional firm-based models. To better understand the workings of open source environments, we examine the effects of network embeddedness---or the nature of the relationship among projects and developers---on the success of open source projects. We find that considerable heterogeneity exists in the network embeddedness of open source projects and project managers. We use a visual representation of the affiliation network of projects and developers as well as a formal statistical analysis to demonstrate this heterogeneity and to investigate how these structures differ across projects and project managers. Our main results surround the effect of this differential network embeddedness on project success. We find that network embeddedness has strong and significant effects on both technical and commercial success, but that those effects are quite complex. We use latent class regression analysis to show that multiple regimes exist and that some of the effects of network embeddedness are positive under some regimes and negative under others. We use project age and number of page views to provide insights into the direction of the effect of network embeddedness on project success. Our findings show that different aspects of network embeddedness have powerful but subtle effects on project success and suggest that this is a rich environment for further study.},
	keywords = {affiliation network, age, developers, latent class analysis, network embeddedness, open source software, page views, perl, project success, registration, sourceforge},
	issn = {0025-1909},
	doi = {10.1287/mnsc.1060.0550},
	url = {http://portal.acm.org/citation.cfm?id=1246148.1246155},
	author = {Grewal, Rajdeep and Lilien, Gary L. and Mallapragada, Girish}
}
@article {Yu:2006:MKO:1150566.1150571,
	title = {Maintainability of the kernels of open-source operating systems: A comparison of Linux with FreeBSD, NetBSD, and OpenBSD},
	journal = {J. Syst. Softw.},
	volume = {79},
	year = {2006},
	note = {"Data regarding the number and total number of lines of code of kernel and nonkernel modules in the four operating systems are provided in Table 1"
loc, kloc, number of kernel modules, number of nonkernel modules
size 
c files
.h files},
	month = {June},
	pages = {807{\textendash}815},
	publisher = {Elsevier Science Inc.},
	address = {New York, NY, USA},
	abstract = {We compared and contrasted the maintainability of four open-source operating systems: Linux, FreeBSD, NetBSD, and OpenBSD. We used our categorization of common coupling in kernel-based software to highlight future maintenance problems. An unsafe definition is a definition of a global variable that can affect a kernel module if that definition is changed. For each operating system we determined a number of measures, including the number of global variables, the number of instances of global variables in the kernel and overall, as well as the number of unsafe definitions in the kernel and overall. We also computed the value of each our measures per kernel KLOC and per KLOC overall. For every measure and every ratio, Linux compared unfavorably with FreeBSD, NetBSD, and OpenBSD. Accordingly, we are concerned about the future maintainability of Linux. },
	keywords = {abiword, Common coupling, coupling, Definition-use analysis, freebsd, kernel, lines of code, linux, linux kernel, loc, Maintainability, modules, netbsd, Open-source software, openbsd, source code},
	issn = {0164-1212},
	doi = {http://dx.doi.org/10.1016/j.jss.2005.08.014},
	url = {http://dx.doi.org/10.1016/j.jss.2005.08.014},
	attachments = {https://flosshub.org/sites/flosshub.org/files/YuSchachChen.pdf},
	author = {Yu, Liguo and Schach, Stephen R. and Chen, Kai and Heller, Gillian Z. and Offutt, Jeff}
}
@conference {Bird:2006:MES:1137983.1138016,
	title = {Mining email social networks},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {137{\textendash}143},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Communication \& Co-ordination activities are central to large software projects, but are difficult to observe and study in traditional (closed-source, commercial) settings because of the prevalence of informal, direct communication modes. OSS projects, on the other hand, use the internet as the communication medium,and typically conduct discussions in an open, public manner. As a result, the email archives of OSS projects provide a useful trace of the communication and co-ordination activities of the participants. However, there are various challenges that must be addressed before this data can be effectively mined. Once this is done, we can construct social networks of email correspondents, and begin to address some interesting questions. These include questions relating to participation in the email; the social status of different types of OSS participants; the relationship of email activity and commit activity (in the CVS repositories) and the relationship of social status with commit activity. In this paper, we begin with a discussion of our infrastructure (including a novel use of Scientific Workflow software) and then discuss our approach to mining the email archives; and finally we present some preliminary results from our data analysis.},
	keywords = {communication, contributions, developers, email, email archives, mailing lists, open source, social networks},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138016},
	url = {http://doi.acm.org/10.1145/1137983.1138016},
	attachments = {https://flosshub.org/sites/flosshub.org/files/137MiningEmail.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Gertz, Michael and Swaminathan, Anand}
}
@conference {Bird:2006:MES:1137983.1138033,
	title = {Mining email social networks in Postgres},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {185{\textendash}186},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open Source Software (OSS) projects provide a unique opportunity to gather and analyze publicly available historical data. The Postgres SQL server, for example, has over seven years of recorded development and communication activity. We mined data from both the source code repository and the mailing list archives to examine the relationship between communication and development in Postgres. Along the way, we had to deal with the difficult challenge of resolving email aliases. We used a number of social network analysis measures and statistical techniques to analyze this data. We present our findings in this paper.},
	keywords = {developers, email, email archives, open source, postgresql, scm, social network analysis, social networks, source code, status},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138033},
	url = {http://doi.acm.org/10.1145/1137983.1138033},
	attachments = {https://flosshub.org/sites/flosshub.org/files/185MiningEmail.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Gertz, Michael and Swaminathan, Anand}
}
@article {1124,
	title = {Motivation, Governance, and the Viability of Hybrid Forms in Open Source Software Development},
	journal = {Management Science},
	volume = {52},
	year = {2006},
	note = {"Data from three primary sources informed this research (Table 1). All data were collected in 2001{\textendash}2002."
Online project documentation: All publicly available project descriptions, charters, bylaws, meeting minutes, etc.
Mailing lists: Over 2,000 messages read over a three-month period prior to interviews
Interviews 
"Ireadallpostingstoproject-specific and general mailing lists for both communities for a three-month period preceding the interviews. Over 2,000 messages were posted during this period. Read- ing these messages allowed me to gain familiarity with the technology..."},
	month = {07/2006},
	pages = {1000 - 1014},
	abstract = {Open source software projects rely on the voluntary efforts of thousands of software developers, yet we know little about why developers choose to participate in this collective development process. This paper inductively derives a framework for understanding participation from the perspective of the individual software developer based on data from two software communities with different governance structures.

In both communities, a need for software-related improvements drives initial participation. The majority of participants leave the community once their needs are met, however, a small subset remains involved. For this set of developers, motives evolve over time and participation becomes a hobby. These hobbyists are critical to the long-term viability of the software code: They take on tasks that might otherwise go undone and work to maintain the simplicity and modularity of the code. Governance structures affect this evolution of motives. Implications for firms interested in implementing hybrid strategies designed to combine the advantages of open source software development with proprietary ownership and control are discussed.},
	keywords = {email, email archives, governance, INNOVATION, interview, mailing list, MOTIVATION, open source software development, Volunteers},
	issn = {1526-5501},
	doi = {10.1287/mnsc.1060.0553},
	url = {http://faculty.washington.edu/skshah/Shah\%20-\%20Motivation,\%20Governance,\%20Hybrid\%20Forms.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Shah\%20-\%20Motivation\%2C\%20Governance\%2C\%20Hybrid\%20Forms.pdf},
	author = {Shah, Sonali K.}
}
@article {895,
	title = {Multi-Modal Modeling, Analysis and Validation of Open Source Software Development Processes},
	journal = {Intern. J. Internet Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {49-63},
	abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies have revealed that development processes in F/OSSD projects are different in a number of ways. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software development processes found in F/OSSD projects, with examples drawn from studies of the software requirements process found in the NetBeans.org project.},
	keywords = {empirical studies of software engineering, open source software development, process modeling, requirements processes, software process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi-Jensen-Noll-Elliott-OSSC05.pdf},
	author = {Walt Scacchi and Chris Jensen and Noll, J. and Elliott, M.}
}
@article {1088,
	title = {Self-Organization Patterns in Wasp and Open Source Communities},
	journal = {IEEE Intelligent Systems},
	volume = {21},
	year = {2006},
	note = {"To investigate such claims, we studied an OSS community{\textquoteright}s social network from a dataset describing the email activity of 120 different software teams"
"Our test data originated from Sourceforge (http://sourceforge.net), a large open source project repository, and included communi- ties ranging from very small networks with one or two members to large networks with thousands of members."
"we limited our consideration to email traffic associated with bug fixes and bug reporting. As other researchers have shown[5] this email subset allows an effective reconstruction of the software community{\textquoteright}s social network."
"We thank Kevin Crowston and James Howison for making their software data publicly available."},
	month = {03/2006},
	pages = {36 - 40},
	abstract = {In this paper, we conducted a comparative study of how social organization takes place in a wasp colony and OSS developer communities. Both these systems display similar global organization patterns, such as hierarchies and clear labor divisions. As our analysis shows, both systems also define interacting agent networks with similar common features that reflect limited information sharing among agents. As far as we know, this is the first research study analyzing the patterns and functional significance of these systems{\textquoteright} weighted-interaction networks. By illuminating the extent to which self-organization is responsible for patterns such as hierarchical structure, we can gain insight into the origins of organization in OSS communities.},
	keywords = {agents, decentralization, developers, email, email archives, flossmole, hierarchy, labor division, organization, self-organizing teams, social network analysis, social networks, sourceforge, teams, wasps},
	issn = {1541-1672},
	doi = {10.1109/MIS.2006.34},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.95.5574\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/valverde.pdf},
	author = {Valverde, S. and Theraulaz, G. and Gautrais, J. and Fourcassie, V. and Sole, R.V.}
}
@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.}
}
@conference {779,
	title = {Carrot2 Clustering Framework},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {298-299},
	abstract = {Carrot2 is an Open Source framework for research experiments with querying various textual data sources, processing and presentation of the results. Its main goal is to promote component reuse in order to reduce the effort involved in the development of Information Retrieval software. So far, the most successful and popular application of Carrot2 has been organizing results of Internet searches into easy to browse thematic groups called clusters. In this area, the project successfully competes with commercial counterparts like Vivisimo or iBoogie.},
	keywords = {BSD license, cluster, clustering framework, open source, research, result},
	url = {http://pascal.case.unibz.it/handle/2038/788},
	author = {Weiss, Dawid and Osi{\textasciiacute}nski, Stanis{\l}aw}
}
@conference {795,
	title = {The challenges of creating open source education software: the Gild experience},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {338-340},
	keywords = {COMMUNITY, eclipse, learning environment, novice programmers, open source, programming environment},
	url = {http://pascal.case.unibz.it/handle/2038/1539},
	author = {Daniel M. German and Rigby, Peter and Cubranic, Davor and Storey, Margaret-Anne and Thomson, Suzanne}
}
@article {10.1109/TSE.2005.89,
	title = {Comparing High-Change Modules and Modules with the Highest Measurement Values in Two Large-Scale Open-Source Products},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	year = {2005},
	pages = {625-642},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {Identifying change-prone modules can enable software developers to take focused preventive actions that can reduce maintenance costs and improve quality. Some researchers observed a correlation between change proneness and structural measures, such as size, coupling, cohesion, and inheritance measures. However, the modules with the highest measurement values were not found to be the most troublesome modules by some of our colleagues in industry, which was confirmed by our previous study of six large-scale industrial products. To obtain additional evidence, we identified and compared high-change modules and modules with the highest measurement values in two large-scale open-source products, Mozilla and OpenOffice, and we characterized the relationship between them. Contrary to common intuition, we found through formal hypothesis testing that the top modules in change-count rankings and the modules with the highest measurement values were different. In addition, we observed that high-change modules had fairly high places in measurement rankings, but not the highest places. The accumulated findings from these two open-source products, together with our previous similar findings for six closed-source products, should provide practitioners with additional guidance in identifying the change-prone modules.},
	keywords = {mozilla, openoffice},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2005.89},
	author = {G{\"u}nes Koru, A. and Tian, Jeff (Jianhui)}
}
@article {102,
	title = {Empirical validation of object-oriented metrics on open source software for fault prediction},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	number = {10},
	year = {2005},
	note = {"This paper describes how we calculated the object-oriented metrics given by Chidamber and Kemerer to illustrate how fault-proneness detection of the source code of the open source Web and e-mail suite called Mozilla can be carried out. We checked the values obtained against the number of bugs found in its bug database - called Bugzilla - using regression and machine learning methods to validate the usefulness of these metrics for fault-proneness prediction. We also compared the metrics of several versions of Mozilla to see how the predicted fault-proneness of the software system changed during its development cycle."
metrics, 
wmc weighted methods per class, 
dit depth of inheritance, 
rfc response for a class,
noc number of children,
cbo coupling between object classes,
cohesion,
lines of code, loc, sloc
chidamber and kemerer metrics},
	pages = {897-910},
	abstract = {Open source software systems are becoming increasingly important these days. Many companies are investing in open source projects and lots of them are also using such software in their own work. But, because open source software is often developed with a different management style than the industrial ones, the quality and reliability of the code needs to be studied. Hence, the characteristics of the source code of these projects need to be measured to obtain more information about it. This paper describes how we calculated the object-oriented metrics given by Chidamber and Kemerer to illustrate how fault-proneness detection of the source code of the open source Web and e-mail suite called Mozilla can be carried out. We checked the values obtained against the number of bugs found in its bug database - called Bugzilla - using regression and machine learning methods to validate the usefulness of these metrics for fault-proneness prediction. We also compared the metrics of several versions of Mozilla to see how the predicted fault-proneness of the software system changed during its development cycle.},
	keywords = {bugs, bugzilla, cbo, defects, dit, fault-prone modules, faults, lcom, lcomn, loc, metrics, mozilla, noc, object-oriented, rfc, source code, wmc},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.115.8372\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Gyimothy.pdf},
	author = {Gyimothy, T. and Ferenc, R. and Siket, I.}
}
@conference {792,
	title = {Experiences teaching a graduate course in Open Source Software Engineering},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {326-328},
	abstract = {This paper describes the early experiences of a graduate course in open source software engineering at the Department of Computer Science at the University Victoria. It includes a description of the motivation for the course, its structure and evaluation methods. It concludes with a discussion of the lessons learned and its future.},
	keywords = {course, FOSS, MOTIVATION, open source, open source software engineering},
	url = {http://pascal.case.unibz.it/handle/2038/971},
	author = {Daniel M. German}
}
@conference {775,
	title = {eZPA portale e-government per enti locali},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {289-290},
	abstract = {Tra i numerosi settori in cui Internet sta intervenendo con una forte carica di {\textquotedblleft}modernizzazione{\textquotedblright}, quello dell{\textquoteright}e- Government, inteso come possibilit{\`a} per tutti gli utenti, per tutti i cittadini, di gestire il rapporto con la Pubblica Amministrazione, anche on line, sta producendo gli effetti maggiormente innovativi. L{\textquoteright}occasione fornitaci dall{\textquoteright}amministrazione del Comune di Ozzano dell{\textquoteright}Emilia ha permesso di sviluppare l{\textquoteright}applicazione eZPA, scritta con software a codice sorgente aperto e rilasciata con licenza GNU-GPL (General Publish Licence), liberamente utilizzabile e modificabile. Il portale consente la fruibilit{\`a} telematica dei servizi comunali sia ai clienti esterni (cittadini e imprese), sia agli utenti interni (dipendenti e collaboratori comunali), attraverso una struttura di sportelli fisici/virtuali. In particolare, l{\textquoteright}utilizzo della metafora di comunicazione {\textquotedblleft}Evento della vita{\textquotedblright},[1] raccomandata dalle linee guida del Ministro per l{\textquoteright}Innovazione e le Tecnologie, ha ...},
	keywords = {e-government, enti locali, INTERNET, open source, pubblica amministrazione},
	url = {http://pascal.case.unibz.it/handle/2038/874},
	author = {Colognesi, Cristina and Guandalini, Stefano}
}
@conference {773,
	title = {Fare Open Source all{\textquoteright}Istat: il generatore di data-entry per indagini statistiche},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {283-286},
	abstract = {Viene presentata una prima esperienza di sviluppo di software Open Source all{\textquoteright}Istat, che riguarda un sistema generalizzato di data-entry per indagini statistiche. L{\textquoteright}applicazione, in via di rilascio, copre la fase di acquisizione dati propria delle indagini statistiche e consentir{\`a} di generare maschere che potranno essere utilizzate sia in Intranet che sul Web. L{\textquoteright}applicazione descritta, che utilizza PHP e XML come tecnologie fondanti, rappresenta un{\textquoteright}esperienza concreta di sviluppo Open Source nella quale l{\textquoteright}Istat vuole riversare le proprie esperienze specifiche, mettendole poi a disposizione delle altre strutture interessate.},
	keywords = {data-entry, indagini statistiche, open source, PHP, web, XML},
	url = {http://pascal.case.unibz.it/handle/2038/903},
	author = {Altarocca, Francesco and Vaccari, Carlo}
}
@conference {786,
	title = {Future Development in the European Software Industry: Patentability of Computer Programs or Open Source Software?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {311-313},
	abstract = {Economic literature has treated the patent system as an indispensable tool to incentive inventive activity and to foster diffusion of technological improvements, but recent developments have brought at the center of the stage the Open Source phenomenon which is based on completely different mechanisms among which the free disclosure of the inventive steps. This work analyzes changes that are taking place into patent literature in order to give account of the desirability of patents in software sector. In addition some ideas on empirical analysis are put forward: the possibility of measuring the relationship between patents and input of innovation process in the software sector and the influence that private firms will have on Open Source developers motivations.},
	keywords = {european, market segment, open source, os, patent, patent literature, patentability, software industry, software sector},
	url = {http://hdl.handle.net/2038/966},
	author = {Rentocchini, Francesco}
}
@conference {781,
	title = {Idealism and Commercialism {\textendash} Developing Free/Libre and Open Source Software in Private Businesses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {301-302},
	abstract = {This paper presents a PhD research project undertaken as part of a larger project aimed at paying sociological attention to different forms of distribution of knowledge, including program code. We want to investigate empirically how the commons knows as free/open source software is actually made. In my PhD project I study the use and development of FLOSS in private businesses, focusing on professional developers working in private businesses and at the same time participating in the FLOSS community. The theoretical starting point is theories of power, dominance and legitimacy by Max Weber and Pierre Bourdieu.},
	keywords = {dominance, FLOSS, FLOSS community, free/libre, legitimacy, linux, open source, Private Businesses, social organisation, theories of power},
	url = {http://pascal.case.unibz.it/handle/2038/970},
	author = {Lundestad, Christian V.}
}
@conference {784,
	title = {An Investigation of Developer and User Activity In FLOSS Projects},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {307-308},
	abstract = {This document outlines research plans to investigate the evolution of a set of FLOSS (Free, Libre, and Open Source Software) projects and their communities by looking at patterns of developer and user activity through a combination of analysis of archived material and interaction with the project communities. The goal of the proposed research is to better understand the dynamics within FLOSS projects and how some projects become successful.},
	keywords = {developer, development, FLOSS, FLOSS project, open source, pattern, portal, project},
	url = {http://pascal.case.unibz.it/handle/2038/712},
	author = {Gale, Stephen}
}
@conference {789,
	title = {Legal issues of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {320-321},
	abstract = {From the legal standpoint, Open Source amounts to distributing rights and obligations in software license agreements in such a way, that they would (1) both grant users control over the program and (2) facilitate the sharing of improvements. The Open Source idea aims at reversing the process usually referred to as proprietary licensing and equaling the rights of the users with these of the authors. To some extent, it attempts to destroy monopolies created by copyright laws and to prevent them to arise again. There is much in the discussion on the legal issues of Open Source. The first voices came from the programmers who started the movement.},
	keywords = {cooperation, copyright law, freedom, intellectual property, legal issue, license, open source software},
	url = {http://pascal.case.unibz.it/handle/2038/974},
	author = {Siewicz, Krzysztof}
}
@conference {777,
	title = {Live! I-Learn @ Home},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {294-295},
	abstract = {In this paper we present a live CD based on GNU/Linux (Knoppix), customized in order to supply a complete working and studying environment for the students of the Corso di Studi in Informatica. In particular, it supplies the Moodle course management system for e-learning complete of the courses of the first year. The aim is to enable the use of such resources off-line and without requiring special skills that will be achieved by studying but that newbies do not have.},
	keywords = {e-learning, environment, GNU/Linux, java, open source, technology},
	url = {http://pascal.case.unibz.it/handle/2038/977},
	author = {Baldoni, Matteo and Baroglio, Cristina and Roversi, Luca and Grandi, Claudio}
}
@conference {791,
	title = {Looking at Free and Open Source Software: A Study about F/OSS Developers{\textquoteright} Culture},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {324-325},
	abstract = {My work will be a cultural study of a F/OSS development project, mixing a symmetric approach with the interaction analysis by Erving Goffman. Methodologically I will approach cyber {\textendash} ethnography.},
	keywords = {cultural analysis, cultural study, cyber, F/OSS developers, open source, software development},
	url = {http://pascal.case.unibz.it/handle/2038/968},
	author = {Teli, Maurizio}
}
@conference {774,
	title = {Migrazione di un Sistema Informativo da UNIX-AIX a UNIX-Linux},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {287-288},
	abstract = {Il presente documento ha come obiettivo quello di descrivere la politica adottata dall{\textquoteright}Istituto Nazionale di Statistica rispetto all{\textquoteright}uso del software Open Source. In particolare vengono descritti i sistemi che attualmente operano su piattaforma Linux, quelli che sono in fase di migrazione e le scelte che si sono fatte nel caso di convivenza tra sistemi {\textquotedblleft}open{\textquotedblright} e sistemi {\textquotedblleft}proprietari{\textquotedblright}. Viene inoltre illustrata l{\textquoteright}architettura hardware scelta nel caso della migrazione di un sistema complesso da piattaforma interamente proprietaria (UNIX AIX) a piattaforma con sistema operativo open Linux Red Hat.},
	keywords = {architettura hardware, linux, migrazione, open source, server, sistema informativo, sistema proprietario, unix aix},
	url = {http://pascal.case.unibz.it/handle/2038/978},
	author = {Colasanti, Cecilia and Patruno, Vincenzo and Vaccari, Carlo}
}
@conference {Fischer:2005:MED:1083142.1083145,
	title = {Mining evolution data of a product family},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {12-16},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Diversification of software assets through changing requirements impose a constant challenge on the developers and maintainers of large software systems. Recent research has addressed the mining for data in software repositories of single products ranging from fine- to coarse grained analyses. But so far, little attention has been payed to mining data about the evolution of product families. In this work, we study the evolution and commonalities of three variants of the BSD (Berkeley Software Distribution), a large open source operating system. The research questions we tackle are concerned with how to generate high level views of the system discovering and indicating evolutionary highlights. To process the large amount of data, we extended our previously developed approach for storing release history information to support the analysis of product families. In a case study we apply our approach on data from three different code repositories representing about 8.5GB of data and 10 years of active development.},
	keywords = {bsd, change analysis, change history, cvs, evolution, freebsd, netbsd, openbsd, release history, source code, text mining},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083145},
	url = {http://doi.acm.org/10.1145/1082983.1083145},
	attachments = {https://flosshub.org/sites/flosshub.org/files/12MiningEvolution.pdf},
	author = {Fischer, Michael and Oberleitner, Johann and Ratzinger, Jacek and Gall, Harald}
}
@conference {Huang:2005:MVH:1083142.1083158,
	title = {Mining version histories to verify the learning process of Legitimate Peripheral Participants},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {84-88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Since code revisions reflect the extent of human involvement in the software development process, revision histories reveal the interactions and interfaces between developers and modules.We therefore divide developers and modules into groups according to the revision histories of the open source software repository, for example, sourceforge.net. To describe the interactions in the open source development process, we use a representative model, Legitimate Peripheral Participation (LPP) [6], to divide developers into groups such as core and peripheral teams, based on the evolutionary process of learning behavior.With the conventional module relationship, we divide modules into kernel and non-kernel types (such as UI). In the past, groups of developers and modules have been partitioned naturally with informal criteria. In this work, however, we propose a developer-module relationship model to analyze the grouping structures between developers and modules. Our results show some process cases of relative importance on the constructed graph of project development. The graph reveals certain subtle relationships in the interactions between core and non-core team developers, and the interfaces between kernel and non-kernel modules.},
	keywords = {awstats, bzflag, cvs, filezilla, gallery, Legitimate Peripheral Participants (LPP), moodle, open boundary, open source software development process, phpmyadmin, social networks, sourceforge},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083158},
	url = {http://doi.acm.org/10.1145/1082983.1083158},
	attachments = {https://flosshub.org/sites/flosshub.org/files/84MiningVersion.pdf},
	author = {Huang, Shih-Kun and Liu, Kang-min}
}
@conference {803,
	title = {Open Source firms: from community to business},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {362-363},
	abstract = {A large body of literature is now addressing the Open Source (OS) phenomenon. Economic scholars have deeply investigated the incentives of people working within OS community projects; the software production models in absence of explicit hierarchical structures; the successful dissemination of OS programs in environments dominated by proprietary standards; the peculiarities in the management of intellectual property within the OS framework. Theoretical contributions have coupled with the collection of extensive empirical evidence mainly through surveys taken on individual developers. Nowadays a new trend is shaping the OS movement: more and more firms are entering the market by offering software solutions based on the new paradigm (Open Source firms).},
	keywords = {business, COMMUNITY, firms, Open Source firms},
	url = {http://pascal.case.unibz.it/handle/2038/1265},
	author = {Andrea Bonaccorsi and Cristina Rossi}
}
@conference {772,
	title = {OTRS: un sistema a ticket per la gestione dell{\textquoteright}help desk},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {281},
	abstract = {Descriviamo l{\textquoteright}esperienza di utilizzo di un software a codice sorgente aperto per la gestione a ticket dell{\textquoteright}help desk informatico del D.I.S.I. (Dipartimento di Informatica e Scienze delll{\textquoteright}Informazione) dell{\textquoteright}Universit{\`a} degli Studi di Genova.},
	keywords = {help desk, open source, ticketing system, trouble ticket},
	url = {http://pascal.case.unibz.it/handle/2038/1423},
	author = {Bencetti, Stefano and Verduci, Gianni}
}
@conference {Phadke:2005:PRM:1145319.1145337,
	title = {Predicting risky modules in open-source software for high-performance computing},
	booktitle = {Proceedings of the second international workshop on Software engineering for high performance computing system applications},
	series = {SE-HPCS {\textquoteright}05},
	year = {2005},
	pages = {60{\textendash}64},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper presents the position that software-quality modeling of open-source software for high-performance computing can identify modules that have a high risk of bugs.Given the source code for a recent release, a model can predict which modules are likely to have bugs, based on data from past releases. If a user knows which software modules correspond to functionality of interest, then risks to operations become apparent. If the risks are too great, the user may prefer not to upgrade to the most recent release.Of course, such predictions are never perfect. After release, bugs are discovered. Some bugs are missed by the model, and some predicted errors do not occur. A successful model will be accurate enough for informed management action at the time of the predictions.As evidence for this position, this paper summarizes a case study of the Portable Extensible Toolkit for Scientific Computation (PETSC), which is a mathematical library for high-performance computing. Data was drawn from source-code and configuration management logs. The accuracy of logistic-regression and decision-tree models indicated that the methodology is promising. The case study also illustrated several modeling issues.},
	keywords = {C4.5, decision trees, empirical case study, high performance computing, logistic regression, Open-source software, PETSc, software metrics, software quality model, software reliability},
	isbn = {1-59593-117-1},
	doi = {10.1145/1145319.1145337},
	url = {http://doi.acm.org/10.1145/1145319.1145337},
	author = {Phadke, Amit A. and Allen, Edward B.}
}
@conference {785,
	title = {Quality Improvement in Volunteer Free Software Projects: Exploring the Impact of Release Management},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {309-310},
	abstract = {Even though free software has achieved great popularity and success in recent years, there are a number of product quality challenges facing the open source development model. There is significant room for further quality improvement and one area that deserves special attention is release management. This research will identify problems with current release practices, verify possible advantages of an increasingly popular release model, and develop interventions to improve release management in free software projects. The research also aims to answer the fundamental question as to how volunteer projects can deliver predictable and high quality software.},
	keywords = {free software, open source, process improvement, quality assurance, release management, volunteer projects},
	url = {http://pascal.case.unibz.it/handle/2038/1429},
	author = {Martin Michlmayr}
}
@conference {794,
	title = {SchoolTool: Defining Our Niche in the Open Source Architecture of Schools},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {334-337},
	keywords = {information system, open source, school, student},
	url = {http://pascal.case.unibz.it/handle/2038/1436},
	author = {Hoffman, Tom}
}
@conference {Hindle:2005:SFM:1083142.1083161,
	title = {SCQL: a formal model and a query language for source control repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {100-104},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Source Control Repositories are used in most software projects to store revisions to source code files. These repositories operate at the file level and support multiple users. A generalized formal model of source control repositories is described herein. The model is a graph in which the different entities stored in the repository become vertices and their relationships become edges. We then define SCQL, a first order, and temporal logic based query language for source control repositories. We demonstrate how SCQL can be used to specify some questions and then evaluate them using the source control repositories of five different large software projects.},
	keywords = {evolution, file, gnumeric, modperl, openssl, revision, samba, scm, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083161},
	url = {http://doi.acm.org/10.1145/1082983.1083161},
	attachments = {https://flosshub.org/sites/flosshub.org/files/100scql.pdf},
	author = {Hindle, Abram and Daniel M. German}
}
@article {springerlink:10.1007/s10606-005-9000-1,
	title = {Socialization in an Open Source Software Community: A Socio-Technical Analysis},
	journal = {Computer Supported Cooperative Work (CSCW)},
	volume = {14},
	year = {2005},
	note = {"I present the results of my analyses of participation patterns in a particular OSS project, used as a case study: Python. More precisely, I use the Open Source Project Browser to qualitatively track and analyze the trajectories of several project members who evolved (or not) into full-fledged participants. This allows me to later discuss how socialization proceeds in an OSS community such as Python"

"Over the course of 2002, I progressively retrieved the entire email archive of python-dev (the developers{\textquoteright} mailing list) and the CVS source tree for the project. "

"I read the entirety of the messages written by these participants and also looked at the software code they produced. There were striking similarities between their progressions over time, which I will de- scribe shortly. Overall the trajectory of these participants reflects successful socialization in Python: an evolution from newcomer to developer."

http://www2.parc.com/csl/members/nicolas/documents/JCSCW-OSS.pdf},
	pages = {323-368},
	publisher = {Springer Netherlands},
	abstract = {Open Source Software (OSS) development is often characterized as a fundamentally new way to develop software. Past analyses and discussions, however, have treated OSS projects and their organization mostly as a static phenomenon. Consequently, we do not know how these communities of software developers are sustained and reproduced over time through the progressive integration of new members. To shed light on this issue I report on my analyses of socialization in a particular OSS community. In particular, I document the relationships OSS newcomers develop over time with both the social and material aspects of a project. To do so, I combine two mutually informing activities: ethnography and the use of software specially designed to visualize and explore the interacting networks of human and material resources incorporated in the email and code databases of OSS. Socialization in this community is analyzed from two perspectives: as an individual learning process and as a political process. From these analyses it appears that successful participants progressively construct identities as software craftsmen, and that this process is punctuated by specific rites of passage. Successful participants also understand the political nature of software development and progressively enroll a network of human and material allies to support their efforts. I conclude by discussing how these results could inform the design of software to support socialization in OSS projects, as well as practical implications for the future of these projects.},
	keywords = {cvs, developers, email, email archive, mailing list, open source project browser, participation, python, scm, source code, team, tools},
	issn = {0925-9724},
	url = {http://dx.doi.org/10.1007/s10606-005-9000-1},
	author = {DUCHENEAUT, NICOLAS}
}
@conference {790,
	title = {	Socialization practices in FLOSS development teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {322-323},
	abstract = {Socialization of new members into Free/Libre Open Source Software (FLOSS) development teams is an important but little studied process in producing effective teams of this type. This is a dissertation proposal for a virtual ethnographic study that looks at the mechanisms and processes used to socialize new members into the team in order to help maintain a common group identity and focus.},
	keywords = {development team, FLOSS, member, open source, socialization},
	url = {http://pascal.case.unibz.it/handle/2038/1438},
	author = {Chengetai Masango}
}
@conference {Fielding:2005:SAO:1062455.1062474,
	title = {Software architecture in an open source world},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {43{\textendash}43},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In spite of the hype and hysteria surrounding open source software development, there is very little that can be said of open source in general. Open source projects range in scope from the miniscule, such as the thousands of non-maintained code dumps left behind at the end of class projects, dissertations, and failed commercial ventures, to the truly international, with thousands of developers collaborating, directly or indirectly, on a common platform. One characteristic that is shared by the largest and most successful open source projects, however, is a software architecture designed to promote anarchic collaboration through extensions while at the same time preserving centralized control over the interfaces. This talk features a survey of the state-of-the-practice in open source development in regards to software architecture, with particular emphasis on the modular extensibility interfaces within several of the most successful projects, including Apache httpd, Eclipse, Mozilla Firefox, Linux kernel, and the World Wide Web (which few people recognize as an open source project in itself). These projects fall under the general category of collaborative open source software development, which emphasizes community aspects of software engineering in order to compensate for the often-volunteer nature of core developers and take advantage of the scalability obtainable through Internet-based virtual organizations.},
	keywords = {apache, collaborative open source development, eclipse, extensibility, Firefox, linux, linux kernel, loose coupling, modularity, mozilla, open source, software architecture},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062474},
	url = {http://doi.acm.org/10.1145/1062455.1062474},
	author = {Roy T. Fielding}
}
@conference {899,
	title = {Stopping spyware at the gate: a user study of privacy, notice and spyware},
	booktitle = {2005 Symposium on Usable Privacy and Security},
	year = {2005},
	month = {07/2005},
	pages = {43-52},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Pittsburgh, PA},
	keywords = {agreement,, and, Aspects,, Design,, end, EULA,, Experimentation,, Factors,, Human, Legal, license, notice,, of, privacy,, security, service,, spyware,, terms, ToS,, usability,, user},
	isbn = {1-59593-178-3 },
	author = {N. Good and Dhamija, R. and J. Grossklags and D. Thaw and Aronowitz, S. and D. Mulligan and J. Konstan}
}
@conference {788,
	title = {Structure, Cohesion, and Open Source Software Success},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {317-319},
	abstract = {This paper proposes a dissertation designed to understand how the open source software (OSS) development group and its associated interest community jointly and independently impact OSS success for a single OSS project.},
	keywords = {interest community, network externalities, open source software, software quality},
	url = {http://pascal.case.unibz.it/handle/2038/1536},
	author = {Sherae Daniel}
}
@conference {782,
	title = {Towards Supporting Agile Practice Within The Libre Software Paradigm},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {303-304},
	abstract = {Individual agile methods have never been practiced as defined, in the same way that Royce{\textquoteright}s waterfall [1] model never reflected actual practice. Instead, practitioners adapted the core principles of these processes in order to suit their needs. Understanding this is key to appreciating the agile mindset. What does exist is a set of principles1 which, when followed loosely, form the agile practices. It is an important part of the agile mentality that the individuals within a project are more important that the process they follow. However, the individual methods do have their own identifying features that make them unique; for example testing must be performed before coding within eXtreme Programming (XP) [2]. However, if practitioners were to apply XP, exactly as Beck describes it, then they are probably not {\textquotedblleft}doing agile{\textquotedblright} as they may not be following the process that suits their needs best. One of the interesting features of the XP method is its requirement of a collocated team. Th...},
	keywords = {agile methods, agile practice, extreme programming, libre software, open source, XP},
	url = {http://pascal.case.unibz.it/handle/2038/1546},
	author = {Adams, Paul and Boldyreff, Cornelia}
}
@conference {797,
	title = {Transfering Libre Software Development Practices to the Production of Educational Resources: the Edukalibre Project},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-348},
	abstract = {The transfer of methodologies common in libre (free, open source) sofware development to the domain of educational resources can radically change the way educational content is developed and used, enabling both educational practitioners and students to become actively involved in its creation and distribution. New software architectures and tools are needed to effectively support this process. This paper describes a platform aimed to support the creation of free, collaboratively constructed educational content on the web, which has been developed within the Edukalibre project. It provides easy access to core technologies: a control version system combined with conversion tools to produce several convenient formats for each document. Its modular architecture offers many different interfaces to the users. The Edukalibre platform is distributed as libre software.},
	keywords = {educational resources, information systems, open source, software development practices},
	url = {http://pascal.case.unibz.it/handle/2038/1548},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Chris Tebb and Vania Dimitrova and Chaparro, Diego and Romera, Teo}
}
@conference {Neamtiu:2005:USC:1083142.1083143,
	title = {Understanding source code evolution using abstract syntax tree matching},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {2-6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Mining software repositories at the source code level can provide a greater understanding of how software evolves. We present a tool for quickly comparing the source code of different versions of a C program. The approach is based on partial abstract syntax tree matching, and can track simple changes to global variables, types and functions. These changes can characterize aspects of software evolution useful for answering higher level questions. In particular, we consider how they could be used to inform the design of a dynamic software updating system. We report results based on measurements of various versions of popular open source programs, including BIND, OpenSSH, Apache, Vsftpd and the Linux kernel.},
	keywords = {abstract syntax trees, apache, bind, evolution, linux, openssh, software evolution, source code, source code analysis, vsftpd},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083143},
	url = {http://doi.acm.org/10.1145/1082983.1083143},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2Understanding.pdf},
	author = {Neamtiu, Iulian and Foster, Jeffrey S. and Hicks, Michael}
}
@conference {783,
	title = {Unreliable Collaborators: Coordination in distributed volunteer teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {305-306},
	abstract = {Drawing together the interest, skills and resources of individuals to pursue productive activity is the cornerstone of wealth creation. Recently, new forms of productive activity have emerged that draw together highly motivated, often volunteer, participants to collaborate through low-cost information systems to produce high quality products that rival those produced by wealthy firms and markets. Examples include free (libr{\^A}{\textasciiacute}e) and open source software (FLOSS), such as Linux, and collaboratively edited texts, such as Wikipedia and the Open Directory. There is an opportunity to study these novel activities, to understand their organization, in order to both further their continued success and to assess whether and which of their novel organization techniques might be used in wider domains of human collaborative activity.},
	keywords = {coordination, floss organization, MOTIVATION, open source, volunteer teams},
	url = {http://pascal.case.unibz.it/handle/2038/1552},
	author = {Howison, James}
}
@conference {778,
	title = {Using Plone To Support Collaborative Research},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {296-297},
	keywords = {collaboration environment, collaborative research, content management system, open source, plugin},
	url = {http://pascal.case.unibz.it/handle/2038/1558},
	author = {Adams, Paul and Nutter, David and Rank, Stephen and Boldyreff, Cornelia}
}
@conference {799,
	title = {What is the significance of Open Source Software for the education and training community?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {353-358},
	abstract = {There is growing interest in the education community in the development and use of Open Source Software. This paper explains the ideas behind OSS and how what its significance is for education. It examines regional and national initiatives to promote the use of OSS. The paper considers the advantages of OSS and potential problems. It goes on to look at the idea of open content and the sharing of learning content, and provides short case studies. The paper concludes that the major significance of OSS and open content is in the new social relations engendered and in fostering innovation in e-learning, both in application development and new pedagogies.},
	keywords = {economic issues, education, open source, pedagocic impact, training},
	url = {http://pascal.case.unibz.it/handle/2038/1563},
	author = {Attwell, Graham}
}
@proceedings {1188,
	title = {Communication and Conflict Issues in Collaborative Software Research Projects},
	year = {2004},
	pages = {14-17},
	abstract = {The Open Source Component Artefact Repository (OSCAR) was developed under the auspices of the GENESIS project to store data produced during the software development process. Significant problems were encountered during the course of the project in both the development itself and management of the project. The reasons for and potential solutions to these problems are examined with the intention of developing a set of guidelines to enable participants in other collaborative projects to avoid these pitfalls.
We wish to make it clear that we attach no opprobrium to any of the participants in the GENESIS project as many of the issues we outline below have solutions only visible with hindsight. Instead, we seek to provide a fair-minded critique of our role and the mistakes we made in a fairly typical two-year EU research project, and to provide a set of recommendations for other similar projects, in order that they can (attempt to) avoid suffering similarly.},
	keywords = {artefact, cvs, genesis, oscar},
	attachments = {https://flosshub.org/sites/flosshub.org/files/boldyreff15-18.pdf},
	author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen}
}
@conference {77,
	title = {Do the Rich Get Richer? The Impact of Power Laws on Open Source Development Projects},
	booktitle = {2004 Open Source Conference (OSCON)},
	year = {2004},
	type = {conference presentation},
	address = {Portland, OR, USA},
	keywords = {open source, power law, social network analysis, sourceforge},
	author = {Conklin, Megan}
}
@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}
}
@article {DBLP:journals/electronicmarkets/Joode04,
	title = {Managing Conflicts in Open Source Communities},
	journal = {Electronic Markets},
	volume = {14},
	number = {2},
	year = {2004},
	pages = {104-113},
	abstract = {An increasing number of companies adopt open source software. These companies will typically pay programmers to participate in the design, development and maintenance of open source software. The programmers, however, are reported to have different interests compared to the voluntary programmers who dominate most open source communities. The diversity of interest will inevitably result in conflicts. To ensure that their interests are achieved, companies should understand how conflicts between their programmers and the voluntary programmers can be managed. The aim of this paper is to identify and discuss mechanisms that are currently present to manage conflicts in open source communities.

The mechanisms identified in this paper are based on an explorative literature study and on 48 semi-structured interviews with programmers from a variety of open source communities. Four mechanisms have been identified and their relevance in the management of conflicts are discussed. They are: third-party intervention; modularity; parallel software development lines; and the exit option. The paper ends with an example of Covalent, which deploys parallel software development lines to manage conflicts in the Apache community. },
	keywords = {abiword, apache, conflict, covalent, interviews, organizational sponsorship, Volunteers},
	author = {Ruben van Wendel de Joode}
}
@proceedings {124,
	title = {Membership dynamics and network stability in the open-source community: the ising perspective},
	year = {2004},
	note = {"simulations with the empirical network data that were collected from two actual OSS communities, Linux and Hypermail."

"we initially downloaded nearly 100,000 archived (between 1997 and 2003) LINUX Kernel and Hypermail newsgroup messages posted in a UNIX mailbox format"

"Specific information was obtained regarding the characteristics of these two OSS communities, including the size, the number of average connections per participant, and the hierarchy of each community."},
	abstract = {In this paper, we address the following two questions: (1)How does a participant{\textquoteright}s membership decision affect the others (neighbors) with whom he has collaborated over an extended period of time in an open source software (OSS) network? (2) To what extent do network characteristics (i.e, size and connectivity) mediate the impact of external factors on the OSS participants{\textquoteright} dynamic membership decisions and hence the stability of the network? From the Ising perspective, we present fresh theoretical insight into the dynamic and reciprocal membership relations between OSS participants. We also performed simulations based on empirical data that were collected from two actual OSS communities. Some of the key findings include that (1) membership herding is highly present when the external force is weak, but decreases significantly when the force increases, (2) the propensity for membership herding is most likely to be seen in a large network with a random connectivity, and (3) for large networks, at low external force a random connectivity will perform better than a scale-free counterpart in terms of the network strength. However, as the temperature (external force) increases, the reverse phenomenon is observed. In addition, the scale-free connectivity appears to be less volatile than with the random connectivity in response to the increase in the temperature. We conclude with several implications that may be of significance to OSS stakeholders.},
	keywords = {email, email archive, hypermail, linux, mailing list, membership, membership herding, newsgroup, open source, participants, social network analysis, stakeholders, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OhJeon.pdf},
	author = {Oh, Wonseok and Jeon, Sangyong}
}
@article {Chen:2004:OCL:990374.990391,
	title = {Open-Source Change Logs},
	journal = {Empirical Softw. Engg.},
	volume = {9},
	year = {2004},
	note = {"We decided to compare actual differences in the source code with entries in the ChangeLog file. We used lxr, the Linux cross-referencing tool..., to determine the precise differences between two successive software versions. We then compared these differences with the records in the ChangeLog file to check the completeness of the ChangeLog file."
},
	month = {September},
	pages = {197{\textendash}210},
	publisher = {Kluwer Academic Publishers},
	address = {Hingham, MA, USA},
	abstract = {A recent editorial in Empirical Software Engineering suggested that open-source software projects offer a great deal of data that can be used for experimentation. These data not only include source code, but also artifacts such as defect reports and update logs. A common type of update log that experimenters may wish to investigate is the ChangeLog, which lists changes and the reasons for which they were made. ChangeLog files are created to support the development of software rather than for the needs of researchers, so questions need to be asked about the limitations of using them to support research. This paper presents evidence that the ChangeLog files provided at three open-source web sites were incomplete. We examined at least three ChangeLog files for each of three different open-source software products, namely, GNUJSP, GCC-g++, and Jikes. We developed a method for counting changes that ensures that, as far as possible, each individual ChangeLog entry is treated as a single change. For each ChangeLog file, we compared the actual changes in the source code to the entries in the ChangeLog file and discovered significant omissions. For example, using our change-counting method, only 35 of the 93 changes in version 1.11 of Jikes appear in the ChangeLog file{\textemdash}that is, over 62\% of the changes were not recorded there. The percentage of omissions we found ranged from 3.7 to 78.6\%. These are significant omissions that should be taken into account when using ChangeLog files for research. Before using ChangeLog files as a basis for research into the development and maintenance of open-source software, experimenters should carefully check for omissions and inaccuracies.},
	keywords = {change log, gcc, GCC-g, GNUJSP, Jikes, log files, Open-source software, source code},
	issn = {1382-3256},
	doi = {10.1023/B:EMSE.0000027779.70556.d0},
	url = {http://portal.acm.org/citation.cfm?id=990374.990391},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chen.pdf},
	author = {Chen, Kai and Schach, Stephen R. and Yu, Liguo and Offutt, Jeff and Heller, Gillian Z.}
}
@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}
}
@proceedings {95,
	title = {Open source software in the trenches: Lessons from a large-scale OSS implementation},
	year = {2003},
	keywords = {open source},
	author = {Fitzgerald, Brian and Kenny, Tony}
}
@proceedings {74,
	title = {Survival of open-source projects: A population ecology perspective},
	year = {2003},
	keywords = {open source},
	author = {Chengalur-Smith, Shobha and Sidorova, Anna}
}
@article {Stamelos02codequality,
	title = {Code quality analysis in open source software development},
	journal = {Information Systems Journal},
	volume = {12},
	year = {2002},
	note = {"For our case study, we have used Logiscope{\quotesinglbase} (Telelogic, 2000), a comprehensive set of tools able to perform, automatically, code measurement and comparison with user-defined programming standards"
"Using Logiscope, we examined a sample of 100 C programs found in the SUSE Linux 6.0 release."
metrics collected:
number of statements
cyclomatic complexity
maximum levels
number of paths
unconditional jumps
comment frequency
vocabulary frequency
program length
average size
number of inputs/outputs},
	pages = {43{\textendash}60},
	abstract = {Proponents of open source style software development claim that better software is produced using this model compared with the traditional closed model. However, there is little empirical evidence in support of these claims. In this paper, we present the results of a pilot case study aiming: (a) to understand the implications of structural quality; and (b) to figure out the benefits of structural quality analysis of the code delivered by open source style development. To this end, we have measured quality characteristics of 100 applications written for Linux, using a software measurement tool, and compared the results with the industrial standard that is proposed by the tool. Another target of this case study was to investigate the issue of modularity in open source as this characteristic is being considered crucial by the proponents of open source for this type of software development. We have empirically assessed the relationship between the size of the application components and the delivered quality measured through user satisfaction. We have determined that, up to a certain extent, the average component size of an application is negatively related to the user satisfaction for this application.},
	keywords = {C, Code quality characteristics, functions, linux, metrics, open source development, software measurement, structural code analysis, Suse, user satisfaction},
	author = {Ioannis Stamelos and Lefteris Angelis and Apostolos Oikonomou and Georgios L. Bleris}
}
@conference {1161,
	title = {The Coming Software Revolution},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The growing adoption of collaborative software development will change the global software industry by altering its economics of scale, location, and price. The growth of non-proprietary code will depress prices in the proprietary sector, and the possession of source code will enable the growth of more software industrial centers around the world; their emergence will threaten the business of current leaders. National governments which see themselves as disadvantaged or even threatened by the current software powers will encourage collaborative software development and the services that this development model drives. Only world-wide draconic legislation by the current software powers has any hope of preserving the status quo.},
	keywords = {ECONOMICS, management, open source, politics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Rosenberg.pdf},
	author = {Rosenberg, D.K.}
}
@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}
}
@conference {1156,
	title = {The evolution of the GNOME Project},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The GNOME Project is an attempt to create a GUI desktop for Unix systems. Originally started by a handful of volunteers in 1996, GNOME has become the desktop of choice for Solaris, HP-UX, and Red Hat Linux, and it is currently developed by a team of approximately five hundred people around the world. The importance of GNOME to the Unix world has attracted the attention of several software companies who are actively participating in its development. At the same time, some of its volunteer developers have created enterprises who expect to sell services and products around GNOME. This extended abstract describes, first, the development model of GNOME, then the influence that private companies had had on the project: on one hand they are contributing a large amount of resources to the project, accelerating its development, and increasing its reliability and documentation; and on the other hand, the GNOME Foundation has been created to maintain the goal of the project to provide a free (as in freedom) software desktop for Unix, and avoid that the commercial interests of these partners could jeopardize the interests of the community.},
	keywords = {commercial software, gnome, organizational sponsorship},
	attachments = {https://flosshub.org/sites/flosshub.org/files/German.pdf},
	author = {Daniel M. German}
}
@conference {Nakakoji:2002:EPO:512035.512055,
	title = {Evolution patterns of open-source software systems and communities},
	booktitle = {Proceedings of the International Workshop on Principles of Software Evolution},
	series = {IWPSE {\textquoteright}02},
	year = {2002},
	pages = {76{\textendash}85},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-Source Software (OSS) development is regarded as a successful model of encouraging "natural product evolution". To understand how this "natural product evolution" happens, we have conducted a case study of four typical OSS projects. Unlike most previous studies on software evolution that focus on the evolution of the system per se, our study takes a broader perspective: It examines not only the evolution of OSS systems, but also the evolution of the associated OSS communities, as well as the relationship between the two types of evolution.Through the case study, we have found that while collaborative development within a community is the essential characteristic of OSS, different collaboration models exist, and that the difference in collaboration model results in different evolution patterns of OSS systems and communities. To treat such differences systematically, we propose to classify OSS into three types: Exploration-Oriented, Utility-Oriented, and Service-Oriented. Such a classification can provide guidance on the creation and maintenance of sustainable OSS development and communities.},
	keywords = {case study, open-source software (OSS), open-source software community, software evolution},
	isbn = {1-58113-545-9},
	doi = {10.1145/512035.512055},
	url = {http://doi.acm.org/10.1145/512035.512055},
	author = {Nakakoji, Kumiyo and Yamamoto, Yasuhiro and Nishinaka, Yoshiyuki and Kishida, Kouichi and Ye, Yunwen}
}
@conference {stewart2002an-explorat,
	title = {An Exploratory Study of Factors Influencing the Level of Vitality and Popularity of Open Source Projects},
	booktitle = {ICIS 2002. Proceedings of International Conference on Information Systems 2002},
	year = {2002},
	note = {"We are currently tracking publicly available data on 240 open source projects registered on the freshmeat Website." "First, we randomly selected a total of 120 projects from the utilities, software development, and games and entertainment areas. We then selected 120 projects from these forums that had been registered on the site during the two weeks prior to the start of our data collection effort."},
	month = {2002},
	pages = {1-5},
	abstract = {In this research, we ask the question: What differentiates successful from unsuccessful open source software projects? Using a sample of 240 open source projects, we examine how organizational sponsorship, target audience (developer versus end user), license choice, and development status interact over time to influence the extent to which open source software projects attract user attention and developer activity.},
	keywords = {activity, audience, developers, freshmeat, license analysis, licenses, organizational sponsorship, project success, roles, status, target audience, users},
	author = {Stewart, Katherine J. and Ammeter, Tony}
}
@conference {1152,
	title = {Open-Source Artefact Management},
	booktitle = {2nd Workshop on Open Source Software Engineering at ICSE 2002},
	year = {2002},
	abstract = {This paper presents the GENESIS project, which aims to develop an open-source, lightweight, process-aware (and process-neutral) workflow management system. In particular OSCAR, the artefact repository is discussed. The requirements of a system for artefact management and storage are described, and the concept of active artefacts is explained. The software engineering methods which will be used in the project are described, and some examples of the open-source tools which may be used are described.},
	keywords = {artefacts, artifacts, genesis, oscar, workflow},
	attachments = {https://flosshub.org/sites/flosshub.org/files/BoldyreffNutterRank.pdf},
	author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen}
}
@article {Hissam,
	title = {Trust and vulnerability in open source software},
	journal = {Software, {IEE} Proceedings -},
	volume = {149},
	number = {1},
	year = {2002},
	month = {02/2002},
	pages = {47{\textendash}51},
	chapter = {47},
	abstract = {Software plays an ever increasing role in the critical infrastructures that run our cities, manage our economies, and defend our nations. In 1999, the Presidents Information Technology Advisory Committee (PITAC) reported to the United States President the need for software components that are reliable, tested, modelled and secure supporting the development of predictably reliable and secure systems that underscore our critical infrastructures. Open source software (OSS) constitutes a viable source for software components. Some believe that OSS is more reliable and more secure than closed source software (CSS)-due to a phenomenon dubbed {\textquoteright}many eyeballs{\textquoteright}-but is this truly the case? Or does OSS give the cyber criminal an edge that he would likewise not have? We explore OSS from the perspective of the cyber criminal and discuss what the community of software developers and users alike can do to increase their trust in both open source software and closed source software},
	keywords = {closed source software, community of software developers, critical infrastructures, cyber criminal, open source software, PITAC, predictably reliable systems, predictably secure systems, software components, trust, users, vulnerability},
	issn = {1462-5970},
	doi = {10.1049/ip-sen:20020208},
	author = {Hissam, S. A. and Plakosh, D. and Weinstock, C.}
}
@article {121,
	title = {Two case studies of open source software development: Apache and Mozilla},
	journal = {ACM Transactions on Software Engineering and Methodology},
	volume = {11},
	number = {3},
	year = {2002},
	note = {apache data sources:
email, cvs, bug database 
regarding email: "We wrote Perl scripts to extract date, sender identity, message subject, and the message body that was further processed to obtain details on code changes and problem reports (see below). Manual inspection was used to resolve such things as multiple email addresses in cases where all automated techniques failed."
(but the rest of the paper does not address this data source at all)

mozilla data sources
bugzilla, cvs

},
	pages = {309-346},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high- performance commercial/ open source process hybrids.},
	keywords = {apache, bug fixing, bug reports, bugzilla, change history, core, defect density, email, email archives, mailing list, mozilla, ownership, participation, productivity, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusFieldingHerbsleb2002.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, J. D.}
}
@conference {1141,
	title = {Corporate Source: Applying Open Source Concepts to a Corporate Environment},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {commercial software, hewlett packard, hp, organizational sponsorship},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dinkelackergarg.pdf},
	author = {Dinkelacker, J. and Garg, P.K.}
}
@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.}
}
@conference {Godfrey:2001:GES:602461.602482,
	title = {Growth, evolution, and structural change in open source software},
	booktitle = {Proceedings of the 4th International Workshop on Principles of Software Evolution (IWPSE 2001)},
	series = {IWPSE {\textquoteright}01},
	year = {2001},
	note = {"We measured [linux] system size in uncommented LOC"
"We also examined the growth of several other open source systems, including the VIM text editor, Eric Raymond{\textquoteright}s fetchmail utility, and the GCC compiler suite. "},
	pages = {103{\textendash}106},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our recent work has addressed how and why software systems evolve over time, with a particular emphasis on software architecture and open source software systems [2, 3, 6]. In this position paper, we present a short summary of two recent projects. First, we have performed a case study on the evolution of the Linux kernel [3], as well as some other open source software (OSS) systems. We have found that several OSS systems appear not to obey some of "Lehman{\textquoteright}s laws" of software evolution [5, 7], and that Linux in particular is continuing to grow at a geometric rate. Currently, we are working on a detailed study of the evolution of one of the subsystems of the Linux kernel: the SCSI drivers subsystem. We have found that cloning, which is usually considered to be an indicator of lazy development and poor process, is quite common and is even considered to be a useful practice. Second, we are developing a tool called Beagle to aid software maintainers in understanding how large systems have changed over time. Beagle integrates data from various static analysis and metrics tools and provides a query engine as well as navigable visualizations. Of particular note, Beagle aims to provide help in modelling long term evolution of systems that have undergone architectural and structural change.},
	keywords = {agile methods, beagle, cloning, evolution, fetchmail, gcc, growth, kernel, lehman{\textquoteright}s laws, lines of code, linux, linux kernel, loc, open source software, software architecture, software evolution, source code, structural change, supporting environments, vim},
	isbn = {1-58113-508-4},
	doi = {http://doi.acm.org/10.1145/602461.602482},
	url = {http://doi.acm.org/10.1145/602461.602482},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tu2001.pdf},
	author = {Michael Godfrey and Tu, Qiang}
}
@conference {1151,
	title = {Open Source Development: A suitable Method to introduce a standardized communication protocol?},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open Source developments like telnet and Apache are very important for an extensive and compatible use of the TCP/IP and the HTTP protocol. Both contain features which rely on a compatible implementation of complex interactions between computers of different platform types. This can be successfully achieved with the help of Open Source.	Reconciliation	of	different interpretations of the standard, clarifications and extensions can be realised by discussion systems	and	some	generally	accepted conciliators of Open Source projects. As long as companies have a commercial interest in selling solutions based on the protocol, it makes economic sense for them to jointly support its common implementation. This paper examines the possibility to use an Open Source reference implementation of the agricultural communication protocols DIN 9684 [1] [2] and ISO 11783 to establish a capable and compatible implementation in agricultural mobile process control and data collection.},
	keywords = {communication protocol, DIN 9684, ISO 11783, open source},
	attachments = {https://flosshub.org/sites/flosshub.org/files/spangler.pdf},
	author = {Spangler, Achim}
}
@conference {1143,
	title = {Open Source Software: The Other Commercial Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open source software is a source of components from which systems can be built. Components can also be acquired in the marketplace. There are a myriad of issues that affect software that incorporates commercial components. These issues (and others) also affect open source software. In this paper we examine issues that an organization using open source software is likely to face in light of lessons learned from the world of commercial components},
	keywords = {commercial off-the-shelf software, commercial software, COTS software, open source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hissamweinstock.pdf},
	author = {Hissam, S. and Weinstock, C.}
}
@conference {1142,
	title = {Software Engineering Research in the Bazaar},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	note = {"To gain a better understanding of a software system, we recover its software architecture from the system{\textquoteright}s source code.
We recovered the architecture of many open source systems such as the Linux kernel [3], the Mozilla browser [5], the Apache web server [7], and the VIM editor [14]. The recovered architecture is browse-able to permit developers to interact with it, [10] shows an example for the Linux kernel."},
	abstract = {During the last five years, our research group has studied the architecture and evolution of several large open source systems {\textemdash} including Linux, GCC, VIM, Mozilla, and Apache {\textemdash} and we have found that open source software systems often exhibit interesting differences when compared to similar commercially-developed systems. Our investigations of these systems have involved the creation of software architecture models, software architecture repair, the creation of a reference architecture for web servers, the study of evolution and growth of open source systems, and the modelling of architectural properties of systems that are apparent only at build time.},
	keywords = {apache, architecture, gcc, kernel, linux, linux kernel, mozilla, open source software, software architecture, Software Engineering Research, source code, vim},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hassangodfreyholt.pdf},
	author = {Hassan, Ahmed E. and Godfrey, Michael W. and Holt, Richard C.}
}
@conference {Yamauchi:2000:CLM:358916.359004,
	title = {Collaboration with Lean Media: how open-source software succeeds},
	booktitle = {Proceedings of the 2000 ACM conference on Computer supported cooperative work (CSCW)},
	series = {CSCW {\textquoteright}00},
	year = {2000},
	pages = {329{\textendash}338},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source software, usually created by volunteer programmers dispersed worldwide, now competes with that developed by software firms. This achievement is particularly impressive as open-source programmers rarely meet. They rely heavily on electronic media, which preclude the benefits of face-to-face contact that programmers enjoy within firms. In this paper, we describe findings that address this paradox based on observation, interviews and quantitative analyses of two open-source projects. The findings suggest that spontaneous work coordinated afterward is effective, rational organizational culture helps achieve agreement among members and communications media moderately support spontaneous work. These findings can imply a new model of dispersed collaboration.},
	keywords = {cooperative work, cvs, distributed work, electronic media, INNOVATION, open-source, software engineering},
	isbn = {1-58113-222-0},
	doi = {10.1145/358916.359004},
	url = {http://doi.acm.org/10.1145/358916.359004},
	author = {Yamauchi, Yutaka and Yokozawa, Makoto and Shinohara, Takeshi and Ishida, Toru}
}
