Roger is a software engineer focused on machine learning research and systems. He is a core maintainer of vLLM and the lead maintainer of vLLM-Omni, where he works on infrastructure for large multimodal and omni-modality models. He also recently co-founded Inferact, a startup focused on making AI inference cheaper and faster while helping grow vLLM as a major AI inference engine.
The talk was useful because Roger was speaking from direct experience maintaining open source AI infrastructure at a time when AI coding agents are changing how people contribute.
One of the clearest points was that the maintainer's inbox has changed. For vLLM, weekly new pull requests increased a lot from early 2025 to 2026, with visible spikes around major model and coding agent releases. More people can now generate code and open pull requests quickly.
That creates a real burden for maintainers. The hard part is not only reviewing whether the code works. Maintainers also need to understand whether the contributor understands the system, whether the change solves the right problem, and whether the person will stay involved after the pull request is opened.
A line from the talk captured this well:
Talk and code is cheap, show me you really care.
That was my main takeaway. In open source, a useful contribution is more than a code diff. It requires reading the codebase, understanding the project direction, explaining the design clearly, and taking responsibility for the change.
Roger highlighted a few things contributors should focus on:
Understand the system
Pick the right problem at the right scale
Communicate clearly
Have a sense of ownership and responsibility
These points sound basic, but they matter more now. If AI agents make it easier to submit code, then contributors need to show stronger signals that they understand what they are changing.
For maintainers of critical infrastructure, Roger also pointed to a few changes that matter. Standards are higher now. Projects need clearer non-goals, including when "fork it as a plugin" is a valid path. Design decisions should be reviewable, not just the code diff. Reliability matters more, which means projects need to invest more in continuous integration. Reviewer time should also be spent carefully, especially on contributors who are learning the system and likely to keep contributing.
Another point that stood out was the changing pipeline of open source talent. If the new on-ramp to open source is "prompt an agent," maintainers may see more contributors who have not deeply read the codebase. That creates risk. It also creates an opportunity to be clearer about what good contribution looks like.
The bar for human contribution is getting higher and clearer. Writing plausible code is less of a signal than it used to be. The stronger signals are system understanding, good judgment, clear communication, and trust.
I left the talk thinking that AI agents will change open source contribution, but they will not remove the human part. If anything, the human part becomes more important. The best contributors will be the people who can understand the system, communicate with maintainers, and take responsibility for the work beyond the first pull request.
For anyone trying to contribute to open source now, especially in AI infrastructure, the practical advice is simple:
Ask real questions.
Meet people outside your usual circle.
Support other contributors, especially during poster sessions and discussions.
Read the codebase before asking an agent to change it.
Show that you care about the project, not just the pull request.
Top comments (0)