Understanding group maintenance behavior in Free/Libre Open-Source Software projects: The case of Fire and Gaim

Wei, Kangning; Crowston, Kevin; Li, Na Lina; Heckman, Robert

doi:10.1016/j.im.2014.02.001

Cited by 14 publications

(26 citation statements)

References 66 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…First, the ML NLP might be improved with a richer feature set, though as noted, the performance was already as good as would be expected from an additional human coder. Second, we can consider the effects of additional group maintenance behaviours suggested by Wei et al [19]. The Syracuse SOCQA project has had some success applying ML NLP techniques to these codes, suggesting that this analysis is feasible.…”

Section: Discussionmentioning

confidence: 99%

“…Scialdone et al [18] and Wei et al [19] analyzed group maintenance behaviours used by members to build and maintain reciprocal trust and cooperation in their everyday interaction messages, e.g., through emotional expressions and politeness strategies. Specifically, Scialdone et al [18] found that core members of two teams used more politeness strategies than did peripheral members.…”

Section: Theory and Hypothesesmentioning

confidence: 99%

“…Scialdone et al [18] and Wei et al [19] studied only a few projects and noted problems making comparisons across projects that can be quite diverse. To address this concern, in this paper we studied a larger number of projects (74 in total) that all operated within a common framework at a similar stage of development.…”

Section: Settingmentioning

confidence: 99%

“…To judge the second criteria may require reviewing the sentence in the context of the whole conversation. This usage is only one of the many indicators of group maintenance studied by Scialdone et al [18] and Wei et al [19], but it is interesting and tractable for analysis.…”

Section: Expressions Of Belonging To the Teammentioning

confidence: 99%

See 3 more Smart Citations

Core-periphery communication and the success of free/libre open source software projects

Crowston

Shamshurin

2017

J Internet Serv Appl

Self Cite

View full text Add to dashboard Cite

We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We also compare the volume and content of communication produced by core (committer) and peripheral members and by those peripheral members who are later elected to be core members. We find that volume of communication is related to project success but use of inclusive pronouns does not distinguish successful projects. Core members exhibit more contribution and use of inclusive pronouns than peripheral members.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Theory and Hypothesesmentioning

confidence: 99%

Section: Settingmentioning

confidence: 99%

Section: Expressions Of Belonging To the Teammentioning

confidence: 99%

See 2 more Smart Citations

Core-periphery communication and the success of free/libre open source software projects

Crowston

Shamshurin

2017

J Internet Serv Appl

Self Cite

View full text Add to dashboard Cite

show abstract

“…Studies have demonstrated that more than 80% of FLOSS projects fade away due to insufficient long-term participation [10] [12]. "The most common length of participation, across all roles, is no longer than a single month, reflecting a highly skewed distribution of participation", and the tenure of participants varies significantly according to the roles [1].…”

Section: Introductionmentioning

confidence: 99%

Role Distribution and Transformation in Open Source Software Project Teams

Wang

Perry

2015

2015 Asia-Pacific Software Engineering Conference (APSEC)

View full text Add to dashboard Cite

In Free/Libre and Open-Source Software (FLOSS) project teams, different roles make different types of contributions to the projects, and it has been demonstrated that keeping a rational role distribution is of great significance to the potential growth and expansion of the projects. To identify the underlying patterns of team structures and role transformations, we perform an empirical study on 89 popular GitHub projects. The distribution of 9 roles and 66 types of role transformations are analyzed. Four clusters of FLOSS projects are identified in terms of the distinct characteristics on the proportion of 9 roles (i.e., the team structure) and the frequency of occurrence, duration, and Times of Activeness (ToA) of role transformations. This study would help FLOSS project coordinator have a deeper understanding of dynamic role distributions and role transformations in their teams, so as to take initiatives to improve their team structures.

show abstract

Learning from Elitist Jerks: Creating high‐quality knowledge resources from ongoing conversations

Bullard

Howison

2015

Asso for Info Science & Tech

View full text Add to dashboard Cite

Online-community management is commonly presented as the facilitation of conversation and contributions, especially converting readers to contributors. However, the goal of many discussion communities is to produce a high-quality knowledge resource, whether to improve external task performance or to increase reputation and site traffic. What do moderation practices look like when the community is focused on the creation of a useable knowledge resource rather than facilitating an inclusive conversation? Under what conditions is this style of moderation likely to be successful? We present a case study from online gaming-Elitist Jerks-in which aggressive moderation is used to transform a conversational medium into a high-quality knowledge resource, using the strategy of open censorship. We present a content analysis of moderator comments regarding censored messages. Our analysis revealed differences in types of contributor mistakes and the severity of moderator actions: infractions that interfered with both conversation and resource quality were punished harshly, whereas a set of infractions that supported conversation but undermined resource quality were more respectfully removed. We describe a set of conditions under which moderators should intervene in the conversion of conversation to knowledge resource rather than the conversion of lurkers to contributors.

show abstract

Understanding group maintenance behavior in Free/Libre Open-Source Software projects: The case of Fire and Gaim

Cited by 14 publications

References 66 publications

Core-periphery communication and the success of free/libre open source software projects

Core-periphery communication and the success of free/libre open source software projects

Role Distribution and Transformation in Open Source Software Project Teams

Learning from Elitist Jerks: Creating high‐quality knowledge resources from ongoing conversations

Contact Info

Product

Resources

About