public inbox for pgsql-novice@postgresql.org
help / color / mirror / Atom feedFrom: Laurenz Albe <laurenz.albe@cybertec.at>
To: Yaten Dhingra <yaten598@gmail.com>
To: pgsql-novice@lists.postgresql.org
Subject: Re: Interested in contributing to PostgreSQL documentation and technical writing
Date: Fri, 20 Mar 2026 16:27:33 +0100
Message-ID: <62a535e8a3779e37060ca7862d2d5dabe654b049.camel@cybertec.at> (raw)
In-Reply-To: <CAEdzM0Vx7feHudw1+r_ZM=B50evFz+++P6TLMZf47xXNoYij4w@mail.gmail.com>
References: <CAEdzM0Vx7feHudw1+r_ZM=B50evFz+++P6TLMZf47xXNoYij4w@mail.gmail.com>
On Fri, 2026-03-20 at 17:05 +0530, Yaten Dhingra wrote:
> I’m particularly interested in contributing to PostgreSQL in a non-code capacity,
> specifically in areas like documentation, tutorials, blog posts, or any form of
> technical writing and developer advocacy.
>
> I wanted to ask:
> * Are there any ongoing initiatives or areas in PostgreSQL documentation that need contributions from newcomers?
> * Is there a recommended way to get started with writing or improving docs?
> * Are there opportunities to contribute blog posts or educational content under the PostgreSQL ecosystem?
>
> I would really appreciate any guidance, resources, or pointers on how to begin contributing in this space.
> Looking forward to learning from and contributing to the community.
Get used to how people communicate on the mailing lists, because they are the
communication medium you are going to use. Write plain text e-mails, trim
down text you are quoting, reply inline: you are writing for the archives, too!
About the mailing lists:
https://www.postgresql.org/list/
In particular, hang out on the pgsql-docs list. That might also give you
some inspiration about what you want to work on.
There is intoductory material for hacking on the PostgreSQL source:
A concise introduction:
https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F
Developer FAQ:
https://wiki.postgresql.org/wiki/Developer_FAQ
If you want to write documentation, not all of that is relevant for you, but
some is. In particular, you will have to write patches and work with the
Git repository:
https://wiki.postgresql.org/wiki/Working_with_Git
About submitting patches:
https://wiki.postgresql.org/wiki/Submitting_a_Patch
A great way to start is by reviewing patches in the current commitfest:
https://wiki.postgresql.org/wiki/Commitfest
https://wiki.postgresql.org/wiki/Reviewing_a_Patch
Patch review is a valued contribution, and if you review documentation patches,
you will learn a lot about writing such patches yourself.
If you want to write a blog, you'll want to register it with the PostgreSQL
blog aggregator: https://planet.postgresql.org/
Yours,
Laurenz Albe
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-novice@postgresql.org
Cc: laurenz.albe@cybertec.at, yaten598@gmail.com, pgsql-novice@lists.postgresql.org
Subject: Re: Interested in contributing to PostgreSQL documentation and technical writing
In-Reply-To: <62a535e8a3779e37060ca7862d2d5dabe654b049.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox