Thread
-
Interested in contributing to PostgreSQL documentation and technical writing
Yaten Dhingra <yaten598@gmail.com> — 2026-03-20T11:35:39Z
Hello PostgreSQL Community, I'm Yaten <https://github.com/yaten2302>, a CS undergrad with a strong interest in databases, distributed systems, and open-source. I’ve been actively working with technologies like Go, React, and cloud-native tools, and I’m currently exploring PostgreSQL more deeply. 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. Thank you for your time! Best, Yaten
-
Re: Interested in contributing to PostgreSQL documentation and technical writing
Danjel Jungersen <danjel@jungersen.dk> — 2026-03-20T11:43:52Z
Hi there. First, I CANNOT HELP YOU! But I just wanted to say thank you for your willingness to contribute. It is people like you that make people like me able to use this software. Thanks again to you, and all the other very helpful people who have helped me in the past. Have a very nice day! All of you! Danjel On 20-03-2026 12:35, Yaten Dhingra wrote: > > Hello PostgreSQL Community, > > I'm Yaten <https://github.com/yaten2302>, a CS undergrad with a strong > interest in databases, distributed systems, and open-source. I’ve been > actively working with technologies like Go, React, and cloud-native > tools, and I’m currently exploring PostgreSQL more deeply. > > 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. > > Thank you for your time! > > Best, > Yaten > -- Med venlig hilsen/Kind regards Danjel Jungersen Mail: danjel@jungersen.dk Mobile: +45 20 42 20 11 Jungersen Grafisk ApS, Holsbjergvej 39, DK-2620 Albertslund, Denmark. Tel: +45 43 64 10 00 WEBSHOP: PRINTLIGHT.DK <https://www.printlight.dk> | WWW.JUNGERSEN.DK <https://www.jungersen.dk> Logo <https://www.jungersen.dk>
-
Re: Interested in contributing to PostgreSQL documentation and technical writing
Laurenz Albe <laurenz.albe@cybertec.at> — 2026-03-20T15:27:33Z
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
-
Re: Interested in contributing to PostgreSQL documentation and technical writing
Yaten Dhingra <yaten598@gmail.com> — 2026-03-21T19:02:47Z
On Sat, 21 Mar 2026 at 04:06, Laurenz Albe <laurenz.albe@cybertec.at> wrote: > There are always more people who want to write something than people who > want to review others' patches, so reviews by beginners are most welcome. I'll surely try to review some docs PRs and discuss in the mailing list in case of any doubt. > You are free to write what you want, as long as you follow the "posting > policy" prominently linked on the web page. Got this, will surely check this out! > > (I've tagged "laurenz.albe@cybertec.at" in this mail, correct me > > if I was supposed to tag "pgsql-novice@lists.postgresql.org"?) > > I'm correcting you - never reply privately, always keep discussions > on the list (unless you have something private or clearly off-topic > to say). It's ok, you are new, I understand. Got this. Thanks!