# ensarguet-signal-noise-contribution-ai-slop-open-source-2026-02-04

## Veille

Rethinking open source contribution in the face of "AI slop" - Signal vs noise

## Titre Article

Signal over noise: rethinking what "contribution" means in the age of AI slop

## Date

2026-02-04

## URL

https://www.linkedin.com/pulse/signal-over-noise-rethinking-what-contribution-means-age-ensarguet-77qpe/

## Keywords

Open source, AI slop, contributions, signal vs noise, Ghostty, tldraw, cURL, bug bounty, maintainers, burnout, open source governance, friction, context, verification

## Authors

Philippe Ensarguet

## Ton

**Profile**: Strategic analysis, reflective and pragmatic register, intermediate technical level

**Description**: Philippe Ensarguet adopts the tone of a seasoned observer of the open source ecosystem, combining lucid diagnosis with constructive proposals. The article avoids the trap of anti-AI discourse to focus on the signal/noise issue. The style is structured around an original framework (Contribution Stack) and concrete examples of major projects that have reacted. The target audience includes maintainers, fondations open source, and tech decision-makers.

## Pense-betes

- **Fundamental problem**: Open source relied on an implicit contract where effort signaled understanding. AI decoupled this relationship by enabling "plausible contributions with zero understanding and zero effort"
- **Drastic reactions from major projects**:
- **Ghostty**: Permanent bans for AI-generated code
- **tldraw**: Automatic closure of external PRs
- **cURL**: Shutdown of the bug bounty program (overwhelmed by meaningless submissions)
- **"Contribution Stack" framework**: 5 layers - raw output → understanding → investment → relationships → community belonging. AI produces the superficial layer instantly but bypasses meaningful engagement
- **Shifting from effort to context**: Measuring context rather than banning AI
- Is the submission clearly linked to issues?
- Does the description demonstrate understanding?
- Are the tests comprehensive?
- Has the code been tested?
- → "Basics for professional engineering" but open source relied on effort barriers as an implicit filter
- **Three possible futures**: 1. **Walled gardens**: Contributions restricted to known entities (risk: stifling new maintainers) 2. **Verification layers**: Systems tracing participation history and genuine engagement 3. **Bifurcation**: Different governance models by project type (infrastructure = more restrictive)
- **Foundations gap**: Focus on licensing and IP while maintainers face immediate problems of quality and burnout. Suggestion: fund detection tools, certification frameworks, contribution analytics
- **Key position**: Not anti-AI, but a signal/noise challenge requiring an intentional redesign around demonstrated understanding rather than output volume

## RésuméDe400mots

Philippe Ensarguet analyzes how IA générative is upending open source's contribution model, turning a technical problem into a community governance crisis.

**The broken implicit contract**: Open source ran on a tacit agreement where the effort of contributing signaled a genuine understanding of the project. AI decoupled this relationship by making it possible to produce "plausible-looking contributions with zero understanding and zero effort". Faced with this flood of "AI slop", major projects have reacted drastically: Ghostty imposes permanent bans for AI-generated code, tldraw automatically closes external PRs, and cURL had to shut down its bug bounty program, overwhelmed by meaningless submissions.

**The Contribution Stack**: Ensarguet proposes a framework breaking contributions down into five layers: raw code output, understanding of the project, personal investment, relationships with the community, and community belonging. Traditional friction naturally filtered at the deeper layers. AI instantly produces the superficial layer while completely bypassing meaningful engagement.

**From effort-based filtering to context-based filtering**: Rather than banning AI, the author advocates measuring demonstrated context. Is the submission clearly linked to existing issues? Does the description demonstrate real understanding? Are the tests comprehensive? Has the code actually been tested? These criteria are not revolutionary - they are the "basics of professional engineering" - but open source historically relied on effort barriers as an implicit filter for these qualities.

**Three future scenarios**: Walled gardens restrict contributions to known entities, risking stifling the emergence of new maintainers. Verification layers trace participation history and demonstrate genuine engagement. Bifurcation applies different governance models depending on project type, with infrastructure projects restricting themselves more severely than applications.

**The foundations gap**: While institutions have focused on licensing and intellectual property, maintainers face immediate problems of quality and burnout. Ensarguet suggests that foundations could fund detection tools, certification frameworks, and contribution analytics rather than imposing top-down policies.

The article explicitly positions itself not against AI, but as an analysis of the signal/noise challenge requiring an intentional redesign of contribution systems around demonstrated understanding rather than raw output volume.

## GrapheDeConnaissance

- Philippe Ensarguet —a_créé→ Contribution Stack (METHODOLOGIE, 0.98)
- IA générative —permet→ contributions plausibles sans effort ni compréhension (CONCEPT, 0.97)
- Ghostty —s_oppose_à→ code généré par IA (CONCEPT, 0.98)
- tldraw —s_oppose_à→ PRs externes (CONCEPT, 0.97)
- cURL —publie→ arrêt du programme bug bounty (EVENEMENT, 0.98)
- AI slop —permet→ burnout des mainteneurs (CONCEPT, 0.92)
- Philippe Ensarguet —recommande→ filtrage par le contexte (METHODOLOGIE, 0.97)
- Contribution Stack —s_applique_à→ contributions open source (CONCEPT, 0.96)
- Philippe Ensarguet —affirme_que→ les fondations open source négligent la qualité et le burnout des mainteneurs (AFFIRMATION, 0.88)
- Philippe Ensarguet —prédit→ bifurcation gouvernance open source (AFFIRMATION, 0.9)
- Philippe Ensarguet —affirme_que→ l'AI slop transforme le modèle contributif open source (AFFIRMATION, 0.95)
- Philippe Ensarguet —recommande→ financement par les fondations d'outils de détection AI slop (AFFIRMATION, 0.87)

---
Canonical: https://www.thekb.eu/en/fiches/ensarguet-signal-noise-contribution-ai-slop-open-source-2026-02-04/