| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Umair Shahid <umair(dot)shahid(at)gmail(dot)com> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, 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 13:23:57 |
| Message-ID: | CA+OCxowxEj2=6PvofPHy_azBsv3p_k8jkB_jaFnRq2Tw6iQv2g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Mon, 8 Dec 2025 at 11:43, Umair Shahid <umair(dot)shahid(at)gmail(dot)com> wrote:
>
>
> 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.
>
Agreed - and companies like pgEdge and EDB have policies and often
employment contracts that specifically encourage contributions.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-12-08 14:20:18 | Re: Non-Compete Challenges for Community Work |
| Previous Message | Umair Shahid | 2025-12-08 11:43:23 | Re: Non-Compete Challenges for Community Work |