"Henry Roeland" <[EMAIL PROTECTED]> writes:

> He all GIMP developers out there,
> I'm new to this list and therefore lets introduce myself first. As a
> Software developer I'm working for about 2 years now with Java/C/C++
> and  other languages like XML/XSLT. My expirence with C/C++ is about
> medium and  I know a little about Linux/UNIX programming but have more
> expirence with  Win32 platforms.My expirence with GTK+ and GIMP code
> is zero.
> At this time I'm working(Using) now about 2 weeks with The GIMP for
> graphical stuff (as a hoby) and I'm very excited about all that GIMP
> offers! Because I'm a developer I like to help fixing bugs or add some
> new  features. A already debuged some of the code but because of my
> lack of  expirence with GTK+ and all I like to begin easy :-).
> In short: Can I help with bug fixing? If so should I start with bug
> fixing  (which bugs) and how and to who can I deliver the patches?

Most of this is answered in the Developer FAQ
(http://developer.gimp.org/faq.html) but I will happily answer your
questions anyway.

A good way to get start is to make yourself familiar with
Bugzilla. You can use the predefined queries at
http://developer.gimp.org/bugs.html as a start. Some bugs have the
easy-fix keyword set. Those might be a good start. But we have only
just started to use that keyword, so if a bug doesn't have it set,
doesn't necessarily mean that it is very complex.

We will be releasing 2.2.0 real soon now and will enter a new
development cycle as soon as this has happened (or perhaps wait until
2.2.1 is done). That's a good time to start working on new features.
Just let us know what you are working on and, most importantly, don't
be afraid to ask.

Gimp-developer mailing list

Reply via email to