On Sun, Mar 11, 2012 at 2:21 PM, grafxuser wrote:

Hi,

I'm a bit confused about this answer. Was it meant sarcastic or is there no planning at all in GIMP development?

Could it be both? :)

Planning with the current amount of active developers would be rather pointless.

Alexandre Prokoudine http://libregraphicsworld.org

On Sun, Mar 11, 2012 at 11:23 PM, grafxuser wrote:

I'm software developer, too, and would support GIMP when I have more time. Reading various postings I'm convinced I'm not the only one with this approach. For outsiders the decision to contribute would be easier, if they knew the project is still alive and their contribution would improve something.

The outsiders can read regular news at gimp.org or our very active Google+ page. If the outsiders choose not to do that, I fail to see how else I can get the message through. It's not as if I should be knocking on every door asking "Any potential GIMP contributors inside"? This is really, really simple :)

I heard, some developers packed it all in, because they didn't see their patches become integrated. If one is under the impression, that a project is more an unsystematic tinkering and his contribution doesn't actuate or advance something, it will be pointless for him to get involved.

There are different reasons for a patch to not be integrated. Not all of that has something to do with "unsystematic tinkering".

If you'd publish the progress and the successes in GIMP development at the gimp.org front page more often and outsiders see the project running in ordered circumstances, your problem with missing developers could be solved or at least alleviated.

More often than...?

Alexandre Prokoudine http://libregraphicsworld.org

Alexandre wrote:

Planning with the current amount of active developers would be rather pointless.

I'd say roadmapping work even when there is only one developer, on a half-time basis. it is simply about what needs to be done for the next version. and just as important, that no non-trivial effort is spent on things that are not on the roadmap.

over the years I have seen GIMP being very good at ignoring efforts. enough for me to also say: to remain motivated I also pick my own topics that I want to work on (instead of just playing fireman for non-roadmapped development that keeps popping up).

I think it has been pointed out in the last days here that this knack for ignoring roadmaps has not helped the release frequency of GIMP.

--ps

founder + principal interaction architect man + machine interface works

http://blog.mmiworks.net: on interaction architecture

On Tue, Mar 13, 2012 at 1:58 AM, peter sikking wrote:

Alexandre wrote:

Planning with the current amount of active developers would be rather pointless.

I'd say roadmapping work even when there is only one developer, on a half-time basis. it is simply about what needs to be done for the next version. and just as important, that no non-trivial effort is spent on things that are not on the roadmap.

Which is our plan for post-2.8 :)

Alexandre Prokoudine http://libregraphicsworld.org

Prokoudine wrote:

On Tue, Mar 13, 2012 at 1:58 AM, peter sikking wrote:

I'd say roadmapping work even when there is only one developer, on a half-time basis. it is simply about what needs to be done for the next version. and just as important, that no non-trivial effort is spent on things that are not on the roadmap.

Which is our plan for post-2.8 :)

famous last words...

--ps

founder + principal interaction architect man + machine interface works

http://blog.mmiworks.net: on interaction architecture