typelevel / typelevel/tsc

Plan for Typelevel's exodus from GitHub: AI slop, disrespect, and a future without control

Open
#164 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
11
Forks
4
Avg merge
1h 49m
Merged PRs (30d)
2

Description

[!IMPORTANT]
ai;dr: What follows is a generated issue, but maybe if we helplessly stand in place as the slop rises from knee deep to neck deep, GitHub will become agentic enough that we can just ask the bots to move us.

The Gathering Storm: GitHub's Descent into AI Slop

The Typelevel community is at a crossroads. The relentless proliferation of AI-generated issues and pull requests—slop churned out by tools like Copilot—represents an existential threat to the integrity and sustainability of open source stewardship. Maintainers are besieged by a relentless tide of low-effort, irrelevant, and frequently nonsensical contributions, all in the service of Microsoft's bottom line.

Utter Disregard for Maintainers

AI-generated issues are not just a nuisance; they are a flagrant insult to the time and expertise of maintainers. These so-called "contributions" waste scarce human attention, trivialize the value of genuine participation, and further erode the quality of our shared work.

Microsoft and GitHub: Champions of Hostility

Microsoft continues to unleash maintainer-hostile tools, heedless to the outcry of the very communities that make their platform possible. The recent announcement that Copilot can now create issues automatically is yet another brick in a wall of contempt.

Worse, Microsoft/GitHub has steadfastly refused to provide even the most basic tools for communities to defend themselves. No opt out. No labeling. No recourse. See GitHub Community Discussion.

Demand for Action: Plan the Exodus

We must begin planning Typelevel's departure from GitHub before the deluge becomes an unmanageable catastrophe. Alternatives such as Codeberg, SourceHut, or even a self-hosted forge now demand serious consideration. If we do not act, we will be complicit in our own marginalization.

The time for complacency is over. The era of AI slop is upon us, and only decisive action will safeguard the future of our projects and our community.

Let us not be remembered as the generation that surrendered open source to the algorithms of indifference.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue proposes planning Typelevel's departure from GitHub and evaluating Codeberg, SourceHut, or a self-hosted forge. No repository files, implementation entry points, tests, or acceptance criteria are identified; first define the migration scope and decision process before work can begin. Done is not specified in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.