Skip to main content
Copy and personalize

GSoC Proposal Template

Copy this template into your proposal and fill it in with your own project plan. Use it as structure—write and own the content. Do not submit AI-generated boilerplate.

Proposal GuidelinesProject IdeasBack to GSoC

Important: Many orgs will reject proposals that look auto-generated. Use this template as structure only—write and own the content.

Contributor information

  • Name:
  • Email:
  • Timezone:
  • GitHub:
  • LinkedIn / portfolio:
  • Resume (optional link):
  • Primary languages/stack:

Project selection

  • Project title:
  • Project size: Small (~90h) / Medium (~175h) / Large (~350h)
  • Difficulty: Easy / Medium / Hard
  • Proposed mentor(s):
  • Repos likely involved (olake / olake-ui / olake-docs / other):

Synopsis (short)

1–2 paragraphs. What are you building and why?

Problem statement and motivation

  • What problem exists today?
  • Who is affected (users/operators/maintainers)?
  • Why is this worth solving in OLake?

Background and current state

  • Show that you understand how OLake works (data flow, relevant components).
  • Link to relevant code paths or docs you reviewed.

Proposed solution

Technical design

Describe: new components/modules; API changes (CLI flags, config changes, endpoints, gRPC/protobuf if any); data model implications (Iceberg schema, metrics labels, state store schema); backward compatibility and rollout plan.

Implementation plan

Break down into concrete steps. Mention how you will validate correctness and performance.

Deliverables

Required

List the exact artifacts: code changes; tests (unit/integration); documentation updates; benchmarks (if relevant); example configs / sample pipelines.

Optional stretch goals

Clearly mark stretch goals as optional.

Timeline and milestones

Use the official GSoC 2026 timeline: developers.google.com/open-source/gsoc/timeline

Include: Community Bonding plan (what you will do before coding starts); week-by-week milestones; midterm milestone (must be meaningful and demonstrable); final "code freeze" period for testing/docs/polish.

Testing plan

  • Unit tests:
  • Integration tests:
  • How you will reproduce failure cases locally:
  • CI considerations:

Risks and mitigations

List realistic risks (unknowns in the codebase, performance risks, schema evolution edge cases, etc.) and how you will reduce them.

Communication plan

  • Weekly written updates (where you will post them)
  • Meeting cadence with mentors
  • How quickly you will respond to review feedback

Availability and other commitments

  • Estimated hours/week during coding:
  • Exams/internships/vacations:
  • Any known no-work periods:

Prior work / proof you can execute

  • OSS contributions (links)
  • Any OLake PRs/issues you participated in (links)
  • Relevant projects (short summary + links)
Proposal GuidelinesProject IdeasSubmit at GSoC