MIME-Version: 1.0
From: Cornelia Biacsics <cornelia.biacsics@gmail.com>
Date: Tue, 2 Dec 2025 17:27:20 +0100
Message-ID: 
 <CAN_SPgpnvhZzUjXJ_u4h7bYT_9=N8RO1AytA7_T--4pScpeU_g@mail.gmail.com>
Subject: Non-Compete Challenges for Community Work
To: pgsql-advocacy@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000086304f0644fa929e"
Archived-At: 
 <https://www.postgresql.org/message-id/CAN_SPgpnvhZzUjXJ_u4h7bYT_9%3DN8RO1AytA7_T--4pScpeU_g%40mail.gmail.com>
Precedence: bulk

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

Dear Community,

I would like to raise a general challenge that could affect contributors in
the PostgreSQL ecosystem (in the future).

Broad non-compete clauses in employment contracts =E2=80=94 regardless of w=
hether
they would hold up in court =E2=80=94 may temporarily prevent people from
continuing their work in the database industry.

This could potentially interrupt ongoing community contributions and reduce
continuity.

Before exploring either path further, I would like to understand whether
there is actual demand or interest in addressing this challenge
collectively.


   1. Do you see this as an issue the PostgreSQL community should discuss?
   2. Would either of these options be valuable for community health and
   sustainability?
   3. Is there support for forming a small working group to evaluate
   feasibility and governance?

If there is interest, I see two possible directions:
*1. Community Support & Retention Fund*

A fund to offer temporary financial support or non-commercial project work
for contributors who may be restricted from working within the PostgreSQL
ecosystem due to broad non-compete clauses.
During such a period, these contributors would work exclusively for the
community, focusing on non-commercial tasks aligned with PostgreSQL=E2=80=
=99s
values and needs.
*2. Community Recognition for PostgreSQL Community-Friendly Companies*

Extending the existing community recognition model (used for meetups and
conferences) to organizations. Companies could voluntarily follow
community-aligned guidelines (based on general & expanded CoC guidelines)=
=E2=80=94
including avoiding restrictive industry-wide non-compete clauses =E2=80=94 =
and be
recognized as community-friendly employers within the ecosystem.

I look forward to your thoughts and perspectives =E2=80=94 publicly or priv=
ately =E2=80=94
and appreciate your openness in discussing what can be a sensitive but
important topic.

Thanks a lot and best wishes

Cornelia Biacsics

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

<div dir=3D"ltr"><p>Dear Community,</p>
<p>I would like to raise a general challenge that could affect contributors=
 in the PostgreSQL ecosystem (in the future).=C2=A0</p><p>Broad non-compete=
 clauses in employment contracts =E2=80=94 regardless of whether they would=
 hold up in court =E2=80=94 may temporarily prevent people from continuing =
their work in the database industry.</p><p>
This could potentially interrupt ongoing community contributions and reduce=
 continuity.</p>
<p>Before exploring either path further, I would like to understand whether=
 there is actual demand or interest in addressing this challenge collective=
ly.</p><p></p><ol><li>Do you see this as an issue the PostgreSQL community =
should discuss?</li><li>Would either of these options be valuable for commu=
nity health and sustainability?</li><li>Is there support for forming a smal=
l working group to evaluate feasibility and governance?</li></ol><p></p>
<p>If there is interest, I see two possible directions:</p>
<h3><strong>1. Community Support &amp; Retention Fund</strong></h3>
<p>A fund to offer temporary financial support or non-commercial project wo=
rk for contributors who may be restricted from working within the PostgreSQ=
L ecosystem due to broad non-compete clauses.<br>
During such a period, these contributors would work exclusively for the com=
munity, focusing on non-commercial tasks aligned with PostgreSQL=E2=80=99s =
values and needs.</p>
<h3><strong>2. Community Recognition for PostgreSQL Community-Friendly Comp=
anies</strong></h3>
<p>Extending the existing community recognition model (used for meetups and=
 conferences) to organizations. Companies could voluntarily follow communit=
y-aligned guidelines (based on general &amp; expanded CoC guidelines)=E2=80=
=94 including avoiding restrictive industry-wide non-compete clauses =E2=80=
=94 and be recognized as community-friendly employers within the ecosystem.=
</p>
<p>I look forward to your thoughts and perspectives =E2=80=94 publicly or p=
rivately =E2=80=94 and appreciate your openness in discussing what can be a=
 sensitive but important topic.</p>
<p>Thanks a lot and best wishes</p><p>Cornelia Biacsics</p></div>

--00000000000086304f0644fa929e--