MétaCan
Menu
Back to cohort

Why do projects join the Apache Software Foundation?

2022· article· en· W4283220029 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicOpen Source Software Innovations
Canadian institutionsQueen's UniversityPolytechnique Montréal
Fundersnot available
KeywordsJoin (topology)EclipseFoundation (evidence)SoftwareWork (physics)Open source softwareSoftware developmentBusinessComputer scienceKnowledge managementWorld Wide WebPublic relationsEngineeringPolitical science

Abstract

fetched live from OpenAlex

While numerous open source projects operate on their own, others decide to join well-established foundations such as the Apache Software Foundation (ASF) and the Eclipse Foundation. Although many studies have investigated the motivations of individuals and companies contributing to open source, it remains unknown why projects decide to join software foundations. In this paper, we study the motivators behind the projects‘ decision to join the ASF, the geographical and organizational characteristics of these projects, and the differences between projects in terms of their motivations. To this aim, we analyzed 292 proposals submitted to ASF, and we found that there is an increasing number of company-based and Asia-based projects joining the ASF in recent years. Furthermore, we found that more than half of the projects are motivated by the desire to foster their community, strengthen the outcome of the project, increase interaction with other communities, and boost technical development. Our work shed some light on projects‘ expectations from the ASF. Having this understanding can help foundations to identify ways of supporting newly joined projects, while the prospective joiners can better decide on whether ASF is the right place for them by checking the alignment of their motivations and motivations of projects that have joined in the past. Open Source Software (OSS) is free to be used and modified by any-one in the world for any purpose. Nowadays, OSS is widely used in all kinds of products and hence plays an important role in our daily life. For example, as the most used OSS, the Linux kernel runs on 85% of all smartphones. To create a better environment for OSS de-velopers to collaborate and for OSS projects to grow, many software foundations have been established, such as the Apache Software Foundation (ASF). We have seen that many OSS projects joined the ASF over the years. To join the ASF, OSS projects have to donate all their assets to the foundation, adhering to the foundation's rules and culture. In this paper, we study why these projects decide to join the ASF to understand their expectations from such foundations so that the expected technical and non-technical support can be provided to them. We identified their motivations by analyzing 292 proposals that these projects submitted when applying for joining the ASF. We observed that more than half of the projects try to join the ASF with motivations related to fostering a community, strengthening the project's outcome, increasing interactions with other OSS projects in the ASF, and boosting technical development.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.653
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.028
GPT teacher head0.261
Teacher spread0.232 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Quick stats

Citations6
Published2022
Admission routes1
Has abstractyes

Explore more

Same topicOpen Source Software InnovationsFrench-language works237,207