Community,
With 2020 firmly in the rear view mirror, it is time to look forward and down the highway of 2021. The organizers of People, Postgres, Data have gathered over chat, email, phone, and even a few socially distant, in-person events to determine a strategy for continuing as the most influential and positive community for all things Postgres related.
Sad face
The goal is to resume in-person events. However, out of concern for the health and comfort of our global community, we have made the decision not to host any in-person events until Q4 of 2021. We are prepared to wait until 2022 if that is what the health officials recommend. We know that many will find this news disappointing and we are working diligently to ensure that the health and education of our community is the top priority.
Happy face
We are continuing our popular webinar series, adding new presenters with pertinent content for all of our attendees. We will be adding more professional development and data problem solving topics to our library, and we will no longer be limiting education to just Postgres, as many data and human problems are neutral in the particular platform we happen to enjoy. If there’s a topic you’d like to present or see, we’d love to hear from you!
Ecstasy
Postgres Conference 2021: Digital will be happening in May of this year! An overwhelming feeling of great happiness and excitement has our dopamine pumping, and the whole People, Postgres, Data team is basking in it.
As an all digital conference, we will offer a similar environment to what our community has come to expect: best in class content, professionalism, and top-tier educational opportunities for all who attend! Keep your eyes peeled over the next few weeks for more information on speaking opportunities and how to attend!
 |
| Mastering Postgres Administration: Bruce Momjian |
We are having yet another PGConf Mini in NYC. The event is scheduled for December 14th, 2017 and Work Bench is hosting:
Efficiently and Safely Propagate Data Changes Without Triggers!
PgConf US 2017 has now completed. We had a record number of attendees, a record number of sponsors and a record number of talks. The conference rocked. It was only made possible by a team of highly talented and dedicated volunteers. Thank you to those volunteers.
 |
| Members of the South African Community |
 |
| Thank you to our speakers |
 |
| Thank you to our sponsors |
With the pending GA release of Star Link, more cities adopting municipal WIFI, and the growth of remote work due to the pandemic, one would assume that cell phone providers would be falling hand over fist to provide quality services at a quality price. Unfortunately this is not the case and it is hurting the future of our workforce.
Carriers currently think that 30GB of Hotspot data is enough for the average digital nomad. While that may have been the case previously, it isn’t any longer. There is a hundreds-of-thousands-strong workforce specializing in Information Technology, Digital Design, Web Development, and other creative industries. They are living, working and adventuring in RVs, Sprinters, Skooolies (pictured), and other vehicle dwelling options. This community is nomadic by design and should not be artificially limited by technology.
Why is it that we are being charged so much money for so little? Outside of two providers announcing rural initiatives, we are still acting like data needs are small and that they come at a quality price. Data is ubiquitous; it is the new water (for getting work done). In the new economy workers need faster, higher quality, and unlimited amounts of data to get their job done.
Where could you go and what could you experience if you weren’t tethered by the faux limitations of bandwidth?
As one of the Founders of United States PostgreSQL, a former Director of Software in the Public Interest (one of the NPOs behind Postgresql.org), a former committer (web), former major contributor, President of the oldest PostgreSQL company still independent in North America, and the Founder of Postgres Conference (in the U.S.), I thought I would offer a knowledgeable perspective.
I have had long discussions with one of the primary people within the Fundacion PostgreSQL (Alvaro) and his heart is in the best interest of the community, even if Postgresql.org, PGEU and PGCAC do not agree. You can see this demonstrated within Fundacion’s trademark policy. That said, Fundacion PostgreSQL did go about their actions in an incorrect way. There should have been an open discussion and they should have provided PGCAC the opportunity to resolve the trademark issues on their own. It is also true that while I believe PGEU and PGCAC believe they are protecting the community, if they were interested in positive community growth and collaboration, they would not be taking the approach they currently are. The current path has far reaching implications that PGEU and PGCAC do not see.
Further, the PostgreSQL Community Association of Canada and Fundacion PostgreSQL have resorted to terrible language in representing what is actually going on within the disagreement. Using language such as, “An attack on our community” or “PostgreSQL attacks the community” is immature at best and at worst an intentional decision to use good faith and mindshare against what is largely just a disagreement that could be solved with an active mediator and a few phone calls. If this disagreement is about the best interest of the PostgreSQL community, shouldn’t that involve discourse, honesty, transparency, and kind communication?
(1) Internet consulting.
(2) Internet presence provider- DNS hosting.
(3) Commercial internet support for database applications development and implementation including the ability to host internet domains (as an internet service provider) and provide a wide range of web site development, programming and information technology services, namely computer software architecture, design and/or development services.
(4) Computer hardware sales and service.
The solution to the whole problem is simple; a single contract that states:
The contract should not contain language in regards to future potential filings that involve but are not exclusive to the word Postgres or PostgreSQL. There are already a number of filings worldwide that use Postgres or PostgreSQL as part of an overall mark inclusively such as Postgres Pro, Postgres Plus, Postgres Always On and Postgres Enterprise Manager, all of which are not owned but PGCAC or PGEU.
Because it is the right thing to do. Otherwise this whole affair is going to end up costing one entity or another way too much money for no purpose. There is no clear distinction on who would legally win, and in either situation the main sufferers are the PostgreSQL community. Let’s have the parties show an act of kindness for the betterment of everyone involved.