<div>I agree with Anthony. it will be great.</div><div> </div><div>28.10.2016, 15:33, "Anthony DeBarros" <adebarros(at)gmail(dot)com>:</div><blockquote type="cite"><div>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?<div> </div><div>For example, yesterday BigSQL announced its own fork of pgAdmin3:</div><div><a href="https://www.bigsql.org/pgadmin3/">https://www.bigsql.org/pgadmin3/</a></div></div><div> <div>On Fri, Oct 28, 2016 at 3:16 AM, Dmitry Voronin <span><<a target="_blank" href="mailto:carriingfate92(at)yandex(dot)ru">carriingfate92(at)yandex(dot)ru</a>></span> wrote:<blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<br /><br />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.<br /><br />My fork located at: <a target="_blank" href="https://github.com/dimv36/pgadmin3">https://github.com/dimv36/pgadmin3</a>.<br /><br />Today pgadmin3 can:<br /><br /> - Create or edit policies<br /> - Enable/Disable RLS on tables.<br /> - Full translation for ru locale.<br /><br />Your pull requests or additions are welcome!<br /><br /><span><font color="#888888">-- <br />Best regards, Dmitry Voronin<br /><br /><br />--<br />Sent via pgadmin-support mailing list (<a href="mailto:pgadmin-support(at)postgresql(dot)org">pgadmin-support(at)postgresql(dot)org</a>)<br />To make changes to your subscription:<br /><a target="_blank" href="http://www.postgresql.org/mailpref/pgadmin-support">http://www.postgresql.org/mailpref/pgadmin-support</a></font></span></blockquote></div></div></blockquote><div> </div><div> </div><div>-- </div><div>Best regards, Dmitry Voronin</div><div> </div>