PostgreSQL Leadership & Developer Meeting at PGConf.dev 2024

From PostgreSQL wiki
Jump to navigationJump to search

At 9:00 AM on Tuesday, May 28, 2024, at SFU Vancouver in advance of PGConf.dev, PostgreSQL community leaders and developers will meet.

This is a PostgreSQL Community event.

Meeting Goals

The goal of the meeting is to resolve outstanding technical or procedural issues that cannot easily be addressed over email, to build awareness of the current state of ongoing community projects, to build consensus on the technical and operational focus of those projects going forward, and to set PostgreSQL project priorities for the year,

During the first part of the meeting, we’ll hear presentations addressing outstanding activities, operations and governance issues from the previous year and discuss any resulting issues or concerns.

The next portion of the meeting will occur in small groups. Individuals will participate in groups discussing the topics in which they are interested. Groups will discuss proposed topics, with one group member presenting key takeaways to the larger group. The small group topics will be suggested and selected in advance.

Topics may be technical or procedural and should be something that could not easily be discussed and decided on a mailing list or in an email. An Unconference will be held on Friday for in-depth discussion of technical topics.

As in previous years, topics may include Wicked problems that we should seek to solve as a project as well as policy and procedural concerns and proposals.

We aim to either make a decision on the issue or agree upon goals for addressing the topic over the next year and actions we should take in support of doing so.

Agenda

Operations and Governance Short Presentations and Q&A (1 hour)

  • Governance Overview - Jonathan Katz
  • Core Team Overview - Tom Lane
- Short history of Core and its current responsibilities
  • Security Overview - Noah Misch
- PostgreSQL CNA and how this changes things
- Users' reactions to security news
- Interesting details about vulnerabilities patched this year
  • PgCA Updates - Steve Singer
  • Code of Conduct Committee Updates - Eliza Bennett
- 2023/2024 (to date) activities
- Future directions under consideration
  • Port Reports - Thomas Munro

Breakout Groups (1.5 hours including scheduled refreshment break)

Group Readouts (1.5 hours)

Lunch will be served at 13:00

Suggested Breakout Group Topics

The following topics have been suggested. All those who have +1'd the topic appear next to the item. Please feel free to add additional detail to the topic you have suggested or +1'd.

Topics will be selected subject to popularity and relevance.

  • Use of hardware security tokens (e.g. YubiKeys) for commits (Andres, Melanie, Magnus, Jeff, Michael P)
  • Documenting supported operating systems somewhere (Melanie)
  • State of the Windows port (Thomas M, Andrew D, Dave Cramer)
  • Revisit bug tracker (Andres, Melanie, Misch)
  • ARM support, specifically Windows ARM support (Dave Cramer)
  • Protocol changes to support drivers and clustering (Dave Cramer)
  • Feature Freeze policy changes (Robert H, Andreas, Tom Lane, Matthias)
- Try to come up with a way to avoid the following happening again in the future
- too many patches were committed at the last minute
- some of those were not really ready to be committed
- an awful lot of stuff is getting reverted
- Try to reduce impact of Feature Freeze on new feature commit cycle (Matthias)
  • Process for Future Improvements to Table Access Methods API (Alexander Korotkov, Melanie)
- Attempt to gain a broader consensus on the direction of Table AM development and avoid potential conflicts and issues post feature freeze.
  • Any interest in new TPC benchmarks: E, DS, or AI (Mark Wong, Melanie)
- Make the less costly E our primary OLTP benchmark.
- Does the DS star-schema and snowflake help existing or upcoming patches?
- Is the AI benchmark relevant to the AI hype?
- Would AppImages or other packaging make the OSDL kits easy enough to use over HammerDB, etc.?
  • Reviewing PostgreSQL exhibition efforts (Mark Wong)
- Are we covering appropriate non-PostgreSQL events?
- Should we make more effort to be at events outside of North America?
- How formal should we make our presence?
  • What to do when you need design feedback from someone and they aren't giving it (Robert, Melanie, Misch, Matthias)
  • Consider Surprising_Behavior_Roles_Privileges and ways to make progress on improvements. (Jeff)
  • On using better tools to track and address comments on code and design (IOW using review boards (e.g. Github PR) and documents (e.g. GDoc)) (Ashutosh)
  • Any action items on the commitfest improvement thread? (Melanie)

Attendees (those who RSVP'd yes)

  • Jonathan Katz
  • Bruce Momjian
  • Peter Geoghegan
  • Tom Lane
  • Steve Singer
  • Melanie Plageman
  • Jeff Davis
  • Nathan Bossart
  • Dilip Kumar
  • Devrim Gündüz
  • Michael Paquier
  • Bharath Rupireddy
  • Karen Jex
  • Bertrand Drouvot
  • Magnus Hagander
  • Matthias van de Meent
  • Heikki Linnakangas
  • Dave Cramer
  • Jelte Fennema-Nio
  • Joe Conway
  • Amit Langote
  • Amit Kapila
  • Thomas Munro
  • Masahiko Sawada
  • Dave Page
  • Stacey Haysler
  • Vik Fearing
  • Mark Wong
  • Álvaro Herrera
  • Ashutosh Bapat
  • Robert Haas
  • Tatsuo Ishii
  • Andrew Dunstan
  • Peter Eisentraut
  • Andreas Scherbaum
  • Andres Freund
  • Tomas Vondra
  • Kyotaro Horiguchi
  • Hou Zhijie
  • Paul Ramsey
  • Andrey Borodin

Organizers

  • Jonathan Katz
  • Melanie Plageman

contact AT pgconf DOT dev

Retrieved from "https://wiki.postgresql.org/index.php?title=PostgreSQL_Leadership_%26_Developer_Meeting_at_PGConf.dev_2024&oldid=39266"