The Human Layer of Open Source

At a Maintainer Unconference in Brussels this year, a breakout session on the future of open source produced one sticky note that captured the mood: as AI improves at writing code, the human work around code becomes more important and more invisible. Mentoring contributors, building community trust, and making judgement calls about a project's direction—that is what turns a repository into a genuine collaboration.

The pace isn't slowing down. Pull requests merged on GitHub have nearly doubled year over year, and agentic workflows are pushing even harder. Maintainers are feeling it. One put the dilemma bluntly: how much time should be spent reviewing something the contributor didn't spend any time on? There is weariness in the conversations this year, but there is also innovation. Maintainers are rallying around standards like agents.md, building trust systems, and designing workflows that put control back in their hands.

New Controls for the Contribution Firehose

The influx of low-quality contributions has been a recurring theme, flagged in February as open source's Eternal September. In response, GitHub has been shipping tools maintainers asked for—specifically, repeatedly, and often loudly.

  • Granular contribution limits: Maintainers can now set limits on how many pull requests a new or unknown user can make, avoiding the binary of closing the doors entirely or leaving the floodgates open.
  • Pull request archiving: Spam PRs can be swept out of public view without needing to contact support for cleanup.
  • Pull request creation controls: Repositories can restrict PR creation to collaborators only, or disable PRs entirely—useful for mirrors, roadmaps, and similar projects.
  • Pinned comments on issues: The most important comment can now be pinned to the top of any issue thread.
  • Sort notifications oldest-first: A new control to work through the backlog in order rather than always chasing the latest ping.
  • File upload in issue forms: Structured issue templates now support file uploads.

There's also a new accessibility best practices guide on opensource.guide, offering practical steps to make projects usable by everyone.

Ecosystem Support and Resources

Maintainer Month has drawn support from across the ecosystem, with companies and foundations putting real resources behind maintainers. Offerings include free tools, compute credits, threat intelligence, conference tickets, and more.

Open source runs on maintainers, and we're proud to partner with GitHub to celebrate and support them. As the ecosystem scales, maintainers are doing more than ever to keep projects secure and reliable. Maintainer Month is a chance to connect, share knowledge, and remind them they're not doing this alone.

— Robin Ginn, OpenJS Foundation

A Partner Pack consolidates what's available:

  • Sentry: Sentry for Open Source
  • Daytona: $100 in compute credits for maintainers (and up to $10,000 for projects via Startup Grid)
  • Mockoon: Free Mockoon Cloud accounts for OSS projects
  • Ref.tools: Free project planning tools
  • Arachne Digital: Free cyber threat intelligence reporting for OSS projects
  • Radix / .Tech: Free 1-year .tech domain for maintainers
  • OpenJS Foundation: 15% discount on RenderATL tickets (code: OPENJSGITHUB)
  • Open Source Initiative: The maintaine.rs book, free for all maintainers
  • Web Summit: Conference tickets (details coming soon)

Last year, Sentry took a creative approach by celebrating companies that fund open source on a Times Square billboard. Companies, startups, and educators interested in participating can reach out about the Partner Pack or explore the GitHub Partner Program.

There's also news for those maintaining tools for science: the Open Source for Science Fund has launched with $20 million in funding, offering grants up to $1 million for projects supporting data-intensive research. Letters of intent open May 11.

Community and Events

More than 20 events and streams are scheduled throughout Maintainer Month, ranging from meetups to conference appearances to hackathons. Highlights include a Maintainers Meetup in Delhi (May 9), PyCon US 2026 in Long Beach (May 13–19), a virtual discussion on how corporations should support OSS maintainers (May 14), a two-day Open Source Assistive Technology Hackathon in San Francisco (May 21–22), and a virtual session on licensing, SBOMs, and security in light of the EU's Cyber Resilience Act (May 27).

A common refrain this year is the desire to be part of something bigger rather than operating as a solo maintainer. The Maintainer Community is a vetted space designed for that—an environment for sharing experiences, getting support, and having honest conversations about the realities of maintenance. Members also get access to an exclusive tier of the Partner Pack with deeper discounts and higher credit limits.

How to Take Part

For those looking to support maintainers directly, the options range from financial to personal. Sponsoring a maintainer through GitHub Sponsors is one of the most direct forms of support. Hosting or attending an event—or submitting one to the calendar—helps build the community. Sharing stories with the #MaintainerMonth tag makes the work visible.

Sometimes the simplest gesture matters most: find a project you depend on and tell the maintainers you appreciate them. Open source is changing fast, but the reality remains that real people choose every day to maintain the software the world runs on—and millions depend on that choice.