GNOME.org
 

[gimp-web] content: update the "Get Involved" page.

commit 898df4bd0fe5b344473a5091b42bfc18e63df248
Author: Jehan <jehan girinstud io>
Date:   Wed Sep 21 21:40:42 2022 +0200

    content: update the "Get Involved" page.
    
    I am mostly getting rid of all the redundant text which is about bug reporting
    or hacking GIMP in particular. This was said and re-said in various pages, which
    I am now all merging into the core/ section of the developer website, well
    organized and with no duplicate text.
    
    Instead I transform the initial listing of "ways you can help" into a definition
    list with short texts and appropriate direct links for each item.
    
    Some more contents may still disappear. Not sure how useful the "Development
    Status" is (it's also developer website material, i.e. the roadmaps, and
    available for the general public in news) and the bottom links. I'll see for
    these later and decide if we move these around (or probably just delete these as
    it's all links we list in relevant pages).

 content/develop/index.md | 131 +++++++++++++++++++++--------------------------
 1 file changed, 59 insertions(+), 72 deletions(-)
---
diff --git a/content/develop/index.md b/content/develop/index.md
index 1b2feed3..b1422da4 100644
--- a/content/develop/index.md
+++ b/content/develop/index.md
@@ -11,96 +11,87 @@ Author: Pat David
 
 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](https://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.
+freedoms">Free Software</span> and historically part of the [GNU
+Project](https://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](https://developer.gimp.org/) new features,
-*   report [bugs](/bugs/) (errors in the program),
-*   test existing features and provide feedback,
-*   add [documentation](/docs/),
-*   translate GIMP or documentation to your own language: contact the
-    respective [translator team](https://l10n.gnome.org/teams/) for your
-    language
-*   write [tutorials](/tutorials/),
-*   improve this website,
-*   make artwork for GIMP,
-*   let people know you used GIMP for your artwork,
-*   give away copies of GIMP,
-*   help others to learn to use GIMP, etc.
+[Fix bugs or program](https://developer.gimp.org/core/submit-patch/) new features
+: Our [Developer Website](https://developer.gimp.org/) is where you want to
+start learning about being a code contributor.
 
-As you can see, anyone can help.
+Report [bugs](/bugs/) (errors in the program),
+: GIMP is not bug-free nor is any other application so reporting bugs that you encounter is very important 
to the development, it helps the developers to make GIMP more stable.
+  You don't have to be a developer or a everyday user to report bugs.
 
-### Development Status
+Test existing features and provide feedback
+: If you think a feature can be improved somehow, you can discuss the
+improvements on the [`gimp-gui` mailing list](/discuss.html#mailing-lists) and
+create enhancement requests (the same way you report [bugs](/bugs/)).
 
-The team is currently busy working on v3.0\. This will be a port of GIMP to
-GTK+3, much newer and better supported version of the user interface toolkit.
-
-Most of GIMP's source code is related to the user interface, so this port is a
-major undertaking, especially since we shall break API and refactor numerious
-parts of the program.
-
-We still need to port more plugins to become GEGL operations. If you are willing
-to help with that, please refer to the [Porting filters to 
GEGL](https://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](https://developer.gimp.org/core/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.
+Write or improve the [documentation](https://docs.gimp.org/)
+: The [Documentation websites tells you all about
+contributing](https://docs.gimp.org/help.html).
 
-### Web Development
+Translate GIMP or documentation to your own language
+: Contact the respective [translator team](https://l10n.gnome.org/teams/) for
+your language
 
-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.
+Write [tutorials](/tutorials/) on this website
+: We have a [procedure for writing tutorials](/tutorials/#contributing-new-tutorials-or-fixes) too!
 
-## Hacking
+Improve this website
+: 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. We explain how to help us [in a dedicated
+tutorial](https://developer.gimp.org/core/wgo/).
 
-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:
+Make artwork for GIMP
+: After all, GIMP is for artists, designers, photographers and other creators.
+So if you want to contribute your art under a Libre license, feel free to [reach
+out](/discuss.html).
 
-*   [`gimp`](https://gitlab.gnome.org/GNOME/gimp/) - the GIMP application itself
-*   [`gimp-web`](https://gitlab.gnome.org/Infrastructure/gimp-web/) - repo for this website
-*   [`gimp-web-devel`](https://gitlab.gnome.org/Infrastructure/gimp-web-devel/) - repo for the developer 
site at <https://developer.gnome.org>
-*   [`gimp-help`](https://gitlab.gnome.org/GNOME/gimp-help/) - the GIMP user manual
-*   [plus several 
others](https://gitlab.gnome.org/explore/projects?utf8=%E2%9C%93&name=gimp&sort=latest_activity_desc)
+Let people know you used GIMP for your artwork
+: On your website, social networks or whatnot!
 
-New contributors should first introduce themselves on IRC (the #gimp channel at irc.gimp.org) and/or the 
relevant mailing lists:
+Give away copies of GIMP
+: This is Free Software, it is made to be shared, just like knowledge and
+know-how. Give GIMP to your neighbours, your friend, your family, everyone!
 
-*   [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)
+Help others to learn GIMP
+: Write [books about GIMP](/books/), teach it [in
+university](/news/2018/11/08/gimp-2-10-8-released/#gimp-in-universite-de-cergy-pontoise),
+in websites, video tutorial, everywhere! GIMP is free to use and will never try
+to tamper with your work.
 
-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.
+etc.
+: As you can see, anyone can help. This is what a community is about.
 
-GIMP has a complex code base, and newcomers that might not be sure where to start should have a look at our 
list of bugs for newcomers:
+Once you've figured out what to do, though, be bold and get to work!
 
-* [List of bugs for new 
contributors](https://gitlab.gnome.org/GNOME/gimp/issues?label_name%5B%5D=4.+Newcomers)
+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.
 
-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://developer.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.
+## Development Status
 
-*   [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)
-     _(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)
-     _(The main README for GIMP which should be read by everyone)_
-*   [README.i18n](https://gitlab.gnome.org/GNOME/gimp/blob/master/README.i18n)
-     _(The internationalization README which should be read by translators)_
+The team is currently busy working on v3.0\. This will be a port of GIMP to
+GTK+3, much newer and better supported version of the user interface toolkit.
 
-Once you've figured out what to do, though, be bold and get to work!
+A huge part of GIMP's source code is related to the user interface, so this port
+is a major undertaking, especially since we shall break API and refactor
+numerous parts of the program.
 
-## How To Submit Your Changes
+We still need to port more plugins to become GEGL operations. If you are willing
+to help with that, please refer to the [Porting filters to 
GEGL](https://wiki.gimp.org/index.php/Hacking:Porting_filters_to_GEGL)
+page to see what you could work on.
 
-When you're ready, we suggest to create a fork of the repository [GitLab Fork 
Repository](https://docs.gitlab.com/ee/gitlab-basics/fork-project.html#how-to-fork-a-project), make your 
edits to the fork and submit a [GitLab Merge 
Request](https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html#how-to-create-a-merge-request). Make 
sure you select the item of
-**"Allow commits from members who can merge to the target branch."**, this will allow the developers to do 
additional changes or to give
-feedback in a simpler way.
+To get a better understanding of where the project is heading to, which features
+are planned etc., please visit the [Roadmap](https://developer.gimp.org/core/roadmap/) page.
 
-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
 
@@ -127,7 +118,3 @@ The GIMP community is a friendly one, but it probably is still worth saying this
 
 [GNOME GIT](https://gitlab.gnome.org/)
  GNOME GIT source code repository
-
-## Latest Changes in Code
-
-The [Unstable GIMP](https://gitlab.gnome.org/GNOME/gimp/commits/master) 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]