Mailing Lists

If you want to discuss features, tips, tricks or contribute to the development of GIMP, then we have several useful mailing lists and IRC channels for you.

The original (mostly unix based) user list. For the everyday user. Here you will find tips for doing cool effects, user questions, etc.
Archives: GNOME, mail-archive, Gmane, nabble, spinics
Old Archives: mail-archive
GIMP Developer
The GIMP developer list. For plug-in developers and core program developers; discussion about the source code.
Archives: GNOME, mail-archive, Gmane, nabble
Old Archives: mail-archive
GEGL Developer
The GEGL developer list. For developers interested in contributing to GEGL, the new architecture for image processing.
Archives: GNOME, mail-archive, Gmane
Old Archives: mail-archive
The GIMP GUI list. For discussions around UI/UX.
Archives: GNOME, mail-archive,
The GIMP web list. For discussion about the contents and structure of this web site.
Archives: GNOME, mail-archive, Gmane
The GIMP documentation list. For discussion about the GIMP User Manual and all derivative works.
Archives: GNOME, mail-archive, Gmane
Old Archives: mail-archive

Code of Conduct

Mailing lists are an important communication channel between contributors and users of GIMP. Therefore we urge you to follow the following common etiquette rules. Failure to observe them, or instructions from the moderators, may be grounds for reprimand, probation, or removal.

  • Be considerate and respectful. Every email in our most popular mailing lists, gimp-user@ and gimp-developer@, will be read by ca. 1,000 subscribers and then aggregated to be seen by an even larger audience. Please make sure that you add value to the discussion, avoid repetitive arguments, flamewars, trolling, and personal attacks.
  • Write in English. While GIMP community is multinational, we need a lingua franca for communication which happens to be English. It’s OK to have bad skills in English as long as you do your best.
  • Do basic research. Chances are that your questions, feature requests, or bug reports have already been thoroughly discussed, and decisions have already been made. See the list of source for reference below.
  • Stick to plain text. Please don’t send emails in HTML.
  • Be specific. When describing a bug you discovered, please always mention: operating system and its version, architecture (32bit or 64bit), exact version of GIMP (use File->About for reference).
  • Keep it short. When replying long threads, please trim unnecessary content and write your replies inline instead of “top posting”.

The code may change in the future, followed by a notification to subscribers.

Please use these sources to check for information on the project, roadmap, feature requests, bug reports etc.:

  • Bug tracker. Useful for checking bug reports and feature reqursts.
  • Roadmap. We do not schedule releases, but we plan what things we work on next.
  • FAQ. There are some frequently asked questions we already replied.
  • Usability. There’s ongoing work to improve user experience of GIMP.
  • Development. If you wish to contribute, please check the wiki for basic information for developers.

We also suggest checking archives of the mailing lists for existing discussions.