From the minutes of a GIMP developer conference meeting not too long ago: The user scenarios would be written down in advance. These scenarios should not be ch

From the minutes of a GIMP developer conference meeting not too long ago: The user scenarios would be written down in advance. These scenarios should not be changed afterwards because it would lead to too much discussion. The goal is to cut down all this discussion. The product vision is to be used as a filter. For example: If someone comes with the request that the UI of GIMP should be like Photoshop, we can simply state: We are not trying to be like Photoshop, because we have a different product vision. http://developer.gimp.org/gimpcon/2006/index.html http://developer.gimp.org/gimpcon/2006/index.html I think defining their software in terms of "not being Photoshop" hurts their software. Photoshop is free to add any features which they think will help users edit images, while the Gimp limits itself to the features that Photoshop has not already chosen.