GNOME.org
 

[gimp-web/gimp-web-static] Minor tweak to text on submitting changes

commit 0a2d267490881a0ea41476c985345606b737815f
Author: Pat David <patdavid gmail com>
Date:   Tue Oct 27 11:35:14 2015 -0500

    Minor tweak to text on submitting changes

 content/develop/index.md |  191 +++++++++++++++++++++++-----------------------
 1 files changed, 97 insertions(+), 94 deletions(-)
---
diff --git a/content/develop/index.md b/content/develop/index.md
index 434065c..16fa958 100644
--- a/content/develop/index.md
+++ b/content/develop/index.md
@@ -1,56 +1,56 @@
-Title: Get Involved
-Date: 2015-08-14T14:18:56-05:00
-Author: Pat David
-
-
-<figure>
-<script type='text/javascript' 
src='https://www.openhub.net/p/gimp/widgets/project_basic_stats?format=js'></script>
-</figure>
-
-## How You Can Help
-
-GIMP is <span class="help" title="software that may be modified and
-distributed freely, as long as you do not deny other users these
-freedoms">Free Software</span> and a part of the [GNU Project](http://www.gnu.org/). In the free software 
world, there is generally no distinction between users and developers. As in a friendly neighbourhood, 
everybody pitches in to help their neighbors. Please consider the time you give in assistance to others as 
payment.
-
-Ways in which you can help:
-
-*   [program](http://wiki.gimp.org/) new features,
-*   report [bugs](/bugs/) (errors in the program),
-*   debug existing features,
-*   add [documentation](/docs/),
-*   translate GIMP to your own language,
-*   translate the documentation,
-*   write [tutorials](/tutorials/),
-*   participate in the [UI brainstorm](http://gimp-brainstorm.blogspot.com/),
-*   improve this web site,
-*   make artwork for GIMP used in or with GIMP,
-*   let people know you used GIMP for your artwork,
-*   give away copies of GIMP,
-*   help others to learn to use GIMP, etc.
-
-As you can see, anyone can help.
-
+Title: Get Involved
+Date: 2015-08-14T14:18:56-05:00
+Author: Pat David
+
+
+<figure>
+<script type='text/javascript' 
src='https://www.openhub.net/p/gimp/widgets/project_basic_stats?format=js'></script>
+</figure>
+
+## How You Can Help
+
+GIMP is <span class="help" title="software that may be modified and
+distributed freely, as long as you do not deny other users these
+freedoms">Free Software</span> and a part of the [GNU Project](http://www.gnu.org/). In the free software 
world, there is generally no distinction between users and developers. As in a friendly neighbourhood, 
everybody pitches in to help their neighbors. Please consider the time you give in assistance to others as 
payment.
+
+Ways in which you can help:
+
+*   [program](http://wiki.gimp.org/) new features,
+*   report [bugs](/bugs/) (errors in the program),
+*   debug existing features,
+*   add [documentation](/docs/),
+*   translate GIMP to your own language,
+*   translate the documentation,
+*   write [tutorials](/tutorials/),
+*   participate in the [UI brainstorm](http://gimp-brainstorm.blogspot.com/),
+*   improve this web site,
+*   make artwork for GIMP used in or with GIMP,
+*   let people know you used GIMP for your artwork,
+*   give away copies of GIMP,
+*   help others to learn to use GIMP, etc.
+
+As you can see, anyone can help.
+
 ### Development Status
-
-The team is currently busy working on v2.10\. This will be the first release of GIMP featuring a new, 
advanced image processing engine, high bit depth editing, as well as new and improved transformation and 
selection tools.
-
-Porting internals of GIMP to GEGL is mostly done, but more plugins have to be ported to GEGL, and GEGL needs 
to be made faster. If you are willing to help with that, please refer to the [Porting filters to 
GEGL](http://wiki.gimp.org/index.php/Hacking:Porting_filters_to_GEGL) page to see what you could work on.
-
-To get a better understanding of where the project is heading to, which features are planned etc., please 
visit the [Roadmap](http://wiki.gimp.org/index.php/Roadmap) page.
-
+
+The team is currently busy working on v2.10\. This will be the first release of GIMP featuring a new, 
advanced image processing engine, high bit depth editing, as well as new and improved transformation and 
selection tools.
+
+Porting internals of GIMP to GEGL is mostly done, but more plugins have to be ported to GEGL, and GEGL needs 
to be made faster. If you are willing to help with that, please refer to the [Porting filters to 
GEGL](http://wiki.gimp.org/index.php/Hacking:Porting_filters_to_GEGL) page to see what you could work on.
+
+To get a better understanding of where the project is heading to, which features are planned etc., please 
visit the [Roadmap](http://wiki.gimp.org/index.php/Roadmap) page.
+
 ### Bug Reports
-
-GIMP is not a bug-free application nor is any other application so reporting the bugs that you will 
encounter is very important to the development, it helps the developers to make GIMP more stable and more bug 
free.
-
-You don't have to be a developer or a everyday user to report bugs. It can be hard to report a bug the first 
time you try it out but don't just quit the whole bug report if you think it is hard. Instead, look at the 
[bugs](/bugs/) page you will find some very good help about this.
-
+
+GIMP is not a bug-free application nor is any other application so reporting the bugs that you will 
encounter is very important to the development, it helps the developers to make GIMP more stable and more bug 
free.
+
+You don't have to be a developer or a everyday user to report bugs. It can be hard to report a bug the first 
time you try it out but don't just quit the whole bug report if you think it is hard. Instead, look at the 
[bugs](/bugs/) page you will find some very good help about this.
+
 ### Web Development
-
-Creating websites that contain useful information is very important. It is actually just as important as 
doing bug reports. A website contains a lot of information that is needed for the development to move on and 
it also contains information that will help the public to understand what the application is all about.
-
-## Hacking
-
+
+Creating websites that contain useful information is very important. It is actually just as important as 
doing bug reports. A website contains a lot of information that is needed for the development to move on and 
it also contains information that will help the public to understand what the application is all about.
+
+## Hacking
+
 GIMP uses [git](https://git-scm.com/) as its revision control system, and the [GNOME 
Foundation](https://www.gnome.org/) hosts all of our code repositories:
 
 *   [`gimp`](https://git.gnome.org/browse/gimp/) - the GIMP application itself
@@ -67,51 +67,54 @@ New contributors should first introduce themselves on IRC (the #gimp channel at
 *   [GIMP Documentation mailing list, for working on the user 
manual](https://mail.gnome.org/mailman/listinfo/gimp-docs-list)
 
 This way you can announce the changes you intend to make, ask questions, and discuss which changes would be 
best. It's generally better to focus on one thing at a time. Contributing to a software project for the first 
time is always the hardest part, which is why we're here to help each other. There are also websites to give 
you a good look at how hacking is being done in GIMP.
-
-The site you should keep updated with and the site that is updated all the time with new development help 
guides is located at [http://wiki.gimp.org/](http://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://git.gnome.org/browse/gimp/plain/INSTALL)  
-     _(Contains most up-to-date information on building GIMP from source code)_
-*   [HACKING](https://git.gnome.org/browse/gimp/plain/HACKING)  
-     _(Contains a lot of information that you need to know if you want to start coding)_
-*   [README](https://git.gnome.org/browse/gimp/plain/README)  
-     _(The main README for GIMP which should be read by everyone)_
-*   [README.i18n](https://git.gnome.org/browse/gimp/plain/README.i18n)  
-     _(The internationalization README which should be read by translators)_
-
+
+The site you should keep updated with and the site that is updated all the time with new development help 
guides is located at [http://wiki.gimp.org/](http://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://git.gnome.org/browse/gimp/plain/INSTALL)  
+     _(Contains most up-to-date information on building GIMP from source code)_
+*   [HACKING](https://git.gnome.org/browse/gimp/plain/HACKING)  
+     _(Contains a lot of information that you need to know if you want to start coding)_
+*   [README](https://git.gnome.org/browse/gimp/plain/README)  
+     _(The main README for GIMP which should be read by everyone)_
+*   [README.i18n](https://git.gnome.org/browse/gimp/plain/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 the mailing list for feedback. 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.
-
-## Important GIMP Links
-
-*   [The GNU Image Manipulation Program](http://www.gimp.org/) - www.gimp.org
-*   [GIMP Wiki](http://wiki.gimp.org/) - wiki.gimp.org
-*   [GIMP Bugzilla](https://bugzilla.gnome.org/) - bugzilla.gnome.org
-*   [The GIMP Toolkit](http://www.gtk.org/) - www.gtk.org
-*   [GNU Project](http://www.gnu.org/) - www.gnu.org
-*   [GNU General Public License](/about/COPYING) - GPL
-
-## GIMP RSS feeds
-
-*   [GIMP Active 
Bugs](https://bugzilla.gnome.org/buglist.cgi?bug_file_loc_type=substring&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&changedin=7&chfieldto=Now&product=GIMP&query_format=advanced&title=Bug%20List:%20GIMP%20-%20Current%20Bug%20Week&ctype=atom)
-
-## <a name="development"></a>GIMP Development Links
-
-[GIMP developers](http://wiki.gimp.org)  
- The main GIMP development website.
-
-[Martin Nordholts' GIMP Blog](http://www.chromecode.com/)  
- What happens in GIMP development.
-
-[GEGL](http://www.gegl.org/)  
- An image processing library based on GObjects.
-
-[GNOME GIT](https://git.gnome.org/)  
- GNOME GIT source code repository
-
-## Latest Changes in Code
-
-The [Unstable GIMP](https://git.gnome.org/browse/gimp/log/) page lists the lastest source code commits to 
the unstable branch of GIMP.
+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 
[Bugzilla](https://bugzilla.gnome.org/enter_bug.cgi?product=gimp-web) 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.
+
+## Important GIMP Links
+
+*   [The GNU Image Manipulation Program](http://www.gimp.org/) - www.gimp.org
+*   [GIMP Wiki](http://wiki.gimp.org/) - wiki.gimp.org
+*   [GIMP Bugzilla](https://bugzilla.gnome.org/) - bugzilla.gnome.org
+*   [The GIMP Toolkit](http://www.gtk.org/) - www.gtk.org
+*   [GNU Project](http://www.gnu.org/) - www.gnu.org
+*   [GNU General Public License](/about/COPYING) - GPL
+
+## GIMP RSS feeds
+
+*   [GIMP Active 
Bugs](https://bugzilla.gnome.org/buglist.cgi?bug_file_loc_type=substring&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&changedin=7&chfieldto=Now&product=GIMP&query_format=advanced&title=Bug%20List:%20GIMP%20-%20Current%20Bug%20Week&ctype=atom)
+
+## <a name="development"></a>GIMP Development Links
+
+[GIMP developers](http://wiki.gimp.org)  
+ The main GIMP development website.
+
+[Martin Nordholts' GIMP Blog](http://www.chromecode.com/)  
+ What happens in GIMP development.
+
+[GEGL](http://www.gegl.org/)  
+ An image processing library based on GObjects.
+
+[GNOME GIT](https://git.gnome.org/)  
+ GNOME GIT source code repository
+
+## Latest Changes in Code
+
+The [Unstable GIMP](https://git.gnome.org/browse/gimp/log/) page lists the lastest source code commits to 
the unstable branch of GIMP.
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]