This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Re: When open source projects close the process, something's wrong

Posted by: Anonymous [ip: 69.221.78.208] on November 06, 2007 06:56 AM
> Thanks a lot for writting this. I'm the author of those e-mails... I wanted to be a volunteer for the GIMP UI redesign.
> However, the "position was closed".

No. The position was closed "at the moment". At the time you volunteered the GIMP project was in both "feature freeze" and all development efforts were focused on fixing bugs and refining the final touches on already-implemented features in preparation for the next release. Would you have all the other volunteers (dozens, if not hundreds) put their efforts on hold while your talents and knowledge were assessed so that a suitable role could be created to productively make use of your contributions?

And were you not treated very kindly by GIMP's project leader, Sven Neumann, as he pointed out that the UI suggestions you were making needed to be implemented at the toolkit level -- and provided instruction on how you might more effectively present your ideas to the GTK+ development team?

I am disappointed that you would applaud the comments made in this article. It only requires a minimum of retrospection to realize that you were proposing the wrong ideas at the wrong time to the wrong project. It has nothing at all to do with how open or closed the GIMP development project may be.

#

Return to When open source projects close the process, something's wrong