> Okay, so I misjudged the state of development Gimp is in. I remember trying 
> to find out some time ago how hard it would be to contribute things to Gimp, 
> but I gave up pretty soon. In another thread Rebecca Walter suggested 
> creating a TODO for developers that want to help. I'd like to suggest they 
> make a HOWTODO, because even if you want to help, you have this 15MB pile of 
> source in front of you and not much of an idea of where to start. Some time 
> ago I read the documentation that comes with GEGL, which is quite a lot of 
> code too with a weird pseudo-language as an added bonus, but it's much easier 
> to understand the structure of the code if you have a nice doc that explains 
> what's what.

Yes, this would be nice, but the problem is finding someone to write
it.  Do we have any volunteers? Anyone who could outline a basic process
for conquering some of the projects on Sven's to do list?

Other than that, come join us on #gimp on irc.gimp.org sometime.  You
can learn a lot by listening there and maybe start getting your claws
into the code a little more.  My challenge of the moment is figuring out
how to understand the strings. :-) I'm no coder so sometimes I get
confused to death.  But the channel is a good place to find out what is
going on.  Mitch and Sven are even there a lot. :-)

Gimp-developer mailing list

Reply via email to