# Postgres - the non-code bits

DevFeed: [Postgres - the non-code bits](<https://devfeed.tech/articles/postgres-the-non-code-bits-41202.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2017/10/31/Postgres-the-non-code-bits/>)

Author: Map

Published: 2017-10-31T20:55:56Z

Content type: article

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Databases](<https://devfeed.tech/topics/databases.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [databases](<https://devfeed.tech/tags/databases.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [software](<https://devfeed.tech/tags/software.md>)

## AI overview

An overview of PostgreSQL's distinctive license and community structure. The article explains what the license permits, how logo use is restricted, and how the core team, committers, and contributors support project governance and releases.

## Source excerpt

Postgres is an interesting open source project. It's truly one of a kind, it has its own license to prove it as opposed to falling under something like Apache or GPL. The Postgres community structure is something that is pretty well defined if you're involved in the community, but to those outside it's likely a little less clear. In case you're curious to learn more about the community here's a rundown of a few various aspects of it: PostgreSQL License Let's start with the legal part first. First IANAL. PostgreSQL is under its own license. For those who don't regularly follow software licensing it's extremely liberal and flexible. You can take Postgres, fork it, change it, package it up, and resell it. This is actually one of the reasons you see Postgres at the core of so many other databases like Par Accel, Asterdata, etc. That and that it's such a solid code base that is capable of being extended. I once heard someone describe how they don't really like writing C, but they enjoy writing Postgres C ;) A thing you can't do is profit off the PostgreSQL logo without any approval from the core team. The people Within the Postgres community there are 2 major sets of people. The core team The core team is a smaller team within the Postgres community. The core team is effectively a steering committee for Postgres. They're responsible for coordinating releases, handling confidential issues (read: security issues), managing permissions around PostgreSQL code and infrastructure, defining policy. The core team is a very small list of people, at the moment 5 individuals. Contributors Yes, anyone can contribute to Postgres, and with each release there are a laundry of people that write some code that goes into Postgres. If fact Postgres 10 had 325 people that contributed in some form. That said there is a hierarchy that exists. The two biggest ones are committers and major contributors. Committers gain access after years of contributing to Postgres showing sustained commitment