@inbook {Hirao2016,
	title = {The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {97{\textendash}110},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer{\textquoteright}s final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others{\textquoteright} decisions.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_8},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_8},
	author = {Hirao, Toshiki and Ihara, Akinori and Ueda, Yuki and Phannachitta, Passakorn and Matsumoto, Ken-ichi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {Kazuhiro Yamashita2016,
	title = {Magnet or Sticky? Measuring Project Characteristics from the Perspective of Developer Attraction and Retention},
	journal = {Journal of Information Processing},
	volume = {24},
	number = {2},
	year = {2016},
	pages = {339-348},
	abstract = {Open Source Software (OSS) is vital to both end users and enterprises. As OSS systems are becoming a type of infrastructure, long-term OSS projects are desired. For the survival of OSS projects, the projects need to not only retain existing developers, but also attract new developers to grow. To better understand how projects retain and attract contributors, our preliminary study aimed to measure the personnel attraction and retention of OSS projects using a pair of population migration metrics, called Magnet (personnel attraction) and Sticky (retention) metrics. Because the preliminary study analyzed only 90 projects and the 90 projects are not representative of GitHub, this paper extend the preliminary study to better understand the generalizability of the results by analyzing 16, 552 projects of GitHub. Furthermore, we also add a pilot study to investigate the typical duration between releases to find more appropriate release duration. The study results show that (1) approximately 23\% of developers remain in the same projects that the developers contribute to, (2) the larger projects are likely to attract and retain more developers, (3) 53\% of terminal projects eventually decay to a state of fewer than ten developers and (4) 55\% of attractive projects remain in an attractive category.
},
	keywords = {github, retention},
	doi = {10.2197/ipsjjip.24.339},
	url = {https://www.jstage.jst.go.jp/article/ipsjjip/24/2/24_339/_article},
	author = {Yamashita, Kazuhiro and Kamei, Yasutaka and McIntosh, Shane and Hassan, Ahmed E. and Ubayashi, Naoyasu}
}
@article {1802,
	title = {Candoia: A Platform and an Ecosystem for Building and Deploying Versatile Mining Software Repositories Tools},
	year = {2015},
	note = {" In terms of its focus,
the Candoia platform is closer to Bevan et al.{\textquoteright}s Kenyon [9],
Bajracharya et al.{\textquoteright}s Sourcerer [6], Gousios and Spinellis{\textquoteright}s Alitheia
Core [32, 31], Howison et al.{\textquoteright}s FLOSSMole [39] and different from
Boetticher et al.{\textquoteright}s PROMISE Repository [69], Gonz{\'a}lez-Barahona
and Robles{\textquoteright}s open-access data repositories [29], Black Duck OpenHub
(aka Ohloh) [13], GHTorrent [30, 33], Ossher et al.{\textquoteright}s SourcererDB
[64], the SourceForge Research Data Archive (SRDA) [28],
and Boa [25]. },
	month = {11/2015},
	institution = {Iowa State University},
	abstract = {Research on mining software repositories (MSR) has shown great
promise during the last decade in solving many challenging software
engineering problems. There exists, however, a {\textquoteleft}valley of death{\textquoteright}
between these significant innovations in the MSR research and their
deployment in practice. The significant cost of converting a prototype
to software; need to provide support for a wide variety of tools
and technologies e.g. CVS, SVN, Git, Bugzilla, Jira, Issues, etc,
to improve applicability; and the high cost of customizing tools to
practitioner-specific settings are some key hurdles in transition to
practice. We describe Candoia, a platform and an ecosystem that
is aimed at bridging this valley of death between innovations in
MSR research and their deployment in practice. We have implemented
Candoia and provide facilities to build and publish MSR
ideas as Candoia apps. Our evaluation demonstrates that Candoia
drastically reduces the cost of converting an idea to an app, thus
reducing the barrier to transitioning research findings into practice.
We also see versatility, in Candoia app{\textquoteright}s ability to work with a variety
of tools and technologies that the platform supports. Finally,
we find that customizing Candoia app to fit project-specific needs
is often well within the grasp of developers.},
	keywords = {Analysis of software and its evolution, Application specific development environments, flossmole cited, msr, research to practice, software evolution, software repositories},
	url = {http://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1378\&context=cs_techreports},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Candoia-\%20A\%20Platform\%20and\%20an\%20Ecosystem\%20for\%20Building\%20and\%20Deploying\%20V.pdf},
	author = {Nitin M. Tiwari and Dalton D. Mills and Ganesha Upadhyaya and Eric Lin and Rajan, Hridesh}
}
@proceedings {1785,
	title = {An Investigation of Migrating from Proprietary RTOS to Embedded Linux},
	year = {2015},
	month = {08/2015},
	abstract = {Embedded systems and the open source operating system
Linux have been going hand in hand for a long time now.
Companies using Linux for their embedded products are
praising it for being time and cost efficient when it comes to
performance and maintainability. Another solution for embedded
systems is a Real-Time Operating System (RTOS).
The goal of this this paper is to investigate whether a traditional
proprietary RTOS can be substituted with embedded
Linux, and if this kind of migration can lead to reduced licensing
costs and increased general quality of the system.
We used a qualitative research method for this case-study.
The investigation was conducted with interviews as the main
source of information. The result of this study is an empirical
model we named {\textquoteright}Embedded Linux Adoption Model{\textquoteright}.
We concluded that in many cases a proprietary RTOS can
be substituted with embedded Linux without affecting the
critical needs of the system. The study also showed that
many embedded system developers are very receptive to
open source solutions and could think of contributing to the
community.},
	url = {http://www.opensym.org/os2015/proceedings-files/p101-muchow.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p101-muchow.pdf},
	author = {Oscar Muchow and David Ustarbowski and Hammouda, Imed}
}
@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}
}
@conference {1359,
	title = {Linking e-mails and source code artifacts},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE {\textquoteright}10},
	volume = {1},
	year = {2010},
	note = {"we devised a set of lightweight methods, based on regular expressions, to establish the link between e-mails and software artifacts. We evaluated them in terms of precision and recall considering one single Java system. In this paper we overcome a number of limitations of our previous work, resulting in the following contributions:
{\textbullet} An extensive and publicly available1 benchmark and toolset for recovering traceability links between e-mails and source code artifacts. We created our benchmark by analyzing the mailing lists of six different software systems written in four different programming languages. For each system we manually annotated a statistically significant number of e-mails.
{\textbullet} A comprehensive evaluation of linking techniques. We evaluated and compared, in terms of precision and recall, different linking methods, ranging from lightweight grep-style approaches to more complex approa- ches from the information retrieval (IR) field."},
	month = {05/2010},
	pages = {375-384},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Cape Town, South Africa},
	abstract = {E-mails concerning the development issues of a system constitute an important source of information about high-level design decisions, low-level implementation concerns, and the social structure of developers.

Establishing links between e-mails and the software artifacts they discuss is a non-trivial problem, due to the inherently informal nature of human communication. Different approaches can be brought into play to tackle this traceability issue, but the question of how they can be evaluated remains unaddressed, as there is no recognized benchmark against which they can be compared.

In this article we present such a benchmark, which we created through the manual inspection of a statistically significant number of e-mails pertaining to six unrelated software systems. We then use our benchmark to measure the effectiveness of a number of approaches, ranging from lightweight approaches based on regular expressions to full-fledged information retrieval approaches.},
	isbn = {9781605587196},
	doi = {10.1145/1806799.1806855},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	author = {Bacchelli, Alberto and Lanza, Michele and Robbes, Romain}
}
@conference {548,
	title = {Archetypal Internet-Scale Source Code Searching},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {257 - 263},
	publisher = {Springer},
	organization = {Springer},
	chapter = {21},
	abstract = {Programmers often search for Open Source code to use in their projects. To understand how and why programmers search for source code, we onducted a web-based survey and collected data from 69 respondents, including 58 specific examples of searches. Analyzing these anecdotes, we found that they could be categorized along two orthogonal dimensions: motivation (reuse vs. reference example) and size of search target. The targets of these searches could range in size from a block (a few lines of code) to a subsystem (e.g. library or API), to an entire system. Within these six combinations of motivations and target sizes, nine repeating motifs, or archetypes, were created to characterize Internet-scale source code searching. Tools used for searching and the criteria for selecting a component are also discussed. We conclude with guidance on how these archetypes can inform better evaluation of Internet-scale code search engines, as well as the design of new features for these tools.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Archetypal\%20Internet-Scale\%20Source.pdf},
	author = {Umarji, Medha and Sim, Susan and Lopes, Crista}
}
