Commit 4614705b authored by nmat's avatar nmat 🐍

Add GIMP GUI mailinglist

* Fixes #96
parent 9612fb58
......@@ -72,6 +72,7 @@ New contributors should first introduce themselves on IRC (the #gimp channel at
* [GIMP Developers mailing list, for those who work on the core GIMP application and plugins](https://mail.gnome.org/mailman/listinfo/gimp-developer-list)
* [GEGL Developers mailing list for developers of the GEGL library](https://mail.gnome.org/mailman/listinfo/gegl-developer-list)
* [GIMP GUI Developers mailing list, for working on GIMP GUI](https://mail.gnome.org/mailman/listinfo/gimp-gui-list)
* [GIMP Web Developers mailing list, for working on this website](https://mail.gnome.org/mailman/listinfo/gimp-web-list)
* [GIMP Documentation mailing list, for working on the user manual](https://mail.gnome.org/mailman/listinfo/gimp-docs-list)
......@@ -83,21 +84,21 @@ GIMP has a complex code base, and newcomers that might not be sure where to star
The site you should keep updated with and the site that is updated all the time with new development help guides is located at <https://wiki.gimp.org/>. If you have GIMP installed at the moment then there are some files you should look at in the source code that might help you a little.
* [INSTALL](https://gitlab.gnome.org/GNOME/gimp/blob/master/INSTALL.in)
* [INSTALL](https://gitlab.gnome.org/GNOME/gimp/blob/master/INSTALL.in)
_(Contains most up-to-date information on building GIMP from source code)_
* [HACKING](https://gitlab.gnome.org/GNOME/gimp/blob/master/HACKING)
* [HACKING](https://gitlab.gnome.org/GNOME/gimp/blob/master/HACKING)
_(Contains a lot of information that you need to know if you want to start coding)_
* [README](https://gitlab.gnome.org/GNOME/gimp/blob/master/README)
* [README](https://gitlab.gnome.org/GNOME/gimp/blob/master/README)
_(The main README for GIMP which should be read by everyone)_
* [README.i18n](https://gitlab.gnome.org/GNOME/gimp/blob/master/README.i18n)
* [README.i18n](https://gitlab.gnome.org/GNOME/gimp/blob/master/README.i18n)
_(The internationalization README which should be read by translators)_
Once you've figured out what to do, though, be bold and get to work!
## How To Submit Your Changes
When you're ready, make your edits and [generate a patch file](https://git-scm.com/docs/git-format-patch).
Send the patch file, along with a summary of what you did to a bug/enhancement request on the [bugtracker](https://gitlab.gnome.org/GNOME/gimp/issues) or to the mailing list.
When you're ready, make your edits and [generate a patch file](https://git-scm.com/docs/git-format-patch).
Send the patch file, along with a summary of what you did to a bug/enhancement request on the [bugtracker](https://gitlab.gnome.org/GNOME/gimp/issues) or to the mailing list.
The GIMP community is a friendly one, but it probably is still worth saying this: Try not to take critiques personally. We all just want GIMP to be the best that it can be. Once approved, your edits will be merged into the code base, making you an official GIMP contributor. And if you keep up the good work, not only will this process get easier with practice, your administrative privileges in GIMP development will also increase too.
......@@ -115,16 +116,16 @@ The GIMP community is a friendly one, but it probably is still worth saying this
## <a name="development"></a>GIMP Development Links
[GIMP developers](http://wiki.gimp.org)
[GIMP developers](http://wiki.gimp.org)
The main GIMP development website
[GEGL](http://www.gegl.org/)
[GEGL](http://www.gegl.org/)
An image processing library based on GObjects
[babl](http://gegl.org/babl/)
A dynamic, any to any, pixel format translation library
[GNOME GIT](https://gitlab.gnome.org/)
[GNOME GIT](https://gitlab.gnome.org/)
GNOME GIT source code repository
## Latest Changes in Code
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment