News for hackers. Stuff that matters.
Re:PostgreSQL community impact of 2nd Quadrant purchase by hyperrail on Wednesday October 07, 2020 @03:50PM (#24711984)
Bruce Momjian doesn't mention it in the OP blog post, but the PostgreSQL core team consists of just 5 people including himself: https://www.postgresql.org/community/contributors/

Keep that in mind when you note that he says:

> the acquisition causes edb's representation in the core team to be 60%

This works out to 3 out of 5 people including Bruce himself.

Re:PostgreSQL community impact of 2nd Quadrant purchase by justinclift on Wednesday October 07, 2020 @04:41PM (#24712484)
The core team is kept that way on purpose.

They're a decision making group (eg project direction), and the size doesn't reflect the number of active developers on the project in any way.

eg there are a lot more active developers than there are "core team"

Re:PostgreSQL community impact of 2nd Quadrant purchase by jrochkind1 on Wednesday October 07, 2020 @06:53PM (#24713749)
It makes it pretty easy to solve the "50%" issue though. One person has to leave the core team, to be replaced by a newcomer.
Re:PostgreSQL community impact of 2nd Quadrant purchase by wmf on Wednesday October 07, 2020 @07:12PM (#24713918)
Or expand it to seven people.
Re:PostgreSQL community impact of 2nd Quadrant purchase by ranman on Wednesday October 07, 2020 @08:37PM (#24714461)
Is this a U.S. Supreme Court joke? Because if so... well done.
Re:PostgreSQL community impact of 2nd Quadrant purchase by phire on Wednesday October 07, 2020 @08:36PM (#24714455)
Or one of the three leaves their job.
Re:PostgreSQL community impact of 2nd Quadrant purchase by Thorrez on Wednesday October 07, 2020 @11:30PM (#24715415)
Just 6 should be fine, the rule is "not over half", so half is ok.
Re:PostgreSQL community impact of 2nd Quadrant purchase by wmf on Thursday October 08, 2020 @12:26AM (#24715786)
It's generally good to have an odd number of people on any kind of voting board so that there aren't ties.
Re:PostgreSQL community impact of 2nd Quadrant purchase by d_silin on Thursday October 08, 2020 @01:33AM (#24716163)
A better solution is to have an even number of people, but have a tie-breaker vote token that is passed around between everyone in round-robin fashion.

In the event of the tie, the tie-breaker vote owner resolves it and passes the to token to the next person.

In this manner, the decision bias is averaged out between all of the board members.

Re:PostgreSQL community impact of 2nd Quadrant purchase by gostsamo on Thursday October 08, 2020 @02:45AM (#24716522)
Whoever schedules the agenda can game the system by arranging the token to be in a preferred holder when there is a important decision to be made. Might happen ones in ten years, but bitterness does not have half-life.
Re:PostgreSQL community impact of 2nd Quadrant purchase by zaarn on Thursday October 08, 2020 @02:25AM (#24716419)
And how exactly is that worse than an uneven number of people? If there is an uneven number of people there is no bias of a tie breaker to balance out.
Re:PostgreSQL community impact of 2nd Quadrant purchase by alanbernstein on Thursday October 08, 2020 @01:08AM (#24716037)
Conventional wisdom... But I wonder if that is really true. If a tie indicates a truly divisive issue, might it be better to be stuck with the tie, and be forced to find a compromise?
Re:PostgreSQL community impact of 2nd Quadrant purchase by gwd on Thursday October 08, 2020 @06:29AM (#24717785)
> If a tie indicates a truly divisive issue, might it be better to be stuck with the tie, and be forced to find a compromise?

If 3 people prefer the bike shed to be "pale blue" and the other 3 prefer it to be "cornflower blue", does that make the color a "divisive issue"?

Ultimately, even for an issue where people have very strong feelings on both sides, it's far more important that forward progress be made. At some point, standing around arguing is only going to be counterproductive.

I gave a talk on a particularly divisive decision we had to make a few years ago:

https://www.youtube.com/watch?v=C0kiy56hGm8

Re:PostgreSQL community impact of 2nd Quadrant purchase by alanbernstein on Monday October 12, 2020 @06:17AM (#24752987)
Sure, bike shedding is a problem in general. I've been fortunate enough to have avoided it so far in my life, so I don't have much to say about it.

Anyway, my question was meant to challenge the assumption that "it's far more important that forward progress be made". If you're trying to run a business, it's hard to argue with of course.

Re:PostgreSQL community impact of 2nd Quadrant purchase by gwd on Tuesday October 13, 2020 @04:26AM (#24763469)
> Anyway, my question was meant to challenge the assumption that "it's far more important that forward progress be made".

So just to be clear, what I certainly don't mean is that action should always be taken quickly without a proper consideration. Having a discussion is obviously important for understanding all the potential pros and cons of the various decisions. Additionally, it's really important that everyone feel like their voice is heard and their needs and preferences considered.

I'm talking about once all that's done. Sometimes you have a discussion, everyone basically understands what the other people want and where they're coming from, you're pretty sure all the relevant factors have been considered, and half of the people still prefer A, and the other half prefer B. At that point, further discussion is often counterproductive.

Re:PostgreSQL community impact of 2nd Quadrant purchase by derefr on Wednesday October 07, 2020 @05:10PM (#24712773)
Seems like a more accurate title for this group, then, would be "core maintainers" — or even "board of trustees."
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Wednesday October 07, 2020 @05:36PM (#24713015)
It's 2020, why are we still telling people what they're supposed to call themselves?

They could style as The Choir of the Aztounding Relational Pachyderm for all it ought to matter.

Notwithstanding which, it's pretty conventional for the role of FOSS project core teams to be administrative-deliberative stewardship and an umbrella authority for all project activities. The overlap with membership of the developer community and concern for technical outcomes is a function of the domain, not the team purpose. The governance consequence at hand being that representational proportions matter to preserve independence and the appearance thereof.

Re:PostgreSQL community impact of 2nd Quadrant purchase by Thorentis on Wednesday October 07, 2020 @07:35PM (#24714083)
Conventions exist for a reason. Choosing a name which is immediately recognisable and conveys the meaning you know others will glean from it is a sensible and rational thing to do. In fact, picking outlandish names purely to "buck the trend" and make some kind of statement about naming and identity reeks of immaturity and ideology.
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Wednesday October 07, 2020 @08:45PM (#24714500)
This view isn't merely bland, conservative, and patronising. I find it downright abhorrent, being the kind of sentiment at the roots of every organisation that ever excluded/demoralised the folks that didn't talk, look, think, or behave like some cookie-cutter template.

There is no assertable "fact" that diversity of expression, or the expression of preferences and identity, extends from immaturity or ideology. On the contrary, it is a mark of organisational and civilisational maturity, and willingness to embrace ideas, that such self-expression is possible, accepted, and encouraged. The qualifiers I'd suggest instead are heterogeneity and imagination, and there is no trend to buck; the world is, and always has been, full of complicated, imaginative people.

When I am very lucky, I even get to work with them.

Sans identity, the individual is a puppet, and sans creativity, humanity is cosmically uninteresting.

Re:PostgreSQL community impact of 2nd Quadrant purchase by Thorentis on Wednesday October 07, 2020 @09:55PM (#24714850)
There are plenty of other ways to express your individual identity, without hindering ease of communication. In this particular case, giving the group a name which does not contain information about what the group does is contrary to the goal of communicating the group's purpose.

If your only goal is to communicate what a progressive, free thinking, modern ideologue you are, then sure, give your groups whatever names you like if that's the sort of people you want to dog whistle to. If, like most other people, you simply want to communicate the groups purpose in a quick way, then there are plenty of de facto standards to follow.

Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Wednesday October 07, 2020 @11:06PM (#24715261)
Good grief, what a pernicious worldview.

Fortunately, most people choosing whimsical names for things actually do so playfully and creatively. The idea that out there some grumpy clown with a stick up their ass about "ease of communication" is going to launch into a diatribe about "dog whistles" and "ideology", doesn't enter into that process.

Rather serendipitously my next library extraction is postgresql-related. I was pondering an appropriate name. In the circumstance I think I shall name it Chorale of the Aztounding Relational Pachyderm, and if anyone asks I will point them in your direction for an explanation.

Re:PostgreSQL community impact of 2nd Quadrant purchase by justinclift on Thursday October 08, 2020 @08:24AM (#24718447)
> Chorale of the Aztounding Relational Pachyderm

If you change that slightly to "Chorale of the Relational Aztounding Pachyderm", it might hinder adoption. Or maybe not. ;)

Re:PostgreSQL community impact of 2nd Quadrant purchase by mrslave on Wednesday October 07, 2020 @05:54PM (#24713199)
I can't tell if this is a dig at the elaborate job titles we have today (Director of Creative, Employee Journey Advisor, Sales Engineer, Chief Happiness Officer, etc.) or progressive identity politics (pronouns, etc.). Perhaps they're not unrelated.
Re:PostgreSQL community impact of 2nd Quadrant purchase by danielheath on Wednesday October 07, 2020 @06:35PM (#24713609)
"The Choir of the Aztounding Relational Pachyderm" is exactly the kind of group name I would have expected to see in 90s hacker circles (similar to eg the group that produces POC || GTFO - "PASTOR MANUL LAPHROAIG AND HIS MERRY BAND OF REVERSE ENGINEERS").
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Wednesday October 07, 2020 @09:04PM (#24714603)
You got me. All I remember is, xs4all threw the best parties and the characters of Cryptonomicon all seem eerily familiar.
Re:PostgreSQL community impact of 2nd Quadrant purchase by callamdelaney on Wednesday October 07, 2020 @09:15PM (#24714674)
Because naming is important. I don't call myself Prime Minister, because I'm not the Prime Minister. I don't call my index iterators `golf_ball` either for the same reason.
Re:PostgreSQL community impact of 2nd Quadrant purchase by CodesInChaos on Thursday October 08, 2020 @04:09AM (#24717015)
And yet President of the United States, and President of Germany are completely different roles.
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Thursday October 08, 2020 @04:34PM (#24723638)
People are not loop variables. You don't get to name them. Their names certainly do matter, but in exactly the opposite fashion.

I suppose that a mindset capable of reducing human agency to the status of loop variables, explains some of the frankly tyrannical opinions being expressed in response to my remark.

Re:PostgreSQL community impact of 2nd Quadrant purchase by callamdelaney on Friday October 09, 2020 @05:33AM (#24728236)
Do you ever comment in a tone that isn't permanently offended?
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Wednesday October 14, 2020 @07:17AM (#24775323)
My tone is not offended, Prime Minister. My tone is wearily sardonic tinged with supercilious grandstanding.
Re:PostgreSQL community impact of 2nd Quadrant purchase by callamdelaney on Tuesday October 20, 2020 @07:01PM (#24843181)
How dare you not respect my naming preference, you supercilious tyrannical bigot.
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Wednesday October 07, 2020 @09:56PM (#24714860)
The point being, if you did wish to be called Prime Minister then I'd respect your preference. Who's to say that you're not a Prime Minister? Or perhaps that your family name is actually Minister, and your nickname that everyone's known you by since high school is Prime?

Whatever you choose, it's not my business to judge.

Re:PostgreSQL community impact of 2nd Quadrant purchase by trashburger on Thursday October 08, 2020 @02:18AM (#24716396)
What is your opinion on the investigation by the FBI about the person who impersonated an FBI officer on Twitter, then? Should people be allowed to call themselves FBI officers?
Re:PostgreSQL community impact of 2nd Quadrant purchase by inopinatus on Thursday October 08, 2020 @04:16AM (#24717055)
I have no opinion about US domestic policy and no standing to pronounce one, so I'm unlikely to form one in a hurry just to argue the toss. As for the dumpster fire that is Twitter: the usual advice is, for all Internet denizens is never read the comments, and Twitter is 100% comments. But I digress.

The equivalent, in all my own countries of citizenship, origin, or residence, might be that deceiving someone into thinking you are a police officer is already illegal, although simple impersonation may not be e.g. for satirical purposes. Satire aside, in a country that generally trusts its law enforcement personnel, such a deception, particularly in person, may have both high capacity for harm and a high likelihood it occurs for harm's sake. Nevertheless, notwithstanding my total unfamiliarity with the case you refer to, I struggle to see how Twitter is ever anything other than satire. My own Twitter profile reflects this view.

Curiously, in Australia, it is illegal to claim an association with Sir Donald Bradman, and for similar reasons of potential harm. Impersonating a Prime Minister is not, since it is a very low occupation and any attempt to do so is self-evidently preposterous.

Re:PostgreSQL community impact of 2nd Quadrant purchase by kbenson on Wednesday October 07, 2020 @07:45PM (#24714142)
> It's 2020, why are we still telling people what they're supposed to call themselves?

I think if you look closely you'll see GP didn't say they should be called that, just that it would be more accurate to call them that, presumably with respect to communicating their responsibilities to others.

Re:PostgreSQL community impact of 2nd Quadrant purchase by tclancy on Wednesday October 07, 2020 @06:55PM (#24713768)
Will you sponsor me to rush?
Re:PostgreSQL community impact of 2nd Quadrant purchase by thejobsdev on Wednesday October 07, 2020 @04:01PM (#24712093)
How much depends on so few in tech always amazes me.

Go on any major project and see the contributors and the distribution of commits between the top 5-10 vs everyone else and it's almost always startling.

Re:PostgreSQL community impact of 2nd Quadrant purchase by anarazel on Wednesday October 07, 2020 @05:38PM (#24713046)
Note that the postgres core team aren't all developing postgres itself, and that there's a vastly larger number of people working on postgres than the core team. They're basically "just" a body to escalate things to.
Re:PostgreSQL community impact of 2nd Quadrant purchase by jrott on Wednesday October 07, 2020 @04:11PM (#24712186)
It's always pretty shocking. You even see it at big companies where you'll only have a few engineers working on the core product and then a ton of people working on supporting infrastructure (analytics, marketing and what have you) around them.
Re:PostgreSQL community impact of 2nd Quadrant purchase by jpz on Wednesday October 07, 2020 @07:25PM (#24714010)
Pareto's Principle arises everywhere.
Re:PostgreSQL community impact of 2nd Quadrant purchase by wtracy on Wednesday October 07, 2020 @03:58PM (#24712063)
If so, one or two companies could handle fix this problem by dedicating an employee to working on Postgres.

Unfortunately, most of the likely candidates with money to throw around have their own pet database systems, and don't have in interest in Postgres.

Maybe one of the mid-sized cloud providers like Digital Ocean would be interested?

Re:PostgreSQL community impact of 2nd Quadrant purchase by pgaddict on Wednesday October 07, 2020 @04:21PM (#24712286)
Google the names of the committers and major contributors, and you'll see many are working for quite large enterprise-y companies ;-)

Obviously, if more companies start supporting the community, that'd be even better.

Re:PostgreSQL community impact of 2nd Quadrant purchase by mrich on Wednesday October 07, 2020 @05:48PM (#24713148)
There are many Postgres forks out there. Maybe the solution will be to have someone from EDB step down, and add e.g. an active contributor from Amazon to the core team?
Re:PostgreSQL community impact of 2nd Quadrant purchase by dragonwriter on Wednesday October 07, 2020 @06:42PM (#24713672)
> an active contributor from Amazon to the core team?

That would be weird, since Amazon has no major contributors. NTT, Microsoft, Fujitsu, or another seat for Crunchy Data (among other possibilities) would seem to be more natural choices than giving a seat to Amazon, looking at major contributors.

Re:PostgreSQL community impact of 2nd Quadrant purchase by antb123 on Thursday October 08, 2020 @04:32AM (#24717132)
Fujitsu is the longest standing large company.
Re:PostgreSQL community impact of 2nd Quadrant purchase by vyruss on Thursday October 08, 2020 @08:29AM (#24718492)
major? More like none.
Re:PostgreSQL community impact of 2nd Quadrant purchase by anarazel on Wednesday October 07, 2020 @06:14PM (#24713418)
Amazon is not exactly a large contributor to postgres...
Re:PostgreSQL community impact of 2nd Quadrant purchase by marcinzm on Wednesday October 07, 2020 @03:56PM (#24712043)
It's sort of mind boggling how few people underpin the infrastructure and software so many of us we depend on.
Re:PostgreSQL community impact of 2nd Quadrant purchase by pgaddict on Wednesday October 07, 2020 @04:06PM (#24712134)
Keep in mind that "core team" does not mean "core developers" here. The PostgreSQL core team's responsibilities are more about governing the community (see https://www.postgresql.org/developer/core/).

When it comes to development, it might be better to look at committers, i.e. people with the right to commit stuff, recognized contributors, or even people who submitted patch to a recent commitfest:

* https://wiki.postgresql.org/wiki/Committers

* https://www.postgresql.org/community/contributors/

* https://commitfest.postgresql.org/29/

And those groups are much larger and more diverse (in terms of employers). Plus if you look the the stats published by Robert Haas, some of the most active developers are working for other companies.

Edit: That being said, I'd love to see people from other companies participating in the community, and I'm generally trying to help new contributors with their patches.

Re:PostgreSQL community impact of 2nd Quadrant purchase by xapata on Wednesday October 07, 2020 @08:01PM (#24714245)
That's true outside of software as well. It's a complex world out there. Follow a thread far enough and you'll find that 7 billion people isn't very many after all.
Re:PostgreSQL community impact of 2nd Quadrant purchase by owens99 on Wednesday October 07, 2020 @08:01PM (#24714248)
Why does this fact make a difference? His point still stands pretty strongly in light of this keep in mind comment.
Re:PostgreSQL community impact of 2nd Quadrant purchase by breakingcups on Wednesday October 07, 2020 @03:53PM (#24712018)
Wow, that is such a small core team.