How You Can Help
GIMP is Free Software and a part of the GNU Project. 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 new features,
- report bugs (errors in the program),
- debug existing features,
- add documentation,
- translate GIMP to your own language,
- translate the documentation,
- write tutorials,
- participate in the UI brainstorm,
- improve this web site,
- make artwork for GIMP used in or with GIMP,
- let people know you used GIMP for your artwork,
- give away copies of GIMP,
- help others to learn to use GIMP, etc.
As you can see, anyone can help.
The team is currently busy working on v2.10. This will be the first release of GIMP featuring a new, advanced image processing engine, high bit depth editing, as well as new and improved transformation and selection tools.
Porting internals of GIMP to GEGL is mostly done, but more plugins have to be ported to GEGL, and GEGL needs to be made faster. If you are willing to help with that, please refer to the 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 page.
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 page you will find some very good help about this.
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.
This is the part where people are always needed to help with the development, and this is also the part that is the hardest to start with. Though there are websites and files to give you a good look at how hacking is being done in GIMP.
The site you should keep updated with and the site that is updated all the time with new development help guides is located at http://wiki.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.
(Contains most up-to-date information on building GIMP from source code)
(Contains a lot of information that you need to know if you want to start coding)
(The main README for GIMP which should be read by everyone)
(The internationalization README which should be read by translators)
Important GIMP Links
- The GNU Image Manipulation Program - www.gimp.org
- GIMP Wiki - wiki.gimp.org
- GIMP Bugzilla - bugs.gimp.org
- The GIMP Toolkit - www.gtk.org
- GNU Project - www.gnu.org
- GNU General Public License - GPL
GIMP RSS feeds
The main GIMP development website.
Martin Nordholts' GIMP Blog
What happens in GIMP development.
An image processing library based on GObjects.
GNOME GIT source code repository
Latest Changes in Code
The Unstable GIMP page lists the lastest source code commits to the unstable branch of GIMP.