Postgres Conference (PostgresConf) prides itself on the quality of our community and our work, and the technical and professional accomplishments of our community. We expect everyone who participates to conduct themselves in a professional manner, acting with common courtesy and in the common interest, with respect for all of our community.
It is the expectation that PostgresConf community members will adhere to the PostgresConf Code of Conduct (CoC).
Inclusivity and Appropriate Conduct
PostgresConf is open to participation by anyone with an interest in working with Postgres and related technologies, regardless of their level of experience with the software, or with technology in general. We encourage contributions from all individuals, whatever their background may be.
Personal attacks and negative comments on personal characteristics are unacceptable, and will not be permitted. Examples of personal characteristics include, but are not limited to age, race, national origin or ancestry, religion, political affiliation, gender, or sexual orientation.
Additional behaviors which are also violations of this CoC include, but are not limited to, threats of violence against an individual or group, threats of professional, community, and/or project sabotage, unwelcome sexual attention in any form, engaging in behavior that may bring PostgresConf into disrepute, and refusing to cease inappropriate conduct when requested to do so.
It is also expressly forbidden for anyone to retaliate against a person who brings a complaint under this CoC, or who assists in investigating such a complaint. Retaliation may take the form of, among other actions:
further personal attacks (public or private);
actions which undermine an individual's professional status and/or status with their employer, coworkers, clients, or community;
actions which threaten the individual's privacy, physical person, well-being, home, and/or family.
Acts of retaliation will be treated in the same manner as any other violation of this CoC.
If you are the recipient of inappropriate behavior, please email firstname.lastname@example.org. In the unfortunate event that you wish to make a complaint against some member of the PostgresConf CoC committee, then you may instead contact any of the other Committee member(s) individually and the subject of the complaint will be recused from any decision surrounding the complaint.
In your report, please include as much detail as possible:
a description of the incident;
the timing of events;
screen shots of any electronic discussions;
names, and if possible, contact information for any witnesses; and,
any other information which you think would be helpful in the investigation.
Handling of Complaints
The PostgresConf CoC Committee will promptly acknowledge and investigate each reported incident. With the cooperation of all parties, the Committee will aim to complete the investigation in a period of two weeks from the receipt of the complaint.
Incident reports and investigation activities will be kept confidential to the extent possible, consistent with the need to conduct an adequate investigation.
Acting in Good Faith
Any allegations that prove not to be substantiated, and which prove to have been made maliciously or knowingly to be false, will be viewed as a serious community offense and a violation of this CoC.
We encourage appropriate and collegial relationships among community members; however, members must be sensitive to conduct that may be considered offensive by fellow members and must refrain from engaging in such conduct.
In all interactions with the community, use your professional judgment, and keep the discussion focused on moving our project and our community forward in a positive direction for all.
PostgresConf US 2019 is a non-profit, community driven conference delivering the largest education and advocacy platform for Postgres. In an effort to create a productive and profitable environment for our community we must set a bar of expectation for content and we set the bar high.
The community is comprised of users, developers, core-contributors, sponsors, advocates, and external communities. We work hard to create a professional, valuable, and highly educational environment that produces a net result of, “Wow, that conference was very well done. It had great content with knowledgeable professionals, educators and advocates!”
Types of Presentations We Accept
Any presentation that has a tie-in to Postgres will be considered for acceptance into one of our event programs. This includes, but is not limited to, presentations on Open Source Projects, Postgres forks, extensions, new APIs, and languages. As a conference that makes it a goal to incorporate the entire community we also consider business cases, product talks, and service presentations. Presentations that are not related to the success of Postgres will not be considered.
Laptop connections supported
PostgresConf will provide a VGA and HDMI connection. If you do not have a VGA or HDMI port it is the speaker’s responsibility to provide an adapter.
What about X technology?
When considering whether to submit a topic or not, ask yourself, “Is this presentation in some way related to the success of Postgres?” If it is, then it will be considered. This includes limitations of our great database. It also includes forks of Postgres both closed and Open Source. These types projects and products ultimately contribute to the success of Postgres.
How do presentations on forks or closed source versions help the success of Postgres?
Postgres is BSD style licensed. The BSD license is a true freedom license. The only license that maintains a higher level of freedom for Open Source development is the anti-license: Public Domain. That means the community embraces all forms of use for Postgres as long as it abides by the license.
A presentation on RDS Postgres, Google Cloud Postgres or Greenplum increases overall success via visibility, lowers the barrier of entry for new Postgres users, and supports our commercial community with hard earned efforts to create Postgres products.
Shouldn’t the community be promoting Open Source solutions over proprietary closed source solutions?
Yes, the end goal is that the deployed Postgres is the Open Source Postgres and preference will always be given to Open Source Postgres presentations. However, we offer presentation opportunities to our sponsors that may or may not advocate Open Source Postgres. Sponsors are welcome to present on any topic as long as it follows the guideline of: Does it promote the success of Postgres?
Types of Presentations
PostgresConf offers several presentation opportunities:
Presentation: 20 minutes
Breakout Sessions: 50 minutes
Keynotes: 10 and 20 minutes
Half Day, Full Day and Two day trainings (NOTE: These must be purchased separately from the general conference admission)
Why are Trainings and Tutorials not included with general admission?
At PostgresConf we bring the highest quality content to our community. For trainings that means enlisting the help of professional trainers/consultants. These professionals are compensated for their valuable time by the extra training financial contribution.
If you must cancel for any reason you must notify us in writing by March 4, 2019 to receive a refund minus the $25 cancellation fee. Please contact us via email at email@example.com. Cancellations within 14 days of the event are non-refundable. You may transfer your registration to another person through the conference website. Confirmed and paid attendees who do not attend or who cancel after the deadline are liable for the entire fee. In the unlikely event of cancellation of the conference, the liability of PostgresConf is limited to the return of paid registration fees.
This tool is
released under the
You can run, copy, distribute, study, change and improve it.
The source code and the developers are on