GSoC

From PostgreSQL wiki
Jump to navigationJump to search

PostgreSQL goes through the Google Summer of Code application process.

This page is your starting point for PostgreSQL's participation in the GSoC program. Please watch this page for updates, and make sure you read everything before proceeding to examine proposals. The proposals link is highlighted in one of the sections below.

Admins

  • Pavlo Golub <pavlo (dot) golub (at) gmail (dot)>
  • Jesper Pedersen <jesperpedersen (dot) db (at) gmail (dot) com>
⚠️WARNING!

If you want to discuss Google Summer of Code projects, contact us through email, please. DO NOT CONTACT ORGANIZATION ADMINS ON LINKEDIN OR OTHER PRIVATE SOCIAL MEDIA CHANNELS. Abuse of private social media of organization admins might compromise your chances of your proposal being accepted.

Mentors

If you want to submit a GSoC proposal that you want to mentor, contact the PostgreSQL org admins, please.

Note, that a proposal requires a primary mentor, and a backup mentor. The primary mentor has to be unique, so only ONE proposal per primary mentor. The primary mentor also has to sure that the project submitted can be COMMITTED before the GSoC project deadline.

DO NOT SUBMIT A PROPOSAL BEFORE YOU HAVE DISCCUSED IT WITH THE ADMINS, AND FILLED THE TWO MENTOR SLOTS.

Contributor

Slack

Postgres Slack channel: link

Note: If you can't join the channel please send an email to gsoc-mentors@lists.postgresql.org

We have an informal Slack channel for #gsoc-contributors link. General guidelines:

  • Feel free to ask questions about setting up projects, infrastructure, tech stack, tips (anything that other potential contributors might also wonder, or benefit from)
  • Get to know fellow contributors, introduce yourself

Do NOT use Slack to send proposal drafts to mentors!

Some mentors are on Slack, but some prefer not to be. Each mentor is free to choose their preferred communication channel, indicated in each proposal. Only email mentors if EXPLICITLY STATED in the project proposal. Otherwise, you can find them on Slack. This holds in particular for organization admins who are also mentors - please do not contact us via email unless absolutely necessary, and use Slack.

Mailing list

Please email gsoc-mentors@lists.postgresql.org

We have an internal mailing list that all mentors can read, use this for any kind of communication that should be private and you might not want other contributors to see. Examples:

  • Proposal drafts (to get feedback)
  • New ideas
  • Any other personal matter

Applying

Here are some general guidelines on what to do if you are interested in GSoC 2026.

  • Read carefully through this webpage
  • Read the list of proposals for 2026
  • Find 1-2 proposals you would like to know more about, or some other project idea not in the list that you would like to work on
  • Identify the correspondent mentors, and their preferred communication channels
  • (Optional) Join Slack to see whether some other contributor is interested in the same project, or some question has already been asked, and eventually ask your own questions
  • Set up the infrastructure, read the project documentation, try running it locally
  • Think about how the mentor ideas can be integrated, and ask them any further question you may have
  • Start writing your proposal
  • Send the drafts to the mentors MAILING LIST and ask for feedback (Google Docs or PDF)
  • Submit your final proposal through the Google Summer of Code website

In your proposal, we ask that you create:

  • A list of deliverables
  • A detailed description
  • Outline your approach
  • Outline your approximate schedule
  • A document describing your background and motivation

Please also include if you have other commitments during the period of GSoC. This includes jobs (part time or full time), exams, vacation, and anything else which might prevent you from working on your project.

Please, try and keep your application around 4 pages.

We encourage you to contact the PostgreSQL Project through the mentors mailing list before submitting your proposal through the GSoC website, and discuss the details with us. Proposal changes after the deadline can't be accepted.

Please send your proposal to: [tbd]. The deadline for proposals is **April 02, 2026**.

Proposals

Project ideas collected for GSoC 2026

A regular proposal should follow this template:

Project Description

The project focuses on ...

Skills needed

  • Proficiency in ...
  • Familiarity with ...
  • Experience with ...
  • Basic understanding of ...
  • PostgreSQL

Difficulty level

Easy|Moderate|Hard

Project size

Small: approximately ~90 hours of work. Medium: approximately ~175 hours of work. Large: approximately ~350 hours of work.

Mentors

  • ... (Primary)
  • ... (Backup)

Expected outcomes

  • A refined set of ...
  • Updated and polished ...
  • Enhanced ...
  • Documentation outlining ...
  • Tests covering ...

References

Help

There are several resources which can provide help.

Useful links

Years

Retrieved from "https://wiki.postgresql.org/index.php?title=GSoC&oldid=42757"