[gimp-web/testing] update content/bugs/submit-patch.html

[Pat David <patdavid src gnome org>]

commit 56575d524830d4e7c00bc57a5c4db6a619975d74
Author: Pat David <patdavid gmail com>
Date:   Fri Jun 8 16:56:04 2018 -0500

    update content/bugs/submit-patch.html
    
    Moved the old `submit-patch` files out of /howtos/ and updated to
    reflect using GitLab now.
    
    Ref: #1

 content/bugs/{howtos => }/submit-patch.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)
---
diff --git a/content/bugs/howtos/submit-patch.md b/content/bugs/submit-patch.md
similarity index 80%
rename from content/bugs/howtos/submit-patch.md
rename to content/bugs/submit-patch.md
index e4e52a9e..c737d8ce 100644
--- a/content/bugs/howtos/submit-patch.md
+++ b/content/bugs/submit-patch.md
@@ -1,14 +1,14 @@
 Title: How to Create and Submit a Patch
 Date: 2015-08-17T11:09:31-05:00
-Modified: 2015-08-17T11:09:40-05:00
+Modified: 2018-06-08T16:43:52-06:00 
 Authors: Pat David
 Status: hidden
 
-
 ## Introduction
 
 A patch is exactly what the word says: a small piece of code used to repair a breach. It is normally a plain 
text file containing only the differences between the current version of the code and the fixed version.
 
+
 ## Generating a Patch
 
 ### With git
@@ -50,35 +50,35 @@ To summarize the steps:
 *   Generate the patch file using  
     `diff -rup /path/to/unmodified/source /path/to/modified/source > patchfile.patch`
 *   Examine the resulting .patch file to make sure it contains only the intended changes
-*   Submit the patch using Bugzilla, see below
+*   Submit the patch using GIMP GitLab, see below
 
-## Using Bugzilla
+## Using GitLab 
 
 ### Closing a bug patch
 
-The best way to submit a patch to the GIMP development is to send it to Bugzilla and inform the rest of the 
team what the patch is doing:
+The best way to submit a patch to the GIMP development is to send it to GitLab and inform the rest of the 
team what the patch is doing:
 
 *   Is it closing bugs?
 *   Is it a enhancement?
 *   What are the changes in the code?
 *   Are there any know problems with the patch?
 
-If you have a patch that is closing bugs then you can attach the patch to the bug/bugs explaining what the 
patch is doing. You can also inform the gimp-developer mailing list about the closed bug but avoid to attach 
the patch to the mail sent to the list, instead put the bug links in the mail where the attached patch is 
located.
+If you have a patch that is closing bugs then you can attach the patch to the bug/bugs explaining what the 
patch is doing. You can also inform the gimp-developer mailing list about the closed bug but avoid attaching 
the patch to the mail sent to the list, instead put the bug links in the mail where the attached patch is 
located.
 
 1.  Test the patch locally on your own machine and look if it closes the bug there.
-2.  Find the bug it is closing in the [Open 
bugs](https://bugzilla.gnome.org/buglist.cgi?product=GIMP&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED)
 list.
+2.  Find the bug it is closing in the [Open bugs](https://gitlab.gnome.org/GNOME/gimp/issues) list.
 3.  Attach the patch to the bug report.
 4.  Explain what the patch is doing and if there might be any problems with the patch.
-5.  If you want to send a mail to the gimp-developer list and explain it there also. Remember to have the 
bug number or even better the link to the bug in the mail. Avoid attaching the patch to the mail.
+5.  If you want, send a mail to the gimp-developer list and explain it there also. Remember to have the bug 
number or even better the link to the bug in the mail. Avoid attaching the patch to the mail.
 
 Now you just have to wait for the developers and maintainers to look at the patch and see if this is really 
closing the bug and if it might open new bugs. If everything is fine it will be implemented in a release done 
soon either stable or development version.
 
 #### How about enhancements?
 
-Start a new bug report, mark it as enhancement and put the patch in that report on Bugzilla. This will give 
developers a good explanation of why you did the patch and how the patch changes GIMP source or adds new 
things to it. The only thing you need to add to the report is that it is an enhancement and explain the patch 
a little bit. A simple way to this is to:
+Start a new bug report, mark it as enhancement and put the patch in that report on GitLab. This will give 
developers a good explanation of why you did the patch and how the patch changes GIMP source or adds new 
things to it. The only thing you need to add to the report is that it is an enhancement and explain the patch 
a little bit. A simple way to this is to:
 
-1.  Go to [Submit a new bug report](https://bugzilla.gnome.org/enter_bug.cgi?product=GIMP).
-2.  Start a new report and select _enhancement_ as a _Severity_ option.
+1.  Go to [GIMP GitLab issues](https://gitlab.gnome.org/GNOME/gimp/issues).
+2.  Start a new issue and select _feature_ as a template option.
 3.  Attach the patch and explain what you wanted to get going with the help of this patch.
 4.  Remember to explain the purpose of the patch and who might want to use this enhancement.