Re: Volunteering

2025-12-15 Thread [email protected]
Cheers!

Appreciate the info. I'll be reading and watching for the moment.

From: Laurenz Albe 
Sent: Friday, December 12, 2025 2:07 PM
To: [email protected] ; [email protected] 

Subject: Re: Volunteering

On Fri, 2025-12-12 at 15:47 +, [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




Re: doc: Fix the header file where CompareType is defined in gist.sgml

2025-12-15 Thread Paul A Jungwirth
On Sat, Dec 13, 2025 at 12:25 AM Daisuke Higuchi
 wrote:
>
> I found that the header file where CompareType was actually defined did not 
> match the header file described in gist.sgml.
> CompareType is currently defined at "src/include/access/cmptype.h" instead of 
> "src/include/nodes/primnodes.h".
> This change was made in the commit below, but it seems that documentation 
> update was missed.
>
> https://github.com/postgres/postgres/commit/119fc30dd5bd918819b864107ddc8baac51f4d22

You're right, that's where we define it. Your email landed in Gmail's
spam folder for me, so hopefully this +1 will help it not be missed by
a committer.

Yours,

-- 
Paul  ~{:-)
[email protected]