| From: | Umair Shahid <umair(dot)shahid(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Cornelia Biacsics <cornelia(dot)biacsics(at)gmail(dot)com>, pgsql-advocacy(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Non-Compete Challenges for Community Work |
| Date: | 2025-12-08 11:43:23 |
| Message-ID: | CAM184Afu+rcc-eVfc4nTMNDcyjAQcopFd4hygU+UZtW70d6xtQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Wed, Dec 3, 2025 at 8:58 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:
> On Tue, Dec 2, 2025 at 11:27 AM Cornelia Biacsics <
> cornelia(dot)biacsics(at)gmail(dot)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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2025-12-08 13:23:57 | Re: Non-Compete Challenges for Community Work |
| Previous Message | Greg Sabino Mullane | 2025-12-03 15:58:08 | Re: Non-Compete Challenges for Community Work |