Re: pgadmin3 some fixes - Mailing list pgadmin-support

From Anthony DeBarros
Subject Re: pgadmin3 some fixes
Date
Msg-id CAAQFaFLdXJ1hkgfOO+EPu3FWiZ=jTvA4zKtM6w7u=murRgrdFQ@mail.gmail.com
Whole thread Raw
In response to pgadmin3 some fixes  (Dmitry Voronin <carriingfate92@yandex.ru>)
Responses Re: pgadmin3 some fixes  (Dmitry Voronin <carriingfate92@yandex.ru>)
List pgadmin-support
While pgAdmin 4 will naturally continue to improve, it is fully understandable that people want to keep pgAdmin3 alive and are willing to do the work. That's the beauty of open source. However, I'm wondering whether it would make sense for the community to agree on maintaining one fork of the project so that various improvements all end up in the same place?

For example, yesterday BigSQL announced its own fork of pgAdmin3:

On Fri, Oct 28, 2016 at 3:16 AM, Dmitry Voronin <carriingfate92@yandex.ru> wrote:
Hello,

For some reasons we need to use pgadmin3 in our work. I will make some fixes of pgadmin3 origin code to make it useable with new PostgreSQL versions.

My fork located at: https://github.com/dimv36/pgadmin3.

Today pgadmin3 can:

  - Create or edit policies
  - Enable/Disable RLS on tables.
  - Full translation for ru locale.

Your pull requests or additions are welcome!

-- 
Best regards, Dmitry Voronin


--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support

pgadmin-support by date:

Previous
From: André Cardoso
Date:
Subject: Re: pgAdmin 4.1.1 cannot run on win7
Next
From: Mark Csaba
Date:
Subject: Re: pgAdmin 4.1.1 cannot run on win7