Will Postgres development rely on mailing lists forever?
Postgres development relies on mailing lists, which may deter new contributors. The author suggests gradual improvements and a federated approach to better integrate modern practices without a complete overhaul.
Read original article
Postgres, an open-source database project established in 1996, continues to rely on mailing lists for its development process, a method that may seem outdated compared to modern practices like pull requests used by newer projects. The author, Tomas Vondra, discusses the challenges faced by new contributors unfamiliar with this traditional process, which can be perceived as arcane. While mailing lists were once the standard for open-source collaboration, the emergence of platforms like GitHub has shifted many projects away from this model. Vondra expresses skepticism about the effectiveness of pull requests for complex patches, citing difficulties in tracking discussions and reviews. He highlights that the current reliance on mailing lists may hinder new contributors, as they struggle to navigate the existing workflow. Despite the challenges, Vondra believes that a complete transition to pull requests is unlikely in the near future. Instead, he anticipates gradual improvements to the existing process, including better integration of tools and simplification of workflows. He also suggests exploring alternative methods, such as a federated approach to handle pull requests from new contributors, which could help bridge the gap between traditional and modern development practices.
- Postgres development still relies on mailing lists, which may deter new contributors.
- The author is skeptical about the effectiveness of pull requests for complex patches.
- Gradual improvements to the existing mailing list process are expected rather than a complete overhaul.
- There is a need for better integration and simplification of development tools.
- A potential federated approach could help manage contributions from new developers.
Related
Just Use Postgres for Everything
The article promotes using Postgres extensively in tech stacks to simplify development, improve scalability, and reduce operational complexity. By replacing various technologies with Postgres, developers can enhance productivity, focus on customer value, and potentially cut costs.
Just Use Postgres for Everything
The blog post advocates for using PostgreSQL extensively in tech stacks to simplify development, improve productivity, and reduce complexity. It highlights benefits like scalability, efficiency, and cost-effectiveness, promoting a consolidated approach.
Pull Requests via Git Push
Steinar H. Gunderson introduced a new method on git.sesse.net, enabling pull requests via git push through email. This simplifies patch submissions, despite limitations like no multipush support and potential errors. Security measures are highlighted.
Major Developments in Postgres Extension Discovery and Distribution
The article covers advancements in Postgres extension discovery and distribution. Postgres extensions enhance database capabilities with features like query hints and encryption. PGXN facilitates extension access. A summit in Vancouver will address extension challenges, encouraging developer involvement for ecosystem enhancement.
Difference between running Postgres for yourself and for others
The post compares self-managed PostgreSQL with managing it for others, focusing on provisioning, backup/restore, HA, and security. It addresses complexities in provisioning, backup strategies, HA setup, and security measures for external users.
0 commentsRelated
Just Use Postgres for Everything
The article promotes using Postgres extensively in tech stacks to simplify development, improve scalability, and reduce operational complexity. By replacing various technologies with Postgres, developers can enhance productivity, focus on customer value, and potentially cut costs.
Just Use Postgres for Everything
The blog post advocates for using PostgreSQL extensively in tech stacks to simplify development, improve productivity, and reduce complexity. It highlights benefits like scalability, efficiency, and cost-effectiveness, promoting a consolidated approach.
Pull Requests via Git Push
Steinar H. Gunderson introduced a new method on git.sesse.net, enabling pull requests via git push through email. This simplifies patch submissions, despite limitations like no multipush support and potential errors. Security measures are highlighted.
Major Developments in Postgres Extension Discovery and Distribution
The article covers advancements in Postgres extension discovery and distribution. Postgres extensions enhance database capabilities with features like query hints and encryption. PGXN facilitates extension access. A summit in Vancouver will address extension challenges, encouraging developer involvement for ecosystem enhancement.
Difference between running Postgres for yourself and for others
The post compares self-managed PostgreSQL with managing it for others, focusing on provisioning, backup/restore, HA, and security. It addresses complexities in provisioning, backup strategies, HA setup, and security measures for external users.