public inbox for [email protected]help / color / mirror / Atom feed
Volunteering 3+ messages / 2 participants [nested] [flat]
* Volunteering @ 2025-12-12 15:47 [email protected] <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: [email protected] @ 2025-12-12 15:47 UTC (permalink / raw) To: [email protected] <[email protected]> Hello, 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? Thanks, Grant ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Volunteering @ 2025-12-12 20:07 Laurenz Albe <[email protected]> parent: [email protected] <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Laurenz Albe @ 2025-12-12 20:07 UTC (permalink / raw) To: [email protected] <[email protected]>; [email protected] <[email protected]> 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Volunteering @ 2025-12-15 13:58 [email protected] <[email protected]> parent: Laurenz Albe <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: [email protected] @ 2025-12-15 13:58 UTC (permalink / raw) To: Laurenz Albe <[email protected]>; [email protected] <[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 ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-12-15 13:58 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-12-12 15:47 Volunteering [email protected] <[email protected]> 2025-12-12 20:07 ` Laurenz Albe <[email protected]> 2025-12-15 13:58 ` [email protected] <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox