MIME-Version: 1.0
References: 
 <CAN_SPgpnvhZzUjXJ_u4h7bYT_9=N8RO1AytA7_T--4pScpeU_g@mail.gmail.com>
 <CAKAnmmJPD11WpS-RCbsddhgDrZ2-_61SMjo1vaFtJuUogwTJEw@mail.gmail.com>
In-Reply-To: 
 <CAKAnmmJPD11WpS-RCbsddhgDrZ2-_61SMjo1vaFtJuUogwTJEw@mail.gmail.com>
From: Umair Shahid <umair.shahid@gmail.com>
Date: Mon, 8 Dec 2025 16:43:23 +0500
Message-ID: 
 <CAM184Afu+rcc-eVfc4nTMNDcyjAQcopFd4hygU+UZtW70d6xtQ@mail.gmail.com>
Subject: Re: Non-Compete Challenges for Community Work
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: Cornelia Biacsics <cornelia.biacsics@gmail.com>,
 pgsql-advocacy@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000001bf6c706456f4e74"
Archived-At: 
 <https://www.postgresql.org/message-id/CAM184Afu%2Brcc-eVfc4nTMNDcyjAQcopFd4hygU%2BUZtW70d6xtQ%40mail.gmail.com>
Precedence: bulk

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

On Wed, Dec 3, 2025 at 8:58=E2=80=AFPM Greg Sabino Mullane <htamfids@gmail.=
com>
wrote:

> On Tue, Dec 2, 2025 at 11:27=E2=80=AFAM Cornelia Biacsics <
> cornelia.biacsics@gmail.com> wrote:
>
>>
>>    1. Do you see this as an issue the PostgreSQL community should
>>    discuss?
>>
>> No. I've seen no examples of this. The Postgres ecosystem is thriving,
> and people jump jobs from one employer to another with no friction right
> now.
>

+1

I have not seen any examples of non-compete clauses that prevent the person
from contributing to PostgreSQL. The clauses that I have seen & experienced
are designed to prevent poaching.


>
> --
> Cheers,
> Greg
>
> --
> Crunchy Data - https://www.crunchydata.com
> Enterprise Postgres Software Products & Tech Support
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Dec 3, =
2025 at 8:58=E2=80=AFPM Greg Sabino Mullane &lt;<a href=3D"mailto:htamfids@=
gmail.com">htamfids@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Tue, Dec =
2, 2025 at 11:27=E2=80=AFAM Cornelia Biacsics &lt;<a href=3D"mailto:corneli=
a.biacsics@gmail.com" target=3D"_blank">cornelia.biacsics@gmail.com</a>&gt;=
 wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><ol><li>Do you see this as an issue the Pos=
tgreSQL community should discuss?</li></ol></div></blockquote><div>No. I=
9;ve seen no examples of this. The Postgres=C2=A0ecosystem is thriving, and=
 people jump jobs from one employer to another with no friction right now.<=
/div></div></div></blockquote><div><br></div><div>+1=C2=A0<br><br></div><di=
v>I have not seen any examples of non-compete clauses that prevent the pers=
on from contributing to PostgreSQL. The clauses that I have seen &amp; expe=
rienced are designed to prevent poaching.=C2=A0</div><div>=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D=
"gmail_quote"><div><br></div><div>--</div></div><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><br>=
</div><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchydata.c=
om" target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterprise =
Postgres Software Products &amp; Tech Support</div><div><br></div></div></d=
iv></div>
</blockquote></div></div>

--0000000000001bf6c706456f4e74--