@proceedings {1900,
	title = {Understanding When to Adopt a Library: A Case Study on ASF Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {128-138},
	publisher = {Springer},
	abstract = {Software libraries are widely used by both industrial and open source client projects. Ideally, a client user of a library should adopt the latest version that the library project releases. However, sometimes the latest version is not better than a previous version. This is because the latest version may include additional developer effort to test and integrate all changed features. In this study, our main goal is to better understand the relationship between adoption of library versions and its release cycle. Specifically, we conducted an empirical study of release cycles for 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. Moreover, results suggest that software projects are more likely to adopt the latest version of a rapid-release library compared to libraries with a longer release cycles.},
	keywords = {adoption, apache, apache software foundation, libraries},
	doi = {10.1007/978-3-319-57735-7_13},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_13},
	author = {Ihara, Akinori and Daiki Fujibayashi and Hirohiko Suwa and Raula Gaikovina Kula and Kenichi Matsumoto}
}
@conference {Hata:2015:CSO:2819321.2819325,
	title = {Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study},
	booktitle = {Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering},
	series = {CHASE {\textquoteright}15},
	year = {2015},
	note = {Slideshare: http://www.slideshare.net/hideakihata5/characteristics-of-sustainable-oss-projects-a-theoretical-and-empirical-study},
	pages = {15{\textendash}21},
	publisher = {IEEE Press},
	organization = {IEEE Press},
	address = {Piscataway, NJ, USA},
	abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in GitHub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.},
	url = {http://dl.acm.org/citation.cfm?id=2819321.2819325},
	author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Kenichi Matsumoto}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
