Paid vs. Volunteer Work in Open Source

Riehle, Dirk; Riemer, Philipp; Kolassa, Carsten; Schmidt, M. P.

doi:10.1109/hicss.2014.407

Cited by 55 publications

(40 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Software professionals serving both corporate and community interests are representative of the Linux Foundation open source environment, as this environment is predominately comprised of corporate members. At a broad level, nearly “50% of all work contributed to open source software projects has been provided Monday to Friday, between 9 am and 5 pm," serving as a valuable indicator of corporate‐communal engagements (Riehle, Riemer, Kolassa, & Schmidt, , pg. 4).…”

Section: Methodsmentioning

confidence: 99%

The Third Design Space: A postcolonial perspective on corporate engagement with open source software communities

Kendall

Mathiassen

2019

Information Systems Journal

View full text Add to dashboard Cite

Corporations increasingly engage with open source software communities in the co‐creation of software. This collaboration between corporate professionals and open source software community members is strikingly different from the early days of software development where for‐profit firms attempted to dominate and control the industry while attempting to throttle the success of independent developers offering an alternative, open source option. While many metaphors like trading zones, common pool resources and ecosystems have helped understand the phenomenon, the metaphors do not portray what the industry was like before and after the transition. We adopt a postcolonial metaphor as an analytical lens to examine such collaboration based on qualitative data gathered over three years from executives, managers and developers within corporations that engage in open source software development. Drawing on these insights, we then theorize a “Third Design Space,” based on the concept of the third space proposed by Bhabha. This metaphor encourages the cultivation of a new design environment, creation of new design associations and circulation of shared design resources. Together these practices and behaviours make it possible to nurture innovative methods and new rituals for designing software with results and methods that represent a distinct departure from the competitive and proprietary past, even creating innovative artefacts that could not have been created without the Third Design Space.

show abstract

Section: Methodsmentioning

confidence: 99%

The Third Design Space: A postcolonial perspective on corporate engagement with open source software communities

Kendall

Mathiassen

2019

Information Systems Journal

View full text Add to dashboard Cite

show abstract

“…All the projects in Table 3 are found to be developed or supported by companies or laboratories. In general, non-company developers are likely to join OSS projects as hobbyists [22], but company and laboratory developers probably join OSS projects as part of their work [22], [29]. Therefore, projects supported by company or * 9 CocoaPods is the dependency manager for Swift and Objective-C. laboratory developers are more likely to be constantly contributed by the same developers than projects supported by non-company developers.…”

Section: Study Resultsmentioning

confidence: 99%

Magnet or Sticky? Measuring Project Characteristics from the Perspective of Developer Attraction and Retention

Yamashita

Kamei

McIntosh

et al. 2016

Journal of Information Processing

View full text Add to dashboard Cite

Open Source Software (OSS) is vital to both end users and enterprises. As OSS systems are becoming a type of infrastructure, long-term OSS projects are desired. For the survival of OSS projects, the projects need to not only retain existing developers, but also attract new developers to grow. To better understand how projects retain and attract contributors, our preliminary study aimed to measure the personnel attraction and retention of OSS projects using a pair of population migration metrics, called Magnet (personnel attraction) and Sticky (retention) metrics. Because the preliminary study analyzed only 90 projects and the 90 projects are not representative of GitHub, this paper extend the preliminary study to better understand the generalizability of the results by analyzing 16,552 projects of GitHub. Furthermore, we also add a pilot study to investigate the typical duration between releases to find more appropriate release duration. The study results show that (1) approximately 23% of developers remain in the same projects that the developers contribute to, (2) the larger projects are likely to attract and retain more developers, (3) 53% of terminal projects eventually decay to a state of fewer than ten developers and (4) 55% of attractive projects remain in an attractive category.

show abstract

“…We tested the performance of these models on all the commits and on the commits of the least active developers ( Table 5). We also computed the performance metrics when considering as paid commits, all the commits (allpaid), the commits made by a developer with at least a Mozilla email address (email) as done in our previous study [15], and the commits made during regular office hours (officehours) as done by Riehle et al [17].…”

Section: Predicting Paid Commitsmentioning

confidence: 99%

“…This simplifies the process of manually gathering employment status of developers needed to train and test our classifiers. We then compare our results with the ones obtained by applying techniques used in the literature we are aware of [15,17].…”

Section: Introductionmentioning

confidence: 97%