{'fraction_non_alphanumeric': 0.018327605956471937, 'fraction_numerical': 0.009163802978235968, 'mean_word_length': 5.723076923076923, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Stress and Burnout in Open Source: Toward Finding, Understanding, and Mitigating Unhealthy Interactions

Developers from open-source communities have reported high stress levels from frequent demands for features and bug fixes and from the sometimes aggressive tone of these demands. Toxic conversations may demotivate and burn out developers, creating challenges for sustaining open source. We outline a path toward finding, understanding, and possibly mitigating such unhealthy interactions. We take a first step toward finding them, by developing and demonstrating a measurement instrument (an SVM classifier tailored for software engineering) to detect toxic discussions in GITHUB issues. We used our classifier to analyze trends over time and in different GITHUB communities, finding that toxicity varies by community and that toxicity decreased between 2012 and 2018.