Appendix C. How to Contribute

# Appendix C. How to Contribute

Welcome to the GIMP-Help team!

This tutorial is intended for writing documentation. If you want to translate the documentation or the user interface, please go to "https://l10n.gnome.org/teams/xx" where "xx" is your language code: ISO 639-1 language codes can be found at http://www.loc.gov/standards/iso639-2/php/code_list.php.

## 1. Prerequisites

### 1.1. Join our mailing list

You can join our mailing list at https://mail.gnome.org/mailman/listinfo/gimp-docs-list. Please, feel free to ask questions.

### 1.2. Create a Local Working Copy of Code

The GIMP help Manual is lodged in a central repository at https://gitlab.gnome.org/GNOME/gimp-help. Creating a local copy of this repository to work on makes sure that everyone can work on his own without fuzzing around into works of other contributors.

As a newbie, you will access the git repository anonymously (without an account). Open a terminal and type: git clone https://gitlab.gnome.org/GNOME/gimp-help.git .

If you have a GNOME account, the command is: git clone git@gitlab.gnome.org:GNOME/gimp-help.git .

This will create a ”gimp-help” folder in your current directory. Be patient! That's a big download: about 700 MB.

### 1.3. Installing your sandbox

After downloading your local copy, run: cd gimp-help then ./autogen.sh --without-gimp ALL_LINGUAS="en xx".

When running ./autogen.sh, you can notice some not found packages, for example ”checking for dblatex... no”. Most of them are related to PDF files and you have to install them before running ./autogen.sh again if you want to create PDF files.

### 1.4. The gimp-help folder

The GIMP User Manual is maintained in the xml files of the ”src” folder. You will use these xml files to work on.

3. What Happens to a Bug Report after you Submit it |  | 2. Workflow

Report an error in the bug tracker