Got Issues? Who Cares About It? A Large Scale Investigation of Issue Trackers from GitHub

Authore(s) : Tegawend´e F. || University of LuxembourgLuxembourg 2Singapore Management UniversitySingapore 3LaBRIUniversity of BordeauxFrance.

Volume : (3), Issue : 211, February - 2018

Abstract : Abstract—Feedback from software users constitutes a vital part in the evolution of software projects. By filing issue reports, users help identify and fix bugs, document software code, and enhance the software via feature requests. Many studies have explored issue reports, proposed approaches to enable the submission of higher-quality reports, and presented techniques to sort, categorize and leverage issues for software engineering needs. Who, however, cares about filing issues? What kind of issues are reported in issue trackers? What kind of correlation exist between issue reporting and the success of software projects? In this study, we address the need for answering such questions by performing an empirical study on a hundred thousands of open source projects. After filtering relevant trackers, the study used about 20,000 projects. We investigate and answer various research questions on the popularity and impact of issue trackers.

Article: Download PDF Journal DOI : 2364/2018

Cite This Article:

Article No : 10017

Number of Downloads : 101

References :

 G. Antoniol, K. Ayari, M. D. Penta, F. Khomh, and Y.-G. Gu´eh´eneuc, “Is it a bug or an enhancement?: a text-based approach to classify change requests,” in CASCON, 2008.  J. Anvik, L. Hiew, and G. C. Murphy, “Who should fix this bug?” in ICSE, 2006, pp. 361–370. R. P. Bagozzi and U. M. Dholakia, “Open source software user communities: A study of participation in linux user groups,” Manage. Sci., vol. 52, no. 7, pp.... More

1.  G. Antoniol, K. Ayari, M. D. Penta, F. Khomh, and Y.-G. Gu´eh´eneuc, “Is it a bug or an enhancement?: a text-based approach to classify change requests,” in CASCON, 2008.
2.  J. Anvik, L. Hiew, and G. C. Murphy, “Who should fix this bug?” in ICSE, 2006, pp. 361–370.
3. R. P. Bagozzi and U. M. Dholakia, “Open source software user communities: A study of participation in linux user groups,” Manage. Sci., vol. 52, no. 7, pp. 1099–1115, Jul. 2006.
4.  N. Bettenburg, S. Just, A. Schr¨oter, C. Weiss, R. Premraj, and T. Zimmermann, “What makes a good bug report?” in FSE, 2008, pp. 308–318.
5.  C. Bird, A. Bachmann, F. Rahman, and A. Bernstein, “Linkster: enabling efficient manual inspection and annotation of mined data,” in FSE, 2010.
6.  T. F. Bissyand´e, F. Thung, D. Lo, L. Jiang, and L. R´eveill`ere, “Popularity, Interoperability, and Impact of Programming Languages in 100,000 Open Source Projects,” in COMPSAC, Kyoto, Japan, 2013, [To appear].
7. G. Canfora and L. Cerulo, “Supporting change request assignment in open source development,” in SAC, 2006, pp. 1767–1772.
8. R. T. Fielding, “Architectural styles and the design of network-based software architectures,” Ph.D. dissertation, University of California, Irvine, 2000.
9. L. Grammel, H. Schackmann, A. Schr¨oter, C. Treude, and M.-A. Storey, “Attracting the community’s many eyes: an exploration of user involvement in issue tracking,” in HAoSe, 2010, pp. 3:1–3:6.
10. D. G. Hendry, “Public participation in proprietary software development through user roles and discourse,” Int. J. Hum.-Comput. Stud., vol. 66, no. 7, pp. 545–557, Jul. 2008.
11. P. Hooimeijer and W. Weimer, “Modeling bug report quality,” in ASE, 2007, pp. 34–43.
12. W. G. Hopkins, A New View of Statistics. Sport Science, 2004.
13. H. Hosseini, R. Nguyen, and M. W. Godfrey, “A market-based bug allocation mechanism using predictive bug lifetimes,” in CSMR, 2012, pp. 149–158.
14. N. Iivari, “Empowering the users? a critical textual analysis of the role of users in open source software development,” AI Soc., vol. 23, no. 4, pp. 511–528, Oct. 2008.
15. A. J. Ko and P. K. Chilana, “How power users help and hinder open bug reporting,” in CHI, 2010, pp. 1665–1674.
16. T. Koponen and H. Lintula, “Are the Changes Induced by the Defect Reports in the Open Source Software Maintenance?” in SERP, 2006, pp. 429–435.
17. V. Levenshtein, “Binary Codes Capable of Correcting Deletions, Insertions and Reversals,” Soviet Physics Doklady, vol. 10, p. 707, 1966.
18. H. B. Mann and D. R. Whitney, “On a test of whether one of two random variables is stochastically larger than the other,” The Annals of Mathematical Statistics, vol. 18, no. 1, pp. 50–60, 1947.
19. N. Nagappan and T. Ball, “Using software dependencies and churn metrics to predict field failures: An empirical case study,” in ESEM, 2007, pp. 364–373.
20. K. Pavneet Singh, T. F. Bissyand´e, D. Lo, and L. Jiang, “Adoption of Software Testing in Open Source Projects - A Preliminary Study on 50,000 Projects,” in CSMR, Genoa, Italy, 2013.
21. D. Posnett, A. Hindle, and P. T. Devanbu, “Got issues? do new features and code improvements affect defects?” in WCRE, 2011, pp. 211–215.
22. V. Singh, M. Twidale, and D. Nichols, “Users of open source software - how do they get help?” in HICSS, jan. 2009, pp. 1 –10.
23. J. Spolsky, Joel on Software. APress, 2004.
24. C. Sun, D. Lo, S.-C. Khoo, and J. Jiang, “Towards more accurate retrieval of duplicate bug reports,” in ASE, 2011, pp. 253–262.
25. C. Sun, D. Lo, X. Wang, J. Jiang, and S.-C. Khoo, “A discriminative model approach for accurate duplicate bug report retrieval,” in ICSE (1), 2010.
26. Y. Tian, C. Sun, and D. Lo, “Improved duplicate bug report identification,” in CSMR, 2012, pp. 385–390.
27. D. W. van Liere, “How shallow is a bug? why open source communities shorten the repair time of software defects.” in ICIS, 2009, p. 195.
28. C. Weiss, R. Premraj, T. Zimmermann, and A. Zeller, “How long will it take to fix this bug?” in MSR, 2007.
29. D. A. Wheeler, “SLOCCount: Counting physical Source Lines of Code,” http://www.dwheeler.com/sloccount/.
30. R. Wu, H. Zhang, S. Kim, and S.-C. Cheung, “Relink: recovering links between bugs and changes,” in FSE, 2011.

... Less