| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "grant(at)scarydba(dot)com" <grant(at)scarydba(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Volunteering |
| Date: | 2025-12-12 20:07:18 |
| Message-ID: | a5a397c34806089239c82194b54f909996104e5c.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, 2025-12-12 at 15:47 +0000, grant(at)scarydba(dot)com 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daisuke Higuchi | 2025-12-13 08:24:48 | doc: Fix the header file where CompareType is defined in gist.sgml |
| Previous Message | grant@scarydba.com | 2025-12-12 15:47:33 | Volunteering |