Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Efficiency for Experts, Visibility for Newcomers: A Case Study of Label-Code Alignment in Kubernetes

Matteo Vaccargiu, Sabrina Aufiero, Silvia Bartolucci, Ronnie de Souza Santos, Roberto Tonelli, Giuseppe Destefanis

Abstract

Labels on platforms such as GitHub support triage and coordination, yet little is known about how well they align with code modifications or how such alignment affects collaboration across contributor experience levels. We present a case study of the Kubernetes project, introducing label-diff congruence - the alignment between pull request labels and modified files - and examining its prevalence, stability, behavioral validation, and relationship to collaboration outcomes across contributor tiers. We analyse 18,020 pull requests (2014--2025) with area labels and complete file diffs, validate alignment through analysis of over one million review comments and label corrections, and test associations with time-to-merge and discussion characteristics using quantile regression and negative binomial models stratified by contributor experience. Congruence is prevalent (46.6\% perfect alignment), stable over years, and routinely maintained (9.2\% of PRs corrected during review). It does not predict merge speed but shapes discussion: among core developers (81\% of the sample), higher congruence predicts quieter reviews (18\% fewer participants), whereas among one-time contributors it predicts more engagement (28\% more participants). Label-diff congruence influences how collaboration unfolds during review, supporting efficiency for experienced developers and visibility for newcomers. For projects with similar labeling conventions, monitoring alignment can help detect coordination friction and provide guidance when labels and code diverge.

Efficiency for Experts, Visibility for Newcomers: A Case Study of Label-Code Alignment in Kubernetes

Abstract

Labels on platforms such as GitHub support triage and coordination, yet little is known about how well they align with code modifications or how such alignment affects collaboration across contributor experience levels. We present a case study of the Kubernetes project, introducing label-diff congruence - the alignment between pull request labels and modified files - and examining its prevalence, stability, behavioral validation, and relationship to collaboration outcomes across contributor tiers. We analyse 18,020 pull requests (2014--2025) with area labels and complete file diffs, validate alignment through analysis of over one million review comments and label corrections, and test associations with time-to-merge and discussion characteristics using quantile regression and negative binomial models stratified by contributor experience. Congruence is prevalent (46.6\% perfect alignment), stable over years, and routinely maintained (9.2\% of PRs corrected during review). It does not predict merge speed but shapes discussion: among core developers (81\% of the sample), higher congruence predicts quieter reviews (18\% fewer participants), whereas among one-time contributors it predicts more engagement (28\% more participants). Label-diff congruence influences how collaboration unfolds during review, supporting efficiency for experienced developers and visibility for newcomers. For projects with similar labeling conventions, monitoring alignment can help detect coordination friction and provide guidance when labels and code diverge.

Paper Structure

This paper contains 42 sections, 6 equations, 3 figures, 6 tables.

Table of Contents

  1. Introduction
  2. Related Work
  3. Issue Labeling and Coordination in Software Projects
  4. Code Review Dynamics and Collaboration Outcomes
  5. Contributor Experience and Activity Patterns
  6. Human and Social Aspects of Code Review
  7. Dataset
  8. Methodology
  9. Data collection and feature construction
  10. Label normalization and path tokenization.
  11. Metrics.
  12. Descriptive and stability analyses (RQ1)
  13. RQ1—Prevalence and distribution.
  14. RQ1—Temporal stability.
  15. RQ1—Interpretability via area--token associations.
  16. ...and 27 more sections

Figures (3)

  • Figure 1: Overview of the methodology. Data from the Kubernetes repository is processed to construct label--diff congruence metrics, which are then analyzed to assess prevalence, stability, and interpretability (RQ1), and their relationship with collaboration outcomes (RQ2).
  • Figure 2: Quarterly median congruence with Theil--Sen robust fit (2016 Q1 to 2025 Q1). The modest upward trend indicates stable labeling practices over nine years of project growth.
  • Figure 3: Congruence effects by contributor tier (IRRs with 95% CIs). Left: comments. Right: participants. Gray dashed line indicates no effect (IRR=1); red dotted line shows pooled estimate. Effects reverse direction for one-time versus core contributors.