Re: Advanced Patch Feedback Session / pgconf.dev 2025 - Mailing list pgsql-hackers
From | Tomas Vondra |
---|---|
Subject | Re: Advanced Patch Feedback Session / pgconf.dev 2025 |
Date | |
Msg-id | 125cc09d-4fcd-4701-8dfa-c5a185eb5eee@vondra.me Whole thread Raw |
In response to | Advanced Patch Feedback Session / pgconf.dev 2025 (Tomas Vondra <tomas@vondra.me>) |
List | pgsql-hackers |
Hi, I'd like to remind people planning to attend pgconf.dev the registration for Advanced Patch Feedback Session closes on Friday (in ~2 days). If you're interested in participating (as a contributor or a committer), please sign up using the forms linked in the announcement. kind regards Tomas On 3/13/25 17:37, Tomas Vondra wrote: > Hi all, > > pgconf.dev 2025 will host "Advanced Patch Feedback Session", with the > same format as in 2024 [1]: > > Participants will work in small groups with a Postgres committer to > analyze a past contribution or attempted contribution, discussing > what they could have done better both in the patch and communication > about the patch. Applications are now closed and applicants have been > notified. > > Per the schedule [2], the APFS is on Tuesday, May 13, 14:00 - 17:30. The > APFS session is organized by me, Robert Haas and Amit Kapila. > > [1]: > https://www.pgevents.ca/events/pgconfdev2024/schedule/session/224-advanced-patch-feedback-session-invite-only/ > > [2]: https://2025.pgconf.dev/schedule.html > > > At this point we're looking for those who would like to participate in > this session, and get feedback for some of their patches. > > The session would be similar to [1] in that we construct groups each > containing one or more committer volunteers and several non-committer > contributors who have patches about which they want feedback. The > committers look at the patches from the non-committers in their group > in advance of the session, and then give whatever feedback they have. > This can be about technical details of the patches, general technical > matters, or tactical/communication aspects. > > We strongly recommend non-committers to also review each other's patches > in a similar manner, so that they can benefit from feedback given to > other members of the group, or (even better) to participate in the > discussion and share their feedback. > > All this can be for long-term general education but also for short-term > tactical purposes, depending on what the group thinks is beneficial. > > > If you'd like to participate in this session as either a patch author > who wants their patch reviewed or as a reviewer/committer/group > leader, please use one of these forms to register: > > - patch author: > > https://docs.google.com/forms/d/1DqXh5k6kp2ksVmbMOFkw8lybCNRMsGAsjP7PSTM52YA > > - committer: > > https://docs.google.com/forms/d/1aEyvHErVZsy-QJRTsYtyxlz3mp1q9Vh7wa2g-PXpSsw > > If applying as a patch author, please also include a commitfest link > or two about what patches you have pending and would like to focus on. > To be considered, a patch should have some nontrivial level of size or > complexity or difficulty so that it's worth having a meeting about it. > If you have specific questions / areas for feedback, please describe > those in the patch comment. > > If you have any logistical caveats, like you are still waiting for > travel approval, please include that. Beyond those kinds of things, > please don't sign up unless you really can and want to come and make > your own way there. It would be very wasteful and disappointing if a > bunch of people signed up and then didn't show up. > > Given that pgconf.dev is just about 8 weeks away, we would like to get > this first round of feedback in the next 2 weeks (by Friday, March 28), > so that we can proceed with further steps (forming groups, etc.) > > If needed, feel free to ask question - either here, or get in touch > directly with either of the organizers (me, Robert or Amit). > > > kind regards > > -- > Tomas Vondra > > -- Tomas Vondra
pgsql-hackers by date:
Previous
From: m.litsarev@postgrespro.ruDate:
Subject: Re: SQL function which allows to distinguish a server being in point in time recovery mode and an ordinary replica
Next
From: "Euler Taveira"Date:
Subject: Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.