Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Justin Clift <justin(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Josh berkus <josh(at)agliodbs(dot)com>
Subject: Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0
Date: 2016-05-13 16:35:40
Message-ID: 5736025C.4080504@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/13/2016 09:28 AM, Bruce Momjian wrote:
> On Fri, May 13, 2016 at 09:12:23AM -0700, Joshua Drake wrote:
>> There was no disrespect intended. I was trying to push forth an idea that
>> multi-company team collaboration is better for the community than single
>> company team collaboration. I will stand by that assertion.
>
> Uh, we are already doing that. EDB and NTT are working on FDWs and
> sharding, PostgresPro and someone else is working on a transaction
> manager, and EDB and 2nd Quadrant worked on parallelism.
>
> What is the problem you are trying to solve?

Hey, if I am wrong that's awesome. The impression I have is the general
workflow is this:

* Company(1) discusses feature with community
* Company(1) works on patch/feature for a period of time
* Company(1) delivers patch to community
* Standard operation continues (patch review, discussion, etc..)

This is not "bad" but it isn't as productive as something like this
would be:

* Company(1) + Company(2) get together and discuss using their
respective resources to collaboratively develop X (multi-master for
example).

* Company(1) + Company(2) discuss feature with community
* Company(1) + Company(2) work on patch/feature in the open, together
* Company(1) + Company(2) deliver patch to community
* Standard operation continues (patch review, discussion, etc...)

The difference being one of coopetition versions competition for the
betterment of the community. If there are companies that are doing that
already, that is awesome and I applaud it. I was just trying to further
drive that idea home.

This on my end all sourced from this event:

https://www.commandprompt.com/blogs/joshua_drake/2016/04/you_are_my_fellow_community_member/

That event is childish and a poor representation of what our community
stands for: Excellent, Correctness, Inclusion, Collaboration.

Sincerely,

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2016-05-13 16:39:58 Re: 10.0
Previous Message Dave Page 2016-05-13 16:31:16 Re: 10.0