Conversation

Oct 12, 2020

The majority of pgAdmin 4 code is written by EDB employees (easy to check in the repo), now they started to build the packages themselves ignoring the existing community work. Do we still talk about pgAdmin 4 as a

@PostgreSQL

community project? I strongly believe we shouldn't.

Quote Tweet

Christoph Berg

@df7cb

Oct 12, 2020

Is anyone interested in taking up #pgadmin4 maintenance for @Debian? Upstream unilaterally started distributing their own .debs, so I'm not inclined duplicating that work myself. postgresql.org/message-id/202

Replying to

and

I agree that it's concerning when one company dominates an open source project. At the same time, if we punish companies for investing heavily in open source efforts, maybe they just won't. I don't see how that would be better.

Replying to

and

That would be ideal, I'm 100% for it. It's OK to have competing projects --sometimes that comes from different backgrounds, needs ideas. But coordination, planning and tackling problems together, should be a key goal. This should apply to core PostgreSQL too.

Replying to

and

Yes, that's why open source exists. Now, collaboration is not always perfect, and it is often hard. People disagree with each other vigorously, and not always politely, so working in the community is hard, even bruising. But, at the end of the day,

is a great success.

Replying to

Its success clearly owes almost everything to bottom up project planning, incrementalism, and decentralization. Let's not forget that. Everybody cooperating and coordinating and agreeing all the time sounds vaguely sinister to me.

12:57 AM · Oct 13, 2020Twitter Web App

Likes