Contribute

Help build the catalog.

GSoCDex is open-source and runs on community contributions. Here's how to help.

Submit your accepted proposal

If your GSoC proposal was accepted and isn't listed here yet, the easiest path is the submission form. Owner reviews each submission, runs the ingest pipeline, and deploys.

Open a pull request

Bigger contributions — design improvements, new tips articles, accessibility fixes, better tech-tag detection — are best done as a GitHub PR. The repo lives at github.com/PankajKumardev/GsoCDex.

• pnpm install, then pnpm ingest to clone source archives and refresh data/proposals.json.
• pnpm dev for local development at localhost:3000.
• pnpm verify to run our content / trademark sweep before pushing.
• pnpm build to produce the production bundle.

Add a new source archive

We pull from these community archives today:

• SammanSarkar/GSoC_archive_2025 — Org/file.pdf
• satwiksps/GSoC_archive_2026 — Org/{Accepted,Rejected}/file.pdf
• Aritra8438/GSoC_archive — YYYY/Org/Proposals/{Accepted,Rejected}/file.pdf
• Google-Summer-of-Code-Archive/gsoc-proposals-archive — YYYY/Org/file.pdf

If you maintain a similar archive with a permissive license (MIT, Apache, BSD, or CC-BY), open an issue and we'll add it to lib/constants.ts → SOURCE_REPOS. Each newly-added repo gets a license check on every ingest run.

What we do not accept

• AI-generated proposals or content (we curate real, accepted proposals only).
• Commercial / referral content disguised as proposals.
• Newsletter widgets, email-collection forms, or any user-tracking code beyond the existing Vercel Analytics integration.