[prev in list] [next in list] [prev in thread] [next in thread]
List: postgresql-general
Subject: Re: [HACKERS] Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0
From: Oleg Bartunov <obartunov () gmail ! com>
Date: 2016-04-30 21:07:11
Message-ID: CAF4Au4ytVUoKg152JMwdMzcJkJM-oCB=hRB88kFKvi+KVbtsBQ () mail ! gmail ! com
[Download RAW message or body]
On Fri, Apr 29, 2016 at 7:40 PM, Joshua D. Drake <jd@commandprompt.com>
wrote:
> On 04/29/2016 08:44 AM, Bruce Momjian wrote:
>
>> On Tue, Apr 12, 2016 at 11:07:04PM +0300, Oleg Bartunov wrote:
>>
>>> Our roadmap http://www.postgresql.org/developer/roadmap/ is the
>>> problem. We
>>> don't have clear roadmap and that's why we cannot plan future feature
>>> full
>>> release. There are several postgres-centric companies, which have most of
>>> developers, who do all major contributions. All these companies has their
>>> roadmaps, but not the community.
>>>
>>
>> I would be concerned if company roadmaps overtly affected the community
>> roadmap. In general, I find company roadmaps to be very short-sighted
>> and quickly changed based on the demands of specific users/customers ---
>> something we don't want to imitate.
>>
>> We do want company roadmaps to affect the community roadmap, but in a
>> healthy, long-term way, and I think, in general, that is happening.
>>
>>
> The roadmap is not the problem it is the lack of cooperation. Many
> companies are now developing features in a silo and then presenting them to
> the community. Instead we should be working with those companies to have
> them develop transparently so others can be a part of the process.
>
We are working on our roadmap to have it in form to be presented to the
community. I think we'll publish it somewhere in wiki.
>
> If the feature is going to be submitted to core anyway (or open source)
> why wouldn't we just do that? Why wouldn't EDB develop directly within the
> Pg infrastructure. Why wouldn't we build teams around the best and
> brightest between EDB, 2Q and Citus?
>
This is what I suggested. Features considered to be open source could be
discussed and developed together.
>
> Egos.
>
> Consider PgLogical, who is working on this outside of 2Q? Where is the git
> repo for it? Where is the bug tracker? Where is the mailing list? Oh, its
> -hackers, except that it isn't, is it?
>
> It used to be that everyone got together and worked together before the
> patch review process. Now it seems like it is a competition between
> companies to see whose ego can get the most inflated via press releases
> because they developed X for Y.
>
>
git log says better than any press releases :)
> If the companies were to come together and truly recognize that profit is
> the reward not the goal then our community would be much stronger for it.
I'd not limited by the companies, individual developes are highly welcome.
I'm afraid there are some.
>
>
> 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.
>
[Attachment #3 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr \
29, 2016 at 7:40 PM, Joshua D. Drake <span dir="ltr"><<a \
href="mailto:jd@commandprompt.com" \
target="_blank">jd@commandprompt.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 04/29/2016 08:44 AM, Bruce Momjian \
wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> On Tue, Apr 12, 2016 at 11:07:04PM +0300, Oleg Bartunov \
wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> Our roadmap <a \
href="http://www.postgresql.org/developer/roadmap/" rel="noreferrer" \
target="_blank">http://www.postgresql.org/developer/roadmap/</a> is the problem. \
We<br> don't have clear roadmap and that's why we cannot plan future feature \
full<br> release. There are several postgres-centric companies, which have most \
of<br> developers, who do all major contributions. All these companies has their<br>
roadmaps, but not the community.<br>
</blockquote>
<br>
I would be concerned if company roadmaps overtly affected the community<br>
roadmap. In general, I find company roadmaps to be very short-sighted<br>
and quickly changed based on the demands of specific users/customers ---<br>
something we don't want to imitate.<br>
<br>
We do want company roadmaps to affect the community roadmap, but in a<br>
healthy, long-term way, and I think, in general, that is happening.<br>
<br>
</blockquote>
<br></span>
The roadmap is not the problem it is the lack of cooperation. Many companies are now \
developing features in a silo and then presenting them to the community. Instead we \
should be working with those companies to have them develop transparently so others \
can be a part of the process.<br></blockquote><div><br></div><div>We are working on \
our roadmap to have it in form to be presented to the community. I think we'll \
publish it somewhere in wiki. <br></div><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
If the feature is going to be submitted to core anyway (or open source) why \
wouldn't we just do that? Why wouldn't EDB develop directly within the Pg \
infrastructure. Why wouldn't we build teams around the best and brightest between \
EDB, 2Q and Citus?<br></blockquote><div><br></div><div>This is what I suggested. \
Features considered to be open source could be discussed and developed together. \
<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Egos.<br>
<br>
Consider PgLogical, who is working on this outside of 2Q? Where is the git repo for \
it? Where is the bug tracker? Where is the mailing list? Oh, its -hackers, except \
that it isn't, is it?<br> <br>
It used to be that everyone got together and worked together before the patch review \
process. Now it seems like it is a competition between companies to see whose ego can \
get the most inflated via press releases because they developed X for Y.<br> \
<br></blockquote><div><br></div><div>git log says better than any press releases :) \
<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> If the companies were to come \
together and truly recognize that profit is the reward not the goal then our \
community would be much stronger for it.</blockquote><div><br></div><div>I'd not \
limited by the companies, individual developes are highly welcome. I'm afraid \
there are some.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 \
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div \
class="h5"><br> <br>
Sincerely,<br>
<br>
JD<br>
<br>
<br>
-- <br>
Command Prompt, Inc. <a href="http://the.postgres.company/" \
rel="noreferrer" target="_blank">http://the.postgres.company/</a><br> \
+1-503-667-4564<br> PostgreSQL Centered full stack support, consulting and \
development.<br> Everyone appreciates your honesty, until you are honest with \
them.<br> </div></div></blockquote></div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic