We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

How to get a feature committed?

Formal Metadata

Title
How to get a feature committed?
Subtitle
Community rocks
Title of Series
Number of Parts
35
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
PostgreSQL is unique in its way of handling incoming patches and feature proposals with its commit fest system, and getting a feature accepted or rejected can be hard to accept for newcomers which perhaps do not have a lot of insight about how the community works. This presentation covers the process community uses to handle patches and how the development of PostgreSQL happens, from the tools in place to the set of implicit rules used by seasoned hackers. With this presentation, any newcomer to the community will get a good insight of how to work with other members, getting at the end potentially something committed. Because at the end, investing in PostgreSQL takes a certain initial investment but the long-term prospects are excellent for anything depending on PostgreSQL.