

So the broad decisions about what will be done and in what way have already been made at the team- and individual-psychology level, assuming this money doesn't radically change the core team composition. Users who get the most out of GIMP will learn GIMP and its leverage points, rather than discovering that GIMP works the way they do or "shows something big" to demonstrate that it is in sync with what makes something cool or interesting to others (the area of fitting the user's style, be it Maya or whatever, has become a Blender specialty since at least the last decade+). This kind of approach looks at GIMP as a very unique thing-there's nothing else quite like it, and that's worth celebrating and understanding and working on. GIMP developers have long demonstrated more of a GIMP-is-GIMP approach.

That reflects a particular kind of psychological reward system working within the development team. I would go so far as to argue that part of gimp's less intuitive UI is because of having more developers, and if there were fewer developers total the UI would be more cohesive.īlender has always been very project-focused, and you could even say it's really project-identified. For some developers, the numbers would be vastly worse). A developer jumping into irc and trying to ramp up, which for about the first 6 hours of time will likely be a drain on the existing developers with no positive value return until at least 15 work-hours of the developer ramping up (and that's assuming a developer who is already quite experienced and can ramp up pretty efficiently.
#PHOTOFLOW AND GIMP 2.8 PATCH#
A trivial patch which causes more lost time ($) for the existing gimp developers than it creates valueĢ. There are two realistic outcomes from a "1 hour to contribute something" thing:ġ. In reality, if everyone in this thread tried to contribute to gimp for an hour, I expect we'd get two patches of any value out of it, and about 100 hours of time that did nothing but negatively impacted existing gimp developers. Expecting a developer who hasn't yet worked in the gimp codebase to make a meaningful contribution worth a positive dollar value in an hour is vastly under-estimating the cost of ramping up a developer.
