Commit 6311d6ce authored by Jehan's avatar Jehan
Browse files

content: fix irc.html and mail_lists.html links.

Replaced with discuss.html in various long-term contents pages.

I didn't fix in a few places on purpose:
- Old news articles because past is past and the old links will still
  work anyway (a redirection was set up in oscp branch), because good
  URLs don't change. So it's all good.
- Old userfaq for same reason. Outdated and all.
- file-list.md and wtf-pelican.md because these seem to be about the
  move to Pelican years ago, like a historical log of what was done. It
  makes no sense to touch these.
parent 85ce3d47
Pipeline #332653 failed with stage
in 59 minutes and 58 seconds
......@@ -162,12 +162,12 @@ You would write the link using `{filename}` and a relative path to the source lo
This may seem redundant, but it makes sense in the context of Pelican running without our plugin modification and
for a few pages of our own.
For instance, we have a page called [**IRC**]({filename}../../irc.md) that exists on the root of the site:
For instance, we have a page called [**Discuss**]({filename}../../discuss.md) that exists on the root of the site:
www.gimp.org/irc.html
www.gimp.org/discuss.html
The actual source file is located in a different place:
content/about/irc.md
content/about/discuss.md
Using the `{filename}/path/to/source/file` syntax makes sure that links won't break in the future if anything were to change.
......@@ -7,7 +7,7 @@ status: hidden
This site is maintained by a team of volunteers who are constantly trying to improve it. We are all GIMP users and some of us are also GIMP developers. If you have a question or a comment about GIMP, we will do our best to help you. However, we get a _lot_ of mail and we may not be able to answer all queries. The best way to get support is to post your questions and comments to one of the [mailing lists](/mail_lists.html) or [IRC channels](/irc.html), or to the GIMP newsgroup (comp.graphics.apps.gimp).
This site is maintained by a team of volunteers who are constantly trying to improve it. We are all GIMP users and some of us are also GIMP developers. If you have a question or a comment about GIMP, we will do our best to help you. However, we get a _lot_ of mail and we may not be able to answer all queries. The best way to get support is to post your questions and comments to one of the [mailing lists or IRC channels](/discuss.html), or to the GIMP newsgroup (comp.graphics.apps.gimp).
If you have a problem with GIMP and you think that you have found a bug or if you would like to suggest a new feature, you can also take a look at our [bugs page](/bugs/). Your problem may have been reported or solved already, so please [search and browse](https://gitlab.gnome.org/GNOME/gimp/issues) for existing reports first.
......@@ -18,7 +18,7 @@ If you have the feeling that your report will require (longer) discussion - this
If you detected a problem on one of our pages, such as a broken link or some incorrect information, please use GNOME Gitlab to [submit a bug report for this web site](https://gitlab.gnome.org/Infrastructure/gimp-web/issues). Several GIMP contributors are keeping an eye on the bug database regularly so this is probably the best way to tell us about these problems and to get a timely response.
You can also subscribe to the [gimp-web mailing list](/mail_lists.html) and then submit your improvement proposals to the list.
You can also subscribe to the [gimp-web mailing list](/discuss.html) and then submit your improvement proposals to the list.
## Download mirrors
......@@ -39,4 +39,4 @@ You will see lots of partial requests for pieces of files, especially after new
## Last resort
If you want to contact us by e-mail, then post to the [gimp-developer mailing list](/mail_lists.html).
If you want to contact us by e-mail, then post to the [gimp-developer mailing list](/discuss.html).
......@@ -30,7 +30,7 @@ The goal of the following is to give the developers as much information about wh
If using GIMP for GNU/Linux, start the program from a terminal with the command <kbd>gimp</kbd>. Sometimes the program will output error messages that can help. This is especially important if GIMP crashes completely without warning. After reproducing the bug, copy the error messages from your terminal into somewhere where you can save them for the bug report. It is better to give too much information than not enough.
To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running GIMP in another language, try [switching your GIMP to English](https://docs.gimp.org/en/gimp-fire-up.html#gimp-concepts-running-language) so you can report menu items exactly with the English menu item name. It helps - developers generally understand English). If you cannot reproduce the bug, assume it was some weird freak event and don't report it. If it recurs, consult with your appropriate [user mailing list](/mail_lists.html). Perhaps someone else can find the key to reproducing it.
To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running GIMP in another language, try [switching your GIMP to English](https://docs.gimp.org/en/gimp-fire-up.html#gimp-concepts-running-language) so you can report menu items exactly with the English menu item name. It helps - developers generally understand English). If you cannot reproduce the bug, assume it was some weird freak event and don't report it. If it recurs, consult with your appropriate [user mailing list](/discuss.html). Perhaps someone else can find the key to reproducing it.
3. Prepare to face the horror. Go to [bugzilla.gnome.org](https://bugzilla.gnome.org/). If you don't have a login yet, follow the directions to create one. The reason to do this and report a bug with your e-mail address is so the developers can contact you if they have any questions. That way if we miss some useful tidbit of debugging information, they can tell you what to do to get it. Log in.
......
......@@ -17,7 +17,7 @@ Report an issue here!
Making good bug reports is a great way to help increase the software quality of GIMP. A good bug report provides unambiguous step-by-step instructions on how to reproduce the bug, what result is expected, and what the actual result is. Good bug reports make it easy for the developers to reproduce and fix the bug.
Related to bug reports are enhancement requests. An enhancement request should never be filed without prior discussion on the gimp-developer [mailing list](/mail_lists.html). This is to make sure that the enhancement requests that are filed are well-specified and aligned with the overall goals the developers have for GIMP.
Related to bug reports are enhancement requests. An enhancement request should never be filed without prior discussion on the gimp-developer [mailing list](/discuss.html). This is to make sure that the enhancement requests that are filed are well-specified and aligned with the overall goals the developers have for GIMP.
## Bug How Tos
......
......@@ -29,7 +29,7 @@ The goal of the following is to give the developers as much information about wh
If using GIMP for GNU/Linux, start the program from a terminal with the command `gimp`. Sometimes the program will output error messages that can help. This is especially important if GIMP crashes completely without warning. After reproducing the bug, copy the error messages from your terminal into somewhere where you can save them for the bug report. It is better to give too much information than not enough.
To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running GIMP in another language, try [switching your GIMP to English](https://docs.gimp.org/en/gimp-fire-up.html#gimp-concepts-running-language) so you can report menu items exactly with the English menu item name. It helps - developers generally understand English). If you cannot reproduce the bug, assume it was some weird freak event and don't report it. If it recurs, consult with your appropriate [user mailing list](/mail_lists.html). Perhaps someone else can find the key to reproducing it.
To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running GIMP in another language, try [switching your GIMP to English](https://docs.gimp.org/en/gimp-fire-up.html#gimp-concepts-running-language) so you can report menu items exactly with the English menu item name. It helps - developers generally understand English). If you cannot reproduce the bug, assume it was some weird freak event and don't report it. If it recurs, consult with your appropriate [user mailing list](/discuss.html). Perhaps someone else can find the key to reproducing it.
3. Go to [GIMP issues](https://gitlab.gnome.org/GNOME/gimp/issues/). If you don't have a login yet, follow the directions to create one. The reason to do this and report a bug with your e-mail address is so the developers can contact you if they have any questions. That way if we miss some useful tidbit of debugging information, they can tell you what to do to get it. Log in.
......
......@@ -283,7 +283,7 @@ dealing with it.
Great! Please check the [wiki](https://wiki.gimp.org/wiki/Hacking:Developer_FAQ)
for introduction on GIMP development and talk to us on
[IRC](https://www.gimp.org/irc.html).
[IRC](https://www.gimp.org/discuss.html).
### I'm not a developer. Can I still help you somehow?
......
......@@ -18,7 +18,7 @@ Is recommended for most users. Pre-compiled binaries of the stable GIMP are usua
### Development releases
For those who want to check the progress towards the next stable release, and who want to help the developers by testing the code and reporting bugs. The development version contains more features than the stable version but it may crash from time to time so be sure to save your work often. If you are using this version, it is a good idea to subscribe to some of the GIMP [mailing lists](/mail_lists.html) (gimp-user or gimp-developer) so that you can follow the discussions about new features and known bugs.
For those who want to check the progress towards the next stable release, and who want to help the developers by testing the code and reporting bugs. The development version contains more features than the stable version but it may crash from time to time so be sure to save your work often. If you are using this version, it is a good idea to subscribe to some of the GIMP [mailing lists](/discuss.html) (gimp-user or gimp-developer) so that you can follow the discussions about new features and known bugs.
### Git repository
......
......@@ -28,7 +28,7 @@ The goal of the following is to give the developers as much information about wh
If using GIMP for GNU/Linux, start the program from a terminal with the command <kbd>gimp</kbd>. Sometimes the program will output error messages that can help. This is especially important if GIMP crashes completely without warning. After reproducing the bug, copy the error messages from your terminal into somewhere where you can save them for the bug report. It is better to give too much information than not enough.
To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running GIMP in another language, try switching your GIMP to English so you can report menu items exactly with the English menu item name. It helps. (Developers generally understand English) If you cannot reproduce the bug, assume it was some weird freak event and don't report it. If it recurs, consult with your appropriate [user mailing list](/mail_lists.html). Perhaps someone else can find the key to reproducing it.
To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself to explain how to reproduce it in your bug report. If you are running GIMP in another language, try switching your GIMP to English so you can report menu items exactly with the English menu item name. It helps. (Developers generally understand English) If you cannot reproduce the bug, assume it was some weird freak event and don't report it. If it recurs, consult with your appropriate [user mailing list](/discuss.html). Perhaps someone else can find the key to reproducing it.
3. Prepare to face the horror. Go to [bugzilla.gnome.org](https://bugzilla.gnome.org/). If you don't have a login yet, follow the directions to create one. The reason to do this and report a bug with your e-mail address is so the developers can contact you if they have any questions (see also [why we are using Bugzilla](/bugs/why_bugzilla.html)). That way if we miss some useful tidbit of debugging information, they can tell you what to do to get it. Log in.
......
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