public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected] <[email protected]>
To: Laurenz Albe <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Volunteering
Date: Mon, 15 Dec 2025 13:58:17 +0000
Message-ID: <DM5PR05MB3436895EE77BFC9BD9918131A0ADA@DM5PR05MB3436.namprd05.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>
References: <DM5PR05MB34363A88323A570CFAB4A796A0AEA@DM5PR05MB3436.namprd05.prod.outlook.com>
	<[email protected]>

Cheers!

Appreciate the info. I'll be reading and watching for the moment.
________________________________
From: Laurenz Albe <[email protected]>
Sent: Friday, December 12, 2025 2:07 PM
To: [email protected] <[email protected]>; [email protected] <[email protected]>
Subject: Re: Volunteering

On Fri, 2025-12-12 at 15:47 +0000, [email protected] wrote:
> My name is Grant Fritchey. I'm very interested in contributing to the PostgreSQL project.
> However, I'm just a DBA, so I won't be writing a lot of code with the Hackers.
> However, I can write, so I'd be interested in volunteering with the documentation team.
> Could someone share the general duties & needs and just how I'd go about getting involved please?

Welcome!

I'd start by reading appendix J of the documentation.
Set up a build environment for the documentation.

Even if you don't want to write source code, much of the information in
this article will still apply:
https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F

Get familiar with the commitfest app: https://commitfest.postgresql.org/
Patches that you want to be reviewed and committed should go there.
The best starting point might be to review some documentation patches
from the next commitfest.

I am not aware of a TODO list for the documentation, so if you don't
have your own ideas about improving the documentation, you can hang out
on the -docs mailing list and read the questions and complaints that
others have.

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Volunteering
  In-Reply-To: <DM5PR05MB3436895EE77BFC9BD9918131A0ADA@DM5PR05MB3436.namprd05.prod.outlook.com>

* 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