Co-destruction Patterns in Crowdsourcing

Bidar, Reihaneh; Hofstede, Arthur H. M. ter; Sindhgatta, Renuka

doi:10.1007/978-3-030-49435-3_4

Cited by 3 publications

(9 citation statements)

References 43 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The four chosen projects develop widely used python frameworks and have over 500 contributors (Table 2). We use the GitHub API 3 made by over 5800 software contributors. The contributions include discussions, source code commits, the raising of software defects, and reviews in the context of the development.…”

Section: A Data Extraction and Analysismentioning

confidence: 99%

“…Although the success of crowdsourcing has gained attention from researchers and practitioners, the dynamics and openness of crowdsourcing systems can lead to various destructive patterns that if not addressed will diminish their successful deployment [3]. Workers in crowdsourcing come from an "undefined network community, so it's hard to guarantee that they can work together" [34].…”

Section: Introductionmentioning

confidence: 99%

“…Understanding the influencing factors of task failure becomes essential for organisations to improve their crowdsourcing initiatives [17]. But more importantly, the varying forms of actor dynamics that can lead to subop-timal outcomes becomes essential [3] since crowdsourcing systems survive on the contribution of and the interaction between participants [24].…”

Section: Introductionmentioning

confidence: 99%

“…In this paper, we focus on one particular form of destructive actor dynamic in the context of crowdsourcing systems, namely stasis and we explore its various manifestations. Stasis refers to "the lack of progress in a contributed task due to inaction or adversarial action by contributors" [3]. In crowdsourcing systems such as Wikipedia, stasis manifests itself through revert cycles and back and forth interactions between participants over a period of time without any resolution.…”

Section: Introductionmentioning

confidence: 99%

“…In GitHub, for example, this can manifest itself as an owner not maintaining a project or abandoning it altogether. Stasis was seen as one of the most frequently observed destructive patterns by crowdsourcing participants (81%) and its detection and mitigation was considered to be important by the majority of participants (67%) [3].…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Detecting Crowdsourcing Impasses

2021

Self Cite

View full text Add to dashboard Cite

The adoption of crowdsourcing systems to support successful and effective collaboration among actors to perform a variety of tasks continues to grow. The success of such systems relies on actor willingness to contribute to task achievement in pursuit of a collective goal. This willingness may be negatively affected under certain circumstances. One area where this is the case is work progressing insufficiently or even grinding down to a halt. Such situations can be referred to as impasses and this has been captured more formally in the form of the Stasis pattern in previous work. In this paper, we first investigate the various forms stasis can take, next we characterise these forms in the form of a classification problem, and finally, detect their presence and predict the likelihood of their future occurrence in a practical setting. The latter is achieved through an exploratory case study involving computational analyses of development activities within an open-source crowd-sourced software platform (GitHub). Our findings contribute towards a rich understanding of stasis in crowdsourcing systems and how its various forms can be detected early (and thus mitigated) or even prevented altogether. As such, this work helps improve the chances of successful collaboration through the use of these systems.

show abstract

Section: A Data Extraction and Analysismentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%