%0 Conference Proceedings %B Open Source Systems: Towards Robust Practices 13th International Conference on Open Source Systems %D 2017 %T Understanding When to Adopt a Library: A Case Study on ASF Projects %A Ihara, Akinori %A Daiki Fujibayashi %A Hirohiko Suwa %A Raula Gaikovina Kula %A Kenichi Matsumoto %K adoption %K apache %K apache software foundation %K libraries %X 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. %B Open Source Systems: Towards Robust Practices 13th International Conference on Open Source Systems %S IFIP Advances in Information and Communication Technology %I Springer %V 496 %P 128-138 %8 05/2017 %U https://link.springer.com/chapter/10.1007/978-3-319-57735-7_13 %R 10.1007/978-3-319-57735-7_13 %0 Conference Paper %B Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering %D 2015 %T Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study %A Hata, Hideaki %A Todo, Taiki %A Onoue, Saya %A Kenichi Matsumoto %X 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. %B Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering %S CHASE '15 %I IEEE Press %C Piscataway, NJ, USA %P 15–21 %U http://dl.acm.org/citation.cfm?id=2819321.2819325 %1 http://www.slideshare.net/hideakihata5/characteristics-of-sustainable-oss-projects-a-theoretical-and-empirical-study %0 Conference Proceedings %B 12th Working Conference on Mining Software Repositories (MSR 2015) %D 2015 %T A Dataset of High Impact Bugs: Manually-Classified Issue Reports %A Ohira, Masao %A Yutaro Kashiwa %A Yosuke Yamatani %A Hayato Yoshiyuki %A Yoshiya Maeda %A Nachai Limsettho %A Keisuke Fujino %A Hata, Hideaki %A Ihara, Akinori %A Kenichi Matsumoto %K ambari %K camel %K derby %K wicket %X 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). %B 12th Working Conference on Mining Software Repositories (MSR 2015) %I IEEE %8 05/2015 %U http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141 %> https://flosshub.org/sites/flosshub.org/files/5594a518.pdf