IntenseWebs/pgadmin4
3
0
Fork 0
mirror of https://github.com/pgadmin-org/pgadmin4.git synced 2024-11-22 08:46:39 -06:00
Code Issues Packages Projects Releases Wiki Activity

Fix mailto links and link to code_review doc.

Browse Source
This commit is contained in:
Chris Mayo 2016-10-10 09:31:58 +01:00 committed by Dave Page
parent 148808a17b
commit 5ac2cceac7
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en_US/contributions.rst
View File

@ -4,7 +4,7 @@
pgAdmin Project Contributions pgAdmin Project Contributions
***************************** *****************************
pgAdmin is an open-source project that invites you to get involved in the development process. For more information about contributing to the pgAdmin project, contact the developers on the pgAdmin mailing list <mailto:pgadmin-hackers@postgresql.org> to discuss any ideas you might have for enhancements or bug fixes. pgAdmin is an open-source project that invites you to get involved in the development process. For more information about contributing to the pgAdmin project, contact the developers on the pgAdmin mailing list pgadmin-hackers@postgresql.org to discuss any ideas you might have for enhancements or bug fixes.
In the sections listed below, you'll find detailed information about the development process used to develop, improve, and maintain the pgAdmin client. In the sections listed below, you'll find detailed information about the development process used to develop, improve, and maintain the pgAdmin client.

10
docs/en_US/submitting_patches.rst
View File

@ -5,7 +5,7 @@ Submitting Patches
****************** ******************
Before developing a patch for pgAdmin you should always contact the developers Before developing a patch for pgAdmin you should always contact the developers
on the `mailing list <mailto:pgadmin-hackers@postgresql.org>` to discuss your on the mailing list pgadmin-hackers@postgresql.org to discuss your
plans. This ensures that others know if you're fixing a bug and can then avoid plans. This ensures that others know if you're fixing a bug and can then avoid
duplicating your work, and in the case of large patches, gives the community duplicating your work, and in the case of large patches, gives the community
the chance to discuss and refine your ideas before investing too much time the chance to discuss and refine your ideas before investing too much time
@ -29,8 +29,8 @@ might run::
to create a patch between your development branch and the public master branch. to create a patch between your development branch and the public master branch.
Once you have your patch, check it thoroughly to ensure it meets the pgAdmin Once you have your patch, check it thoroughly to ensure it meets the pgAdmin
:doc:`coding_standards`, and review it against the :doc:`code-review' to minimise :doc:`coding_standards`, and review it against the :doc:`code_review` to minimise
the chances of it being rejected. Once you're happy with your work, mail it to the the chances of it being rejected. Once you're happy with your work, mail it to the
`mailing list <mailto:pgadmin-hackers@postgresql.org>`. Please ensure you mailing list pgadmin-hackers@postgresql.org. Please ensure you include a full
include a full description of what the patch does, as well as the rationale for description of what the patch does, as well as the rationale for any important
any important design decisions. design decisions.