Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
---
title: How to Be the Contributor Maintainers Actually Want — Lessons from Pollinations.ai
metaTitle: How to Be the Contributor Maintainers Actually Want — Lessons from Pollinations.ai
metaDesc: >-
A practical, opinionated 30-minute talk for students and early-career developers who want their
first (or next) open source PR to actually land. With concrete examples from pollinations.ai,
learn what 30 seconds of contributor effort can save a maintainer 30 minutes of work.
date: '05/31'
endDate: '05/31'
UTCStartTime: '13:00'
UTCEndTime: '13:30'
type: talk
language: English
location: Virtual
userName: Ayushman Bhattacharya
userLink: 'https://gdg.community.dev/gdg-on-campus-jis-university-kolkata-india/'
linkUrl: 'https://gdg.community.dev/gdg-on-campus-jis-university-kolkata-india/'
---

**The pitch:** Every student wants to "contribute to open source." Almost nobody thinks about what it looks like from the other side of the PR. I'm a maintainer at [pollinations.ai](https://github.com/pollinations/pollinations) — a free, open generative AI platform — and in this 30-minute talk I'll show what 30 seconds of contributor effort can save a maintainer 30 minutes of work, with concrete examples from our repo.

This isn't a meta-talk about the "maintainer crisis." It's a practical, opinionated session for students who are about to open their first PR — so they open one a maintainer actually wants to merge.

**What I'll cover:**

**1. What a PR looks like from the maintainer's chair**
Walking through a real triage queue: what gets merged in 5 minutes, what sits for a week, and why. Hint: it's almost never about the code.

**2. The 5-minute pre-flight checklist that puts you ahead of 80% of contributors**
Reading CONTRIBUTING.md. Searching closed issues before opening a new one. Running the linter locally. Writing a PR description a maintainer can review without opening the diff. None of this is glamorous; all of it works.

**3. How I went from a typo-fix PR to maintainer at pollinations.ai**
The actual path — starting by building *on* the project (a Discord bot on the Pollinations API) before contributing *to* it. Why "show, don't ask" beats "can I be a maintainer?" every time.

**4. AI-assisted PRs: the new contributor trap**
At pollinations we now see PRs that are clearly LLM-generated with no human review. I'll show what good AI-assisted contribution looks like vs. what gets closed on sight.

**5. The Hacktoberfest lens**
I've helped onboard 100+ first-time contributors during Hacktoberfest and co-hosted Kolkata's meetup with 290+ participants. The patterns that separate one-time PRs from contributors who come back are surprisingly consistent.

**Who this is for:** Students and early-career developers who want their first (or next) open source PR to actually land — not just exist. You'll leave with a checklist you can apply to any repo, that same day.
Loading