{'fraction_non_alphanumeric': 0.013095238095238096, 'fraction_numerical': 0.0, 'mean_word_length': 4.922535211267606, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Issue ownership activity in two large software projects

Issue management is one of the major challenges of software development teams. Balanced workload allocation of developers who are responsible for the maintenance of the software product would impact the long-term reliability of the product. In this paper, we analyse the issue report, issue ownership, and issue resolve patterns of two large software products over a period of time. We use GINI index to estimate the inequalities in issue ownership over time. Our results indicate that a small group of developers tends to take the ownership of a large portion of new issues especially when the active issue count is relatively high in the software development life cycle. We discuss the implications of this trend and propose long-term issue management strategies to deal with them.