MIME-Version: 1.0
From: Ryan Booz <ryan@softwareandbooz.com>
Date: Mon, 7 Mar 2022 16:55:38 -0500
Message-ID: 
 <CAMjhCZoJgzichet_8USoQGsQmKdZ8ynVAXjwW0un+rXBkyvyTw@mail.gmail.com>
Subject: PGConf NYC Keynote - Community Initiatives
To: pgsql-advocacy@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000062b8e505d9a7ed1d"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMjhCZoJgzichet_8USoQGsQmKdZ8ynVAXjwW0un%2BrXBkyvyTw%40mail.gmail.com>
Precedence: bulk

--00000000000062b8e505d9a7ed1d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello everyone!

Over the last year or so, I=E2=80=99ve had the pleasure of having a number =
of
conversations and interactions with Andreas Scherbaum, Alicja Kucharczyk,
Robert Treat, Pat Wright and others about how to grow the overall Postgres
community at a more grass roots level. Many of my thoughts (or
frustrations) were largely due to my previous experience with the SQL
Server community and some of the community building initiatives they have
undertaken for many years.

Fortunately my community has grown within the Postgres world (largely due
to my work with Timescale) and this has helped me see the vibrant,
world-wide Postgres community. Still, I continue to find that many users
that are trying to enter the Postgres community from different
communities struggle with similar issues.

Some of my initial thoughts on how to tackle this problem were presented in
a PGConf NYC keynote (
https://www.youtube.com/watch?v=3D4Ot_uoDgeUE&list=3DPLiT-kUSX8USVDO_StcVoE=
rex-l-pVvrvv&index=3D3).
To my surprise, many people approached me afterwards that had similar
experiences... some of which were attending PGConf after starting their
first Postgres job weeks before!

Andreas continued the conversation in the PostgreSQL Slack #pg-promotion
channel and we discussed a number of ideas, from live webinars that would
compare/contrast various databases with Postgres, to more community focused
initiatives like a monthly =E2=80=9Cblog fest=E2=80=9D (called PSQL Phriday=
) on a common
topic, as well as getting a coordinated effort behind a #pghelp hashtag on
Twitter.

In another week, I plan to release a personal blog post discussing these
two initiatives and announcing the beginning of PSQL Phriday with a list of
hosts for the first few months. Any further ideas or discussion would be
easiest in the PostgreSQL Slack room mentioned above, but I=E2=80=99m happy=
 to
answer them here as well (I=E2=80=99m slower to respond to email to be tran=
sparent.
:-)

Overview of the initiatives below.

*PSQL Phriday*

A monthly =E2=80=9Cblog fest=E2=80=9D that can be hosted by anyone in the c=
ommunity. The
goal is to encourage more community blog involvement by providing a common
theme each month and getting traffic to blogs by having a central =E2=80=9C=
roundup=E2=80=9D
of all blog submissions by the host each month. We=E2=80=99ll try it for 6 =
months
and then re-evaluate.

By the first Friday of each month, the host for that month will post the
topic to Twitter and through their Planet Postgres blog feed. On the second
Friday of each month, anyone that wants to take part can share a post (also
with the #PSQLPhriday hashtag on Twitter). The job of the host is to
aggregate all of the links and give a 1-2 sentence synopsis of the post and
share it within a few days.

The next month, we repeat with a new host and a topic of their choice.
Topics can be technical or not, it just has to be focused somehow around
Postgres and the larger community. (sample ideas: best HA story, how you
use indexes effectively, last time you had to recover from a mistake,
coolest Postgres SQL trick, conference talk that had the most impact in
your career, etc.).

Again, the goal is participation (help new community members feel/be
integrated) and to allow other people to host that aren=E2=80=99t always th=
e =E2=80=9Cbig
names=E2=80=9D. Hopefully we end up with no repeat hosts for 2-3 years!)

*#pghelp Twitter Hashtag*

This one might feel a bit old or out of sync with so many of the other
communication avenues people have access to. And yet, Twitter remains a
place where tons of people are seeking help for Postgres related issues.
Robert Treat has tried to handle this himself for years by sometimes taking
replies with #pghelp, but it=E2=80=99s never really taken off because other=
s aren=E2=80=99t
doing the same.

The main tenet of a hashtag like this is that nobody is required to answer.
And, while we could try to =E2=80=9Cguard=E2=80=9D the hashtag from other u=
ses (advertisers
love to latch on to successful hashtags), the overall goal is to at least
get a first response or conversation on a problem. The hope, however, is
that the first interaction is always =E2=80=9Caggressively welcoming=E2=80=
=9D. It=E2=80=99s a place
to help and direct, not have the loudest voice. If the Slack channel is a
better place to get help, kindly direct them. If the person that can best
answer this question only uses the email lists, direct them there. =E2=80=
=9CRTM=E2=80=9D
isn=E2=80=99t the stock answer, but it=E2=80=99s fine to direct to relevant=
 documentation.
;-)


I hope some of you will take part, and again, happy to answer questions and
have more discussion in the #pg-promotion channel in Slack.

Kind Regards,

Ryan Booz
Developer Advocate at Timescale

--00000000000062b8e505d9a7ed1d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>Hello everyone!</p><p>Over the last year or so, I=E2=80=
=99ve had the pleasure of having a number of conversations and interactions=
 with Andreas Scherbaum, Alicja Kucharczyk, Robert Treat, Pat Wright and ot=
hers about how to grow the overall Postgres community at a more grass roots=
 level. Many of my thoughts (or frustrations) were largely due to my previo=
us experience with the SQL Server community and some of the community build=
ing initiatives they have undertaken for many years.<br></p>
<p>Fortunately my community has grown within the Postgres world (largely du=
e to my work with Timescale) and this has helped me see the vibrant, world-=
wide Postgres community. Still, I continue to find that many users that are=
 trying to enter the Postgres community from different communities=C2=A0str=
uggle with similar issues.</p>
<p>Some of my initial thoughts on how to tackle this problem were presented=
 in a PGConf NYC keynote (<a href=3D"https://www.youtube.com/watch?v=3D4Ot_=
uoDgeUE&amp;list=3DPLiT-kUSX8USVDO_StcVoErex-l-pVvrvv&amp;index=3D3" target=
=3D"_blank">https://www.youtube.com/watch?v=3D4Ot_uoDgeUE&amp;list=3DPLiT-k=
USX8USVDO_StcVoErex-l-pVvrvv&amp;index=3D3</a>). To my surprise, many peopl=
e approached me afterwards that had similar experiences... some of which we=
re attending PGConf after starting their first Postgres job weeks before!</=
p>
<p>Andreas continued the conversation in the PostgreSQL Slack #pg-promotion=
 channel and we discussed a number of ideas, from live webinars that would =
compare/contrast various databases with Postgres, to more community focused=
 initiatives like a monthly =E2=80=9Cblog fest=E2=80=9D (called PSQL Phrida=
y) on a common topic, as well as getting a coordinated effort behind a #pgh=
elp hashtag on Twitter.</p>
<p>In another week, I plan to release a personal blog post discussing these=
 two initiatives and announcing the beginning of PSQL Phriday with a list o=
f hosts for the first few months. Any further ideas or discussion would be =
easiest in the PostgreSQL Slack room mentioned above, but I=E2=80=99m happy=
 to answer them here as well (I=E2=80=99m slower to respond to email to be =
transparent. :-)</p>
<p>Overview of the initiatives below.</p>
<p><strong>PSQL Phriday</strong></p>
<p>A monthly =E2=80=9Cblog fest=E2=80=9D that can be hosted by anyone in th=
e community. The goal is to encourage more community blog involvement by pr=
oviding a common theme each month and getting traffic to blogs by having a =
central =E2=80=9Croundup=E2=80=9D of all blog submissions by the host each =
month. We=E2=80=99ll try it for 6 months and then re-evaluate.</p>
<p>By the first Friday of each month, the host for that month will post the=
 topic to Twitter and through their Planet Postgres blog feed. On the secon=
d Friday of each month, anyone that wants to take part can share a post (al=
so with the #PSQLPhriday hashtag on Twitter). The job of the host is to agg=
regate all of the links and give a 1-2 sentence synopsis of the post and sh=
are it within a few days.</p>
<p>The next month, we repeat with a new host and a topic of their choice. T=
opics can be technical or not, it just has to be focused somehow around Pos=
tgres and the larger community. (sample ideas: best HA story, how you use i=
ndexes effectively, last time you had to recover from a mistake, coolest Po=
stgres SQL trick, conference talk that had the most impact in your career, =
etc.).</p>
<p>Again, the goal is participation (help new community members feel/be int=
egrated) and to allow other people to host that aren=E2=80=99t always the =
=E2=80=9Cbig names=E2=80=9D. Hopefully we end up with no repeat hosts for 2=
-3 years!)</p>
<p><strong>#pghelp Twitter Hashtag</strong></p>
<p>This one might feel a bit old or out of sync with so many of the other c=
ommunication avenues people have access to. And yet, Twitter remains a plac=
e where tons of people are seeking help for Postgres related issues. Robert=
 Treat has tried to handle this himself for years by sometimes taking repli=
es with #pghelp, but it=E2=80=99s never really taken off because others are=
n=E2=80=99t doing the same.</p>
<p>The main tenet of a hashtag like this is that nobody is required to answ=
er. And, while we could try to =E2=80=9Cguard=E2=80=9D the hashtag from oth=
er uses (advertisers love to latch on to successful hashtags), the overall =
goal is to at least get a first response or conversation on a problem. The =
hope, however, is that the first interaction is always =E2=80=9Caggressivel=
y welcoming=E2=80=9D. It=E2=80=99s a place to help and direct, not have the=
 loudest voice. If the Slack channel is a better place to get help, kindly =
direct them. If the person that can best answer this question only uses the=
 email lists, direct them there. =E2=80=9CRTM=E2=80=9D isn=E2=80=99t the st=
ock answer, but it=E2=80=99s fine to direct to relevant documentation. ;-)<=
/p><p><br></p><p>I hope some of you will take part, and again, happy to ans=
wer questions and have more discussion in the #pg-promotion channel in Slac=
k.</p><p>Kind Regards,</p><p>Ryan Booz<br>Developer Advocate at Timescale</=
p></div>

--00000000000062b8e505d9a7ed1d--